Coverage API
Description
The CostQuest Coverage API provides access to FCC BDC coverage information by location_id for fixed data and h3_res9_id for mobile data. The source data is updated every 6 months and is synchronized with the FCC Broadband Data Fabric Releases.
Retrieving BDC Fixed Coverage Information
Available vintages can be identified using the coverage/vintages API which returns an array of valid vintage strings.
curl 'https://api.costquest.com/coverage/vintages?type=bdc' -H 'Authorization: <token_type> <access_token>'
To retrieve fixed coverage information for a location_id use the coverage/bdcfixed API. The only required parameter is a valid location_id (example: 1000000005). If a vintage is not provided, the most recent available vintage will be used.
curl 'https://api.costquest.com/coverage/bdcfixed?location_id=1000000005' -H 'Authorization: <token_type> <access_token>'
The response is provided as a JSON array of objects with each object being one record.
[
{
"location_id": "1000000005",
"provider_id": 430076,
"frn": "0026043968",
"brand_name": "Starlink",
"technology_code": 61,
"max_advertised_download_speed": 220,
"max_advertised_upload_speed": 25,
"low_latency": 1,
"business_residential_code": "X",
"coverage": 1
},
{
"location_id": "1000000005",
"provider_id": 340070,
"frn": "0028957306",
"brand_name": "Point Broadband Fiber Holding LLC",
"technology_code": 50,
"max_advertised_download_speed": 1000,
"max_advertised_upload_speed": 1000,
"low_latency": 1,
"business_residential_code": "X",
"coverage": 1
}
]
The fields match the names and definitions from the publicly available FCC BDC Data Documentation.
Retrieving BDC Mobile Coverage Information
To retrieve mobile coverage information for an h3_res9_id use the coverage/bdcmobile API. The only required parameter is a valid h3_res9_id (example: 8948c9b3547ffff). If a vintage is not provided, the most recent available vintage will be used.
curl 'https://api.costquest.com/coverage/bdcmobile?h3_res9_id=8948c9b3547ffff' -H 'Authorization: <token_type> <access_token>'
The response is provided as a JSON array of objects with each object being one record.
[
{
"h3_res9_id": "8948c9b3547ffff",
"frn": "0003766532",
"providerid": 130077,
"brandname": "AT&T",
"technology": 400,
"mindown": 5,
"minup": 1,
"minsignal": -120,
"environment": 0
}, {
"h3_res9_id": "8948c9b3547ffff",
"frn": "0006945950",
"providerid": 130403,
"brandname": "T-Mobile",
"technology": 400,
"mindown": 5,
"minup": 1,
"minsignal": -100,
"environment": 0
}
]
The fields match the names and definitions from the publicly available FCC BDC Data Documentation.