Mobile Operator & Circle Fetch API
Provides real-time operator name (JIO, Airtel, VI, BSNL), operator ID, circle name, circle ID.
POST /api/v1/operator/fetch
~50ms Avg Latency
99.9% Uptime SLA
x-api-key Auth
API Overview
Fetch real-time mobile operator and telecom circle details by mobile number.
Key Features & Data Points:
- Instant Authoritative Response: Fetches verified official data with ultra-low response latency (~50ms).
- 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 |
|---|---|---|
| request_payload* | object | JSON object containing verification parameters. |
Request & Response Examples
Sample Request:
HTTP POST /api/v1/operator/fetch
POST /api/v1/operator/fetch
x-api-key: your_api_key_here
Content-Type: application/json
{\n "mobileNumber": "9876543210"\n}
Sample Response (200 OK — Sanitized Test Data):
HTTP 200 OK • application/json • 50ms
{\n "code": 200,\n "status": "success",\n "message": "Success",\n "request_id": "NS2608311622027UZ0FG",\n "response": {\n "request_Id": "NS2608311622027UZ0FG",\n "mobile_Number": "9876543210",\n "operator": "JIO",\n "operator_Id": "102",\n "circle": "Rajasthan",\n "circle_Id": "19"\n }\n}
Business Use Cases
1
Mobile Recharge Apps
Designed for mission-critical workflows requiring verified real-time data lookups.
2
Telecom Billing & Verification
Designed for mission-critical workflows requiring verified real-time data lookups.
3
Payment Gateway Routing
Designed for mission-critical workflows requiring verified real-time data lookups.
Integration Steps
1
Set x-api-key header
2
Send POST request to /api/v1/operator/fetch with mobileNumber
3