OTPPINDocumentationManage API keys ↗

API reference

Inspect request and response schemas from the application's OpenAPI document. Requests sent using the interactive client are real: purchase operations can debit your balance. Start with a read-only account request.

Endpoint index

JSON REST API under /api/v1/*. Authenticate with an API key generated from the OTPPin dashboard, sent in the X-API-Key header (or as Authorization: Bearer <key>). Each endpoint also needs a matching permission on the key; a key without it gets 403. Every error is JSON { "error": "<CODE>", "message": "<human text>" }. Read endpoints are limited to 600 requests per minute per user and order creation to 120 per minute; a 429 carries a Retry-After header. A separate handler_api.php SMS-activation protocol (SMS-Activate compatible) is served at /stubs/handler_api.php and is documented on the API docs page.

Account

Authenticated account info.

Inventory

Browse supported countries, services, operators and live pricing.

Orders

Create and poll one-time number orders. Cancel is available after 2 minutes. Finish and resend exist as routes but are not available.

Rentals

Rent a number for a fixed duration and read every SMS it receives. A rental can be cancelled for a full credit only inside its cancel window and before any SMS arrives.

The machine-readable document is at /api/openapi. Guides and examples are in the API documentation.