Mobile Plans Fetch API
Provides real-time prepaid mobile recharge plans categorized by Truly Unlimited, Data Packs, Entertainment, Validity Packs, etc., with price, validity, talktime, data, voice, and benefits.
POST /api/v1/plans/fetch
~<500ms Avg Latency
99.9% Uptime SLA
x-api-key Auth
API Overview
Fetch all browse recharge plans for Airtel, VI, Jio, and BSNL mobile numbers across all categories.
Key Features & Data Points:
- Instant Authoritative Response: Fetches verified official data with ultra-low response latency (~<500ms).
- Clean JSON Standard: Normalized structure across all verification services for effortless enterprise integration.
- Enterprise SLA: Backed by NextStepApi 99.9% uptime architecture and redundant provider failover.
- Secure Header Authentication: Direct authentication via
x-api-keyrequest header.
Request Specification
Headers:
| Header Name | Type | Description |
|---|---|---|
| x-api-key* | string | Your secret production API Key obtained from your NextStepApi dashboard. |
| Content-Type* | string | Must be set to application/json. |
| x-request-id | string | Optional client-generated tracking ID (e.g. REQ12345XYZ) for idempotent logging. |
Request Body (JSON):
| Parameter | Type | Description |
|---|---|---|
| mobileNumber* | string | 10-digit Indian prepaid or postpaid mobile number. |
| operatorId* | string | Operator identifier code (e.g. 102 for Jio, 104 for Vi, 101 for Airtel). |
Request & Response Examples
Sample Request:
HTTP POST /api/v1/plans/fetch
POST /api/v1/plans/fetch
x-api-key: your_api_key_here
Content-Type: application/json
{
"mobileNumber": "9898765432",
"operatorId": "104"
}
Sample Response (200 OK — Sanitized Test Data):
HTTP 200 OK • application/json • <500ms
{
"code": 200,
"status": "success",
"message": "Plans fetched successfully",
"request_id": "REQ1234567890",
"response": {
"mobile_number": "9898765432",
"operator_id": "2",
"operator_name": "VI",
"circle_name": "Rajasthan",
"circle_code": "RJ",
"total_plans": 127,
"categories": []
}
}
Business Use Cases
1
Recharge Platforms
Designed for mission-critical workflows requiring verified real-time data lookups.
2
Browse Plans Directory
Designed for mission-critical workflows requiring verified real-time data lookups.
3
Telecom Apps
Designed for mission-critical workflows requiring verified real-time data lookups.
4
Digital Wallets
Designed for mission-critical workflows requiring verified real-time data lookups.
5
Payment Gateways
Designed for mission-critical workflows requiring verified real-time data lookups.
Integration Steps
1
Provide x-api-key header
2
POST /api/v1/plans/fetch with mobileNumber and operatorId
3