PayOrbit
Sign in

Plan & Operator · Operator & Plans

Mobile Operator Find

Detect which operator a mobile number belongs to

POST request

URL: https://api.payorbit.in/api/v1/plan/operator-fetch

Body

{
    "mobile": "9431023126",
    "orderid": "OPF_001"
}

Include a valid Bearer token with every request

Code sample

curl -X POST "https://api.vizodigital.com/api/v1/plan/operator-fetch" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "mobile": "9431023126",
    "orderid": "OPF_001"
}'

Success Response

{
    "fee": 0,
    "data": {
        "circle": "Bihar",
        "number": "9431023xxx",
        "company": "Jio",
        "orderid": "OPF_001",
        "circle_code": "52"
    },
    "status": "success",
    "message": "UAT sample — operator fetched. Use production credentials for live aggregator data.",
    "wallet_balance": 1000
}

Failure response

{
    "status": "error",
    "message": "Request failed. Check credentials, wallet balance, or validation errors."
}

Overview

Verifies which telecom operator a mobile number belongs to and returns circle details.

UAT vs Production

  • UAT tokens (environment: uat via client-credentials) return a sample response. No aggregator call, fee = 0.
  • Production tokens call the live aggregator. Fee is deducted from your wallet.

Access & billing (Production)

  • Admin must enable operator_fetch for your account and set a per-call fee.
  • Fee is deducted from your developer wallet before the provider call.
  • On provider failure, the fee is refunded automatically.
  • Provider credentials are applied server-side — never send EkycHub username/token from the client.

Mobile opcodes

  • A — Airtel
  • V — Vodafone
  • J — Jio
  • BT — BSNL Topup
  • BS — BSNL Special

Circle codes

  • 105 — JHARKHAND
  • 104 — MIZZORAM
  • 103 — MEGHALAY
  • 102 — GOA
  • 101 — CHHATISGARH
  • 100 — TRIPURA
  • 99 — SIKKIM
  • 49 — AP
  • 95 — KERALA
  • 94 — TAMIL NADU
  • 40 — CHENNAI
  • 06 — KARNATAKA
  • 52 — BIHAR
  • 16 — NESA
  • 56 — ASSAM
  • 53 — ORISSA
  • 51 — West Bengal
  • 31 — KOLKATTA
  • 70 — RAJASTHAN
  • 93 — MP
  • 98 — GUJARAT
  • 90 — MAHARASHTRA
  • 92 — MUMBAI
  • 54 — UP(East)
  • 55 — J&K
  • 96 — HARYANA
  • 03 — HP
  • 02 — PUNJAB
  • 97 — UP(West)
  • 10 — DELHI

Body

application/json required

Mobile Operator Find request body

Schema

{
    "type": "object",
    "required": [
        "mobile",
        "orderid"
    ],
    "properties": {
        "mobile": {
            "type": "string",
            "description": "10-digit mobile number"
        },
        "orderid": {
            "type": "string",
            "description": "Unique client order / request ID"
        }
    }
}

Example

{
    "mobile": "9431023126",
    "orderid": "OPF_001"
}

Responses

  • 200 · application/json default

    Successful response

    Example

    {
        "fee": 0,
        "data": {
            "circle": "Bihar",
            "number": "9431023xxx",
            "company": "Jio",
            "orderid": "OPF_001",
            "circle_code": "52"
        },
        "status": "success",
        "message": "UAT sample — operator fetched. Use production credentials for live aggregator data.",
        "wallet_balance": 1000
    }

Rate Limits

60/min