Parking Events Upload Service
API for sending INRIX multiple Parking Events (real-time or historical) in a single JSON POST request.
The Parking Events Upload Service consumes the uploaded data asynchronously after responding to the POST request.
Response times should be approximately 250 milliseconds with the response result referring only to receipt of a data payload and not to the validity of sent data.
Providers can make multiple, simultaneous connections to the Parking Event Upload Service using either a single access token or multiple access tokens.
The service has required fields (such as lat/lon, event, anonymous device ID, and timestamp) as well as optional fields.
You must contact INRIX before using optional fields to ensure compliance with privacy standards.
The production endpoint, which should only be used with real data, is: https://appsvc-ingest.inrix.io/v1/parkdatastream
For testing purposes (including sending test data) the “beta” endpoint is available: https://appsvc-ingest.beta.inrix.io/v1/parkdatastream
The beta endpoint should not be used for load testing, since it has 10X less capacity.
|accessToken||Query||String||A valid access token provided from the GET appToken API response. Alternatively, the accesstoken can be added to the request header instead of a url parameter using format 'Authorization: Bearer xxxx.xxx.xxxx'.|
|Content-Type||Header||String||must be 'application/json'|
|Content-Encoding||Header||String||use 'gzip' to indicate gzip encoding (optional)|
|rid||Body||String||A optional unique identifier for the request|
|dat||Body||Array||Data records. While larger requests are handled, the recommended batch size is 4000-5000 records per request (which will typically be ~1.5MB).|
Example Datastream RequestQuery