The Nepex API is designed for travel agencies and partners who want to connect their own booking or back-office tools to Nepex. It provides a stable, versioned HTTP interface to look up countries and visa types and to start visa applications programmatically, so travellers’ data can flow from your environment into Nepex without manual re-keying.

API traffic is grouped under **/api/v1/platform/*. Typical first calls are read-only (countries, visa metadata); write operations such as creating an application use `POST` with a JSON body. All calls are authenticated with an API key** issued to your organization. Keys belong on your servers or secure integration layer — not in public websites or mobile apps.

Before API access is enabled, Nepex completes partner onboarding and enables the integration for your account. Once enabled, you manage API keys, allowed website origins, and webhook endpoints per environment from your signed-in account on the Nepex travel website (see Authentication and Environments).

Responses use a single JSON style across endpoints: successes include status, statusCode, and result; problems return status: false with a message you can surface in logs or support tooling. Rate limits apply per key; watch the X-RateLimit-* response headers to stay within quotas.

Webhooks let Nepex notify your systems when an application’s status changes, so you can update your CRM or traveller-facing status without polling. You configure callback URLs per environment in the same account area where you manage API keys.