​

Travelese Engine API

The Travelese Engine API provides a unified interface to search, book, and manage flights across multiple providers. Our API normalizes data from different sources into a consistent format, making it easy to integrate with various flight providers through a single API.

​

Base URL

Travelese Engine API is built on REST principles and is served over HTTPS. To ensure data privacy, unencrypted HTTP is not supported.

The Base URL for all API endpoints is:

https://engine-api.travelese.ai

​

Authentication

All API endpoints require authentication using a Bearer token. Include your API key in the Authorization header of each request:

Authorization: Bearer your-api-key

To obtain an API key, please contact our support team.

​

Rate Limiting

The API implements rate limiting to ensure fair usage:

• 100 requests per minute per API key
• 1000 requests per hour per API key

When you exceed these limits, you’ll receive a 429 Too Many Requests response.

​

Supported Providers

The Engine API currently integrates with the following providers:

• Amadeus: Access to traditional GDS inventory and full-service carriers
• Duffel: Direct connections to airlines through NDC, offering rich content and direct distribution

​

Response Format

All responses follow a standardized JSON format:

{
  "success": true,
  "data": {
    // Response data specific to the endpoint
  },
  "error": null
}

In case of errors:

{
  "success": false,
  "data": null,
  "error": {
    "code": "ERROR_CODE",
    "message": "Human-readable error message"
  }
}

​

Common Error Codes

• INVALID_CREDENTIALS: Invalid or missing API key
• RATE_LIMIT_EXCEEDED: Rate limit exceeded
• INVALID_REQUEST: Invalid request parameters
• PROVIDER_ERROR: Error from underlying provider
• INTERNAL_ERROR: Internal server error

​

Best Practices

1. Implement Retry Logic: For temporary failures, implement exponential backoff
2. Cache Responses: Cache search results according to our caching guidelines
3. Handle Rate Limits: Monitor rate limit headers and adjust request rates
4. Validate Input: Ensure all required parameters are provided and properly formatted
5. Error Handling: Implement proper error handling for all possible response codes

​

Versioning

The API uses semantic versioning. The current version is accessible at:

https://engine-api.travelese.ai/v1/

Breaking changes will be introduced in new major versions, with appropriate migration periods.

​

Support

For technical support or questions about the API:

• Email: [email protected]
• Documentation Issues: GitHub Repository
• Status Page: status.travelese.ai

​

SDKs and Libraries

Official SDKs are available for:

• JavaScript/TypeScript: @travelese/engine-sdk
• Python: travelese-engine

​

Changelog

Keep track of API changes and updates in our changelog.