Recharge API documentation

Recharge API

A server-to-server API for mobile and DTH recharge. Everything is JSON over HTTPS, authenticated with an API token issued to you and restricted to your own IP addresses.

Get started API reference

Base URLhttps://apipe.in

This is the Recharge API: recharge, its status, your balance, operators, services and complaints, with your API token alone. Bill payments, money transfer, bus booking, request signing and signed version 3 callbacks are in the Full API docs.

Get started

AuthenticationSend your API token on every request.Retries & idempotencyEvery money endpoint is idempotent on your own reference — urid on recharge, request_id everywhere else.CallbacksGive us an HTTPS URL and we will call it:Service statusQuery it yourself at any time with GET /api/corp/v1/services rather than hardcoding a service list.

API reference

CoreThe modern surface for new integrations.5 endpoints RechargeMobile and DTH recharge.4 endpoints

Reference

Operator codesOn /api/corp/v1/* send the Code column.Result codesThe numeric code field in v1 replies uses this catalog.

One surface

Surface	What you get
`/api/corp/v1/*`	Proper HTTP status codes, a machine-readable `error` string, and a numeric `code` support can trace. JSON in, JSON out, POST for anything that moves money.

Each service answers in its own JSON shape. Read the endpoint you are calling rather than assuming a shared envelope. One exception: a new request we refuse for an account or service reason answers HTTP 200 with a failed reply in the recharge reply's fields, on every service (see Errors).