MultiTEL
Developers

GET/v3/getmobilecount/{prefix_id}

Check mobile inventory for an exchange

Get a point-in-time mobile inventory count for the NPA/NXX represented by an eligible prefix. This is an availability hint, not a reservation or a purchase guarantee.

On this page
  1. Choose a supported prefix
  2. Use the count as a hint
  3. Distinguish zero stock from a failed lookup
  4. Request
  5. Response
  6. Errors
  7. Availability and side effects

Choose a supported prefix

Use a current individual mobile prefix from discovery. This endpoint is intended for NANPA exchanges: an NPA identifies the area code, and an NXX identifies the exchange. An area-code-only prefix is too broad. Do not send grouped display IDs or infer support for another country because its prefix contains enough digits.

Use the count as a hint

Read response.count, with response.npa and response.nxx identifying the exchange. This is the coverage service's snapshot, not stock held for your account. Confirm actual numbers, applicable quotes and any registration requirements before ordering. A successful count never authorizes a purchase.

Distinguish zero stock from a failed lookup

A successful count of zero differs from an API error. Inspect status.code and status.msg as well as the HTTP status. Treat a timeout or failed lookup as unknown availability and retry later with backoff.

Request

Use your enabled API account credentials over HTTPS. Basic authentication and enabled API-account bearer tokens are supported; account restrictions apply.

GET with the prefix identifier in the URL path. There are no documented query or body parameters.

curl --fail-with-body --silent --show-error \
  --user "$API_USER:$API_PASSWORD" \
  "https://api.multitel.net/v3/getmobilecount/$PREFIX_ID"
Path parameters
NameTypeRequiredDescription
prefix_idstringYesCopy the individual prefix ID from the discovery response. Use a supported NANPA mobile prefix containing an area code (NPA) and exchange (NXX), not an area-code-only or grouped summary ID. Treat the identifier as opaque.

Response

Check status.code in the JSON body as well as the HTTP status. A successful response has status.code 200 and status.msg Results. response is an object, not a list: count is an integer inventory snapshot; npa and nxx are three-character strings. status.results is not present for this associative object. A count of 0 means the coverage lookup had no matching exchange or returned zero stock; it does not prove that all suppliers or other discovery routes have no numbers.

Illustrative response shape; not live account data or a current quote.

{
  "status": {
    "code": 200,
    "msg": "Results"
  },
  "response": {
    "count": 42,
    "npa": "212",
    "nxx": "555"
  }
}

Errors

  • 404: Provider disabled: mobile inventory coverage is unavailable on the service.
  • 404: Invalid prefix ID: obtain a current individual prefix ID from discovery.
  • 404: Invalid prefix: the stored prefix does not contain enough digits for an NPA/NXX lookup.
  • 500: Inventory coverage failed: the upstream lookup did not return a successful coverage result. Retry later with backoff; a failure is not a stock count of zero.

Availability and side effects

  • The operation checks inventory and does not place an order, reserve numbers or debit a purchase amount.
  • Stock may change immediately. The coverage count is not adjusted to promise account-specific purchasability or the same length as the next number-search response.
  • A lookup contacts the coverage service and can take time. Do not repeatedly poll every prefix, or treat a timeout/error as successful zero stock.