Corporate APIv1

Developer documentation

Corporate API

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

Get startedAPI reference
Base URLhttps://apipe.in

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 endpointsRechargeMobile and DTH recharge.4 endpointsBill payments — BBPSBrowse the biller directory, render the biller's input form from its customer_params schema, fetch the live bill, then pay.7 endpointsBus bookingSearch a route, open the seat map and the boarding points, hold seats with block, then confirm with book.10 endpointsDomestic money transferRegister the sender once per bank, add a beneficiary, then transfer with the sender's OTP.25 endpoints

Reference

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

One surface

SurfaceWhat 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).