Getting Started with Travel Data Services

Sign in access our API documentation. Don't have an account? Request access.

Sign in
Picture

Introduction

iinside offers a REST API that provides both real time and historical data to assist your clients with their travel plans. The data is provided over an encrypted HTTPS connection and produces a JSON output by default or XML if specified in the request. An approved account is required to query the API, however all functions with example calls are available for viewing without logging in. Authenticated developers may also utilize our Sandbox, which produces simulated data for no charge. Please review the documentation on the individual methods for examples, as well as Try It Out functionality for logged in users.

Authentication

All iinside API requests require authentication. iinside will generate an application identifier and key pair upon account approval. These values must be passed on the query line with every request as app_id and app_key:

app_id=YourAppID&app_key=YourAppKey

Rate Limiting

iinside limits a single Application ID to 500 requests per minute to prevent abuse or Denial of Service (DoS) to other clients. This limit can be increased upon request as needed for the application. A user who hits this rate limit will be returned a response code of "403 Forbidden" with the message "Authentication Failed."

Caching

The data that iinside provides is constantly changing and should be queried every time it is needed for the most up to date information. Please see our Terms of Service for our caching policy.

Response Formats

Data produced by the iinside API is returned in JSON format by default, although XML is also available when requested in the header. Please see the individual API call documentation pages for example responses.

HTTP Status Codes

Code             Text                     Description
200                OK                       Successful request.
204                No content         The server successfully processed the request, but is not returning any content.
400                Bad request        The request was invalid or cannot be otherwise served.
403                Forbidden           Authentication was provided, but the authenticated user is not permitted to perform the requested operation.
404                Not found           The request resource could not be found but may be available again in the future.