Internet speed test
API Documentation

API Documentation

Guides and reference for the CoverageMap APIs: how requests, responses, authentication and usage work, and the endpoints and models of each API.

CoverageMap APIs give your applications the same cellular coverage and network performance data that powers CoverageMap.com. These docs are split in two: the Fundamentals explain what every API shares, and each API then has its own guides, endpoint reference and data models.

Available APIs

Choose an API to see its endpoints, datasets and pricing details.

APICoverageMap APIFCC coverage, crowdsourced speed tests and 0 to 10 summary scores for AT&T, Verizon and T-Mobile at up to 100 US locations per request.

How the APIs work

Every CoverageMap API is a JSON REST API served from the same base URL, https://enterprise.coveragemap.com/api/v1, and follows the same conventions:

  • Authentication uses an API key from your Enterprise dashboard, sent as a Bearer token.
  • Requests are versioned in the path and send JSON bodies.
  • Responses share one envelope with a status, messages and data.
  • Errors come back as readable messages in messages.errors, and rejected requests are never billed.
  • Usage is measured in units and shown in your dashboard as it happens.

Using these docs

Examples use YOUR_API_KEY as a placeholder for your key. Code samples are shown in cURL, JavaScript and Python and can be copied as is. Parameters and fields are described like this:

datasetsstring[]Required
A request parameter you must send.
countrystringOptional
A request parameter you can leave out.

Defaults to US.

idstringOptional
A response field that is left out of the response when it does not apply.
technologyobjectNullable
A response field that is always present but can be null.

New to the APIs? Follow the Quickstart to get a key and send your first request. Other Enterprise products, such as coverage tiles and embeddable maps, are documented inside the Enterprise dashboard.