Traffic Incidents API

Introduction

NextBillion.ai’s Traffic Incidents API provides users with detailed information about the traffic related incidents within a specified geographic area. The service provides users with a list of all incidents/road closures and their associated properties like - cause of incident, impacted roads, severity and probability of incident, start-end times for scheduled or planned closures and the impact on travel time or delays caused by a given incident. The service allows users to search for incidents in a given bounding box area along with other classifying inputs like - specific incident types or timings to receive all desired incident details.

GET

https://api.nextbillion.io/map/traffic_incidents?key={your_api_key}


Request Parameters

Loading..

Response Schema

Loading..

Sample Request

1
curl --location 'https://api.nextbillion.io/map/traffic_incidents?key=<your_api_key>&bbox=-83.1678800,39.9029016,-82.9004315,40.0967332&incident_validity=present'

Sample Response

1
{
2
"incidents": [...]
3
}

API Query Limits

  1. The maximum area of bbox that can be specified is 50000m (50 km²).
  2. The maximum number of IDs that can be provided for the id input list is 5.
  3. NextBillion.ai allows a maximum rate limit of 6000 queries per minute or 100 queries/second for continuous requests.
    Note: We can increase the quota if needed on request. Contact support@nextbillion.ai for more details.

API Error Codes

Response codeDescriptionAdditional notes
200Normal success case.Normal success case.
400Input validation failed.There is a missing or an invalid parameter or a parameter with an invalid value type is added to the request.
401APIKEY not supplied or invalidThis error occurs when the wrong API key is passed in the request or the key is missing altogether.
403APIKEY is valid but does not have access to requested resourcesYou might be querying for a geographical region which is not valid for your account or requesting a service which is not enabled for you.
404Requested host/path not foundThis error occurs when a malformed hostname is used.
422Could not process the requestA feasible solution could not be generated for the given set of locations or parameter configuration.
429Too many requestsQPM reached or API request count quota reached.
500Internal Service error.There was an internal issue with NextBillion.ai services. You can reach out to support@nextbillion.ai for an explanation.