Skip to main content

GET Get all eSIMs

Tip: Use filtering options to narrow down your search results for company-specific or inventory-specific queries.

This endpoint returns a paginated list of all eSIMs with optional filtering by company and inventory.

Configure the API Endpoint

https://esim.betatel.com/api/v1/esim/sim-registries
  • Method: GET

Set Up the Headers

ParamValueDescription
Content-Typeapplication/jsonSpecifies the payload format.
x-api-key{{x-api-key}}Your unique API key for secure access.
x-user-id{{x-user-id}}Your user identifier for added security and tracking.

Query Parameters

Hint: Filters enable targeted retrieval of eSIMs, streamlining the management of multi-company deployments.

ParamTypeRequiredDefaultDescription
countintegeroptional100Number of items to return
offsetintegeroptional0Number of items to skip
companyintegeroptional-Filter by company ID
inventoryintegeroptional-Filter by inventory ID

Example Response

Status Code: 200 OK
Content-Type: application/json

Example Response
{
"total": 250,
"offset": 0,
"count": 20,
"sims": [
{
"iccid": "89148000004012345678",
"sim_status": "WAITING_FOR_ASSIGNMENT",
"group": {
"id": 1001,
"name": "Premium Group"
},
"inventory": {
"id": 12345,
"name": "US East Inventory"
},
"company": {
"id": 100,
"name": "Acme Corp"
},
"provisioned_date": 1640995200,
"terminated_date": 0,
"imsis": [
{
"sponsor_id": 200,
"imsi": 310260123456789
}
],
"mapped_imsi": 310260123456789
}
]
}

The response includes the total number of eSIMs available, current pagination offset, number of items returned, and an array of eSIM objects with detailed information including status, group, inventory, company, and IMSI data.

Code Snippets

Note: These snippets guide API interaction. Ensure all parameters and headers align with specified requirements.

Example - cURL
curl --location 'https://esim.betatel.com/api/v1/esim/sim-registries' \
--header 'Accept: application/json' \
--header 'x-api-key: {{x-api-key}}' \
--header 'x-user-id: {{x-user-id}}'

Error Handling

Important: Keep query parameters accurate to avoid general '400' errors related to bad requests.

  • 400 - Bad Request - Invalid parameters
  • 401 - Unauthorized - Invalid or missing API key