Discuss a booking integration around your workflow
Discuss booking integration requirements with ONNN. Journey requests are reviewed by the team; API access and automation require a separate agreement.
Commercial arrangements are discussed directly with the team.
Start with the process you want to connect
Describe where a travel request begins, which system owns the itinerary and who approves it. Identify the data that needs to be passed and the acknowledgement your staff need before they consider a request received.
Agree on the operational states
Receipt of a request, a quote, acceptance and a confirmed booking are different events. An integration needs to preserve those distinctions, including what happens when a request changes or an upstream service is unavailable.
Discuss access before implementing
The public ONNN site does not issue developer credentials or promise a self-service booking API. Contact the team with your proposed use case, security requirements and expected volume. Access, supported operations and commercial terms must be agreed separately.
Contact the Zayn Limousine team
For company and partnership enquiries, email the operating company. Include the type of enquiry and the information needed to discuss it.
Email the teamPlan the next part.
Discuss your company travel requirements
Discuss company travel, recurring chauffeur requests and coordinated itineraries with ONNN. Share your routes, passenger needs and billing requirements.
Business travel with the details in one place
Prepare business travel requests with ONNN. Share passenger contacts, meeting addresses, timing and billing details so each journey can be reviewed clearly.
Transport requests for company travel
Arrange company travel enquiries through ONNN with clear passenger, organiser and billing details. Discuss recurring or coordinated journeys with the team.