Welcome to the Hubby API documentation. This API enables partners to seamlessly integrate eSIM booking and management capabilities into their applications.
Key Features:
The API supports four types of packages:
Starter packages: Hybrid packages that are both data and time limited. They provide a small data allowance within a short time period (default: 2 days). Perfect for first-time users and trials.
Data-limited packages: Traditional packages with a specific data allowance that expires after a certain period (default: 365 days). This is the primary package type and the default for most use cases.
Unlimited packages: Packages that provide unrestricted data usage for a specified duration. Subject to fair use policy. Ideal for heavy data users and digital nomads.
Time-limited packages: Packages that provide a fixed data allowance for a specific duration with full-speed access. These packages expire when either the data limit or time limit is reached.
Note: Top-ups are always data-limited packages, regardless of the original package type.
Authentication: All API requests must include the following headers:
The HMAC signature must be generated for each request using:
Note: Swagger UI cannot be used to test the API directly as each request requires a unique HMAC signature. Please implement the authentication in your client application.
Example Node.js Implementation:
const cryptoJs = require('crypto-js');
// Configuration values that would normally come from environment
const secretKey = "YOUR_API_SECRET";
const publicKey = "YOUR_API_KEY";
const baseUrl = "YOUR_BASE_URL";
// Function to generate headers for API request
function generateApiHeaders(method, path) {
//Timestamp is in milliseconds e.g. 1715558400000
const timestamp = Math.floor(Date.now()).toString();
// Ensure url is a string
let path = String(url);
// Remove baseUrl from the url if present
path = processedUrl.replace(baseUrl, '');
// Create query string if needed
const queryString = new URL(url).search;
if (queryString) {
processedUrl += queryString;
}
// Validate public key
if (!publicKey) {
throw new Error("Public key is required");
}
// Create the payload
// Sample payload: 1715558400000GET/bookings?bookingId=1234567890
const payload = timestamp + method + path;
// Generate the HMAC signature
const signature = cryptoJs.HmacSHA256(payload, secretKey).toString(cryptoJs.enc.Hex);
// Return headers object
return {
'x-timestamp': timestamp,
'x-signature': signature,
'x-api-key': publicKey,
'Accept': 'application/json'
};
}Need Help?
Returns everything needed to render any screen in a native eSIM integration: eSIM status, installation credentials, and all packages with live usage data.
This is the central endpoint for the Native API. One call gives you the traveler's full state.
When to call:
Authentication: HMAC-SHA256 (same as all partner endpoints).
curl -i -X GET \
https://docs.hubbyesim.com/_mock/apis/v2_0_0/openapi/native/users/partner_user_456{ "success": true, "data": { "external_user_id": "partner_user_456", "esim": { … }, "packages": [ … ] } }
Returns AI-generated, device-specific eSIM installation instructions tailored to the traveler's exact device model, OS version, locale, and current eSIM state.
You do not need to hard-code or maintain installation content in your app — Hubby keeps instructions current for every device and OS version.
The response adapts to:
Authentication: HMAC-SHA256 (same as all partner endpoints).
curl -i -X POST \
https://docs.hubbyesim.com/_mock/apis/v2_0_0/openapi/native/users/partner_user_456/instructions \
-H 'Content-Type: application/json' \
-d '{
"device_info": {
"os": "iOS",
"os_version": "17.4",
"device_model": "iPhone 15 Pro"
},
"locale": "en"
}'{ "success": true, "data": { "instructions": [ … ], "device_summary": "iPhone 15 Pro running iOS 17.4", "install_method": "qr_code" } }
Activates a queued package for a traveler. If there is a currently active package, it is terminated and the selected package becomes active.
When to call: Only when the traveler has multiple queued packages and needs to choose which one to activate. If only one package is queued, it auto-activates when the traveler connects to a local network at the destination.
Authentication: HMAC-SHA256 (same as all partner endpoints).
curl -i -X POST \
https://docs.hubbyesim.com/_mock/apis/v2_0_0/openapi/native/packages/pkg_abc/activate{ "success": true, "data": { "package_id": "pkg_abc", "destination": "TR", "size": "1GB", "status": "active", "activated_at": "2026-07-20T10:00:00Z", "previous_package": { … } } }