API
Connect DispHub with your business systems
Start integration planning with a real task: where an order comes from, what data your team needs and where the result should appear. Together we will define the available API connection and scope of work.
What should your integration achieve?
External booking sources
A website, partner service or internal company system. Describe the booking fields, who confirms the order and how the requester receives the outcome. We verify the available workflow before development.
Data for your team
CRM, accounting or internal analytics may need ride data. Define the fields, exchange frequency and access rules; the transfer method and availability are agreed for the specific system.
Payment workflows
Provider connection depends on the country, agreement and payment method you need. Agree on the payment workflow together with how its result is recorded in the order.
Learn moreDispHub workflow
Addresses, time, fare, assignment and event history connect the team’s work. Dispatchers can move from an active ride to its details and archive.
Learn more
Prepare your integration brief
Share the system description and documentation, a sample exchange without personal data, a list of fields and the responsible developer’s contact. This lets us assess compatibility and scope before connecting.
Discuss your launchFrom a requirement to a tested connection
Workflow and access
Agree on the source system, required data and permitted operations. Check existing capabilities and whether custom development is needed.
Development and testing
Test valid and invalid requests, repeated submissions and how results fit the workflow. Define acceptance criteria before launch.
Launch and ownership
Record who maintains each side of the connection and how changes are agreed. Timing and cost depend on the scope of the custom integration.
Before you launch
How do we get API documentation and access?
Contact us with your workflow and external system details. We will agree on available operations, documentation, access terms and required work for that scenario. This page does not provide a public endpoint catalogue.
Can we add a custom service?
We first review your workflow and check what existing settings cover. If a new algorithm is needed, its scope, timing and development cost are agreed separately.
Let’s plan your next step
Tell us about your operation, city and goals. We will show you the relevant DispHub tools and agree on the scope of your launch.
Discuss your launch