Skip to main content
API access

Request API access

Two ways to start with the Tripgic travel API: book a call with our team, or send us your requirements in writing. Both lead to sandbox credentials and a plan for your integration.

Choose how to request API access

Schedule a meeting

Talk to our team on a video call and leave with a plan for your integration.

  • You want a walkthrough of the API and products
  • You want to discuss pricing, volume or contract terms
  • You are ready to plan go-live with our engineers
Schedule a meeting

Opens our booking page in a new tab. Pick any open slot.

Submit a query

Send your requirements in writing and our sales team replies by email.

  • You prefer email over a call, or work across time zones
  • You need a written proposal to share internally
  • You want to share products and volumes before talking
Submit a query

Takes about two minutes. You get a copy of your inquiry by email.

Submit a query

Fields marked * are required. The rest helps us prepare a useful reply.

The query form is not available right now. Please schedule a meeting instead and we will pick up your request from there.

Schedule a meeting

Requesting API access: common questions

Should I schedule a meeting or submit a query?

Schedule a meeting if you want a walkthrough, want to discuss pricing or volumes live, or are ready to plan go-live. Submit a query if you prefer email, need a written proposal to share internally, or want to send your requirements before talking.

What happens after I submit a query?

Your query goes to the Tripgic sales team and you receive a copy by email with an inquiry reference. Sales replies by email with next steps, pricing and any questions about your integration.

Which APIs can I request access to?

Flights (GDS, NDC and low-cost carriers), hotels, activities, tour packages, transfers, trains, travel eSIM, visa, airport services such as lounge, fast track and meet & greet, and sports & events tickets.

Is there a sandbox?

Yes. Approved partners receive sandbox credentials so they can build against the same schema used in production before going live.