For developers
Travel API documentation and integration
Approved partners receive credentials, full reference documentation and a named integration contact who supports your developers from first request to go-live.
Documentation
What your engineers receive.
Documentation is shared with approved partners after the scoping call.
- API overviewOn request
Products, capabilities and booking lifecycle.
- Integration workflowOn request
Recommended sequence from search to post-booking.
- Authentication & securityOn request
Credential management and access controls.
- Testing environmentTo confirm
Test access for approved partners, where available.
- Reference documentationOn request
Full request and response specifications.
- Onboarding supportIncluded
A named contact through build and certification.
# Illustrative request shape only.
# Endpoints and schemas are published in the
# Avunzo developer documentation.
POST $AVUNZO_BASE_URL/<search-resource>
Authorization: Bearer <access_token>
Content-Type: application/json
{
"product": "flight",
"origin": "LHE",
"destination": "JED",
"departureDate": "2026-11-14",
"passengers": { "adults": 2, "children": 1 }
}Conventions
Learn the API once.
Every product follows the same patterns, so each new product is an extension of work you have already done.
One authentication method
The same credentials and access model for every product you enable.
One booking lifecycle
Search, price, book and manage follow the same sequence across products.
Consistent data
Shared conventions for requests and responses across flights, hotels and services.
Security reviewed at onboarding
Credential management and access controls are reviewed with your team before go-live.
Integration process
From first conversation to live bookings.
- 1Day 1
Request access
Share your business details and the products you want to offer.
- 2Discovery
Scope the integration
We review your platform, workflows and requirements with your team.
- 3Build
Integrate & test
Your developers build against documentation with our integration support.
- 4Launch
Certify & go live
We review your booking flows together, then switch on live access.
FAQ
Common questions
How do we get API credentials?
Request API access with your business details. After a scoping call and approval, we issue credentials and documentation to your team or technology partner.
Can a third-party developer build the integration for us?
Yes. Many travel businesses work with a technology partner. We support whoever is building, through scoping, build and certification.
Is there a test environment?
Test access is offered to approved partners where available for the product. We confirm test access during onboarding.
What happens before go-live?
We review your booking flows together. Once they work as agreed, we switch on live access.
Request documentation access
Share your business details and the products you plan to integrate. We reply within one business day.