Partner Catalog API Reference
Endpoints, parameters, schemas and error codes for the SafarieSIM Partner Catalog API.
What the catalog endpoint returns
The Partner Catalog API exposes SafarieSIM's live eSIM catalog in OpenAPI 3.1 form. A singleGET /partner-catalog request returns the plans that are currently on sale, with their destination, data allowance, validity, coverage countries and prices in the currency you ask for, so a comparison or affiliate platform never has to cache a stale price list.
Base URL and authentication
Production base URL: https://api.safariesim.com/functions/v1. Authenticate with your partner key, sent as x-api-key or as a bearer token. Keys are requested on the partner application page; requests without a valid key return 401.
Query parameters
country— ISO-3166 alpha-2 code; returns every plan whose coverage includes that country.destination— destination slug, for examplekenya.currency— requested pricing currency; a currency without an active conversion rate returns400 unsupported_currency.days— durations to price for day-based destinations (7,1,5,10,1-30orall).format—catalog(default),esims-iooresimdb.pageandper_page— pagination;per_pagedefaults to 100 and accepts up to 250.
Fields in each plan
id— stable plan identifier:<slug>-<days>dfor day-based destinations, the variant UUID for fixed packages.priceandprice_usd— retail price for one traveller for the whole plan in your requested currency, and the same amount in USD before conversion.data_amount_mbandis_unlimited— allowance, withnulldata for unlimited plans; checkis_unlimitedfirst.countries— every country the plan covers, including the full list for regional plans.operatorsandnetwork_types— the recorded local networks and their technologies.product_urlandcheckout_url— the public page and a deep link that opens it with the plan preselected, ready for your affiliate parameter.last_updated— when the plan record was last changed in the catalog.
Freshness, caching and rate limits
Prices are calculated per request by the same resolver the retail checkout uses, so a catalog price always matches what a customer pays for that plan. Responses carry a five-minute cache header and the shared hourly rate limit applies, so polling more often than every five minutes returns no fresher data. Wholesale cost and supplier configuration are never exposed through this endpoint.
Errors
400 unsupported_currency/400 unsupported_format— the query parameter is not one the API serves.401 unauthorized— the partner key is missing, unknown or revoked.405 method_not_allowed— onlyGETis supported.500 internal_error— temporary failure; retry with backoff.
Who uses the partner catalog API
Comparison sites, eSIM directories and affiliate platforms read the catalog to publish current plans and prices instead of maintaining their own price list, then send buyers to the checkout deep link with their referral code attached. Because the same numbers feed the storefront, a published listing cannot drift from the price a buyer is charged.
MCP server for AI assistants
The same catalog is available as a public, read-only Model Context Protocol server, so an AI assistant can search plans, compare countries and calculate the data a trip needs. It needs no key and returns the same prices as this API.