INRIX documentation logo DOCUMENTATION


GET Get an app token from


Name Located in Description Type
Accepts header 'application/json' or 'application/xml' String
appId query Your designated app_id String
hashToken query Your hashed access token for your app String


200 Success
    "copyright": "Copyright INRIX Inc. 2015",
    "versionNumber": "v1",
    "createdDate": "2015-06-04T22:58:39.039099Z",
    "responseId": "f5ba0b34-06e9-40de-af8a-8bb008fc3454",
        "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhcHBJZCI6ImVjOWM3ZDAwLWUwNjUtNDc1OS05M2UyLWI3MWJhMmQ0MTAyYSIsIkV4cGlyeSI6IjIwMTUtMDYtMDVUMjI6NTg6MzkuMDcwMzQ5N1oiLCJleHAiOjE0MzM1NDUxMTksInJvbGUiOiJzZXJ2aWNlIn0.5fL8TL9z6hq2smrpbFhZE3S2CATTvhYNHgzFa5TQtzE",
        "expiry": "2015-06-05T22:58:39.0703497Z"

Successful requests to INRIX APIs requires API-level proper authentication. The APIs support two API-level authentication methods:

  1. an access token-based method in which a client will use an app_id and an app_key to request a 24-hour access_token
  2. a legacy hashed request in which a client uses a hashed string created using request data and an api_key to authenticate each request

Additionally, requests to create a reservation on behalf of a user will require User-level authentication in order to create the request. The Off-Street Payments API supports two User-level authentication methods:

  1. Session/Cookie-based authentication
  2. Basic HTTP Authentication i.e. username/password

This UAS token can be used in the query string with the key accessToken or can be added to the header like so: Authorization: Bearer {UAS-TOKEN}.

Facebook Authentication

Instead of submitting username:password in Auth Header, must use email:accessToken.