Ago Verify - API Documentation

Authentication

All API requests must include your API key. You can manage keys from your Developer page.

X-API-Key: av_your_api_key_here

Or use the standard Bearer token header:

Authorization: Bearer av_your_api_key_here

Base URL

https://agoverify.com/api/v2

Endpoints

GET /services

List all services available via the API.

GET /countries

List all countries available via the API.

GET /countries/for-service?service={service_code}

List countries for a service.

GET /service-price?service={code}&country={code}

Get price for a service/country combination.

GET /balance

Get current account balance.

POST /orders

Create an order. Body: service_code, country_code, operator (optional).

GET /orders

List order history.

GET /orders/active

List active orders.

GET /orders/{id}

Get order details.

GET /orders/{id}/status

Check order status and retrieve SMS code.

POST /orders/{id}/cancel

Cancel an active order.

Provider Selection

AgoVerify runs a unified backend. You never need to specify a provider or server; the system automatically picks the highest-priority enabled provider that has stock for the requested service and country.

Create an order example

curl -X POST "https://agoverify.com/api/v2/orders" \
  -H "X-API-Key: av_your_api_key_here" \
  -H "Accept: application/json" \
  -d "service_code=tg" \
  -d "country_code=0"

Webhooks

Webhooks are sent as POST requests to your registered endpoints. Configure them from the Developer page.

Supported events:

order.created — a new order was created.
sms.received — an SMS code was received for an order.
order.cancelled — an order was cancelled and refunded.
order.expired — an order expired and was refunded.

Each webhook includes a X-Webhook-Signature header (HMAC-SHA256 of the JSON body using your endpoint secret) and X-Webhook-Event.