API Usage - Cab ID List

We have two API endpoints to provide partners access to all Cab IDs and expiration date that are present in our system as a reference list. This reduces the number of API requests needed to collect a list of all available Cab IDs that can be downloaded from our APIs.

The below endpoints are expected to be utilized in the following way: -

• Invoke the Get All Ingestion Dates API endpoint to get a list of all available ingestion dates in JSON format. This will let you see what all dates are available and detect when new cabs have been added.

• The Ingestion dates retrieved in step 1 will be used as a request parameter to Download all Cab IDs endpoint to get the of Cab IDs and the Cab Expiration Dates in CSV format.

• These files are incremental and will not have overlapping data. Once cab IDs for a date are downloaded, they will not be changed. Building a history of available cabs is highly advised to reduce the data redundancy.

• The combined list of all the Cab IDs is the master list of all cabs available for the partner to download and these can be downloaded from the Cab Download endpoint as long as the cab has not expired or has been deleted due to a GDPR deletion request.

• There may be some missing dates in the data. This is expected. If the data processing for a given day fails, there will be no new cabs added for that day. The cabs will be available in the next available ingestion date.

• In case the Cab IDs are being collected from various sources, it is highly advised that you use this API to validate that the cab exists in our system before attempting to download the cab. Our system has an automated rate limit on the bulk cab download endpoint which blocks the requests from a partner after 100 404's responses in a minute.