APIURLSCONNECTED SERVICES
Log inGet started
HomeCatalogDashboardWalletSupport

API Documentation

Build your applications with the API URLS reseller endpoints.

i
Server-side integration only

All purchase requests use your own API URLS wallet. Never expose your API key publicly. Endpoints work only after platform installation and successful supplier configuration.

Authentication

Create a personal key under My API Keys, and send it with requests:

Authorization: Bearer au_YOUR_API_KEY

Endpoints

MethodPathDescription
GET/api/v1/balanceYour PKR wallet balance
GET/api/v1/countriesAvailable product groups
GET/api/v1/servicesCatalog and PKR prices
POST/api/v1/orderPlace a purchase using product_id, quantity and rental_time
GET/api/v1/order_status?order_id=1Order status and allocated numbers
GET/api/v1/otp?number_id=1Check recent SMS (when available)

Example — List products

curl -H 'Authorization: Bearer au_YOUR_API_KEY' \
  'https://YOUR-DOMAIN/api/v1/services'

Example — Purchase

curl -X POST 'https://YOUR-DOMAIN/api/v1/order' \
  -H 'Authorization: Bearer au_YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: YOUR_UNIQUE_32_HEX_ID' \
  -d '{"product_id":1,"quantity":1,"rental_time":1}'

Keep the idempotency key unchanged when retrying the same order. JSON responses include code, data, and message. API orders are charged in PKR.

About upstream 555API

Supplier requests are made through the API URLS backend; the upstream credential is never returned to a customer. The supplier's exact API base URL and account access must be confirmed by the administrator.