Join Industry Leaders Using Yelowsoft
What Partner Bookings Cost Without API Automation
Without taxi API integration and a reliable taxi booking API, partner bookings do not flow into your system automatically. Your team must handle each booking manually, every day, across every partner, increasing effort and risk of errors.
Partner sends bookings by email or phone
Your team reads the email, opens the dispatch system, manually creates the booking. Multiplied by 40–100 partner bookings a day, this is hours of avoidable overhead that errors creep into.
Delay between booking and dispatch
Without an API, a partner booking placed at 11 pm remains unprocessed until morning. With an API, the booking reaches your dispatch dashboard in under 200 milliseconds at any hour, every day.
Partners constantly chase you for status updates
Without a two-way API and webhook system, partners call or email asking if a driver is assigned, if the trip started, if the booking was received. Each chase call is wasted time on both sides.
Commission tracking is a monthly manual reconciliation
Calculating commissions owed to or from each partner without API tracking means pulling spreadsheets together at month end. API commission tracking makes it automatic, real-time and error-free.
One API integration per partner replaces a daily manual process.
Connect a partner once — their bookings flow into your dashboard automatically, in real time, forever. No emails to check. No phone calls to take. No data to re-enter.
- Partner bookings in your dashboard under 200ms — zero manual steps required
- Two-way webhook sync — partners get real-time status without calling you
- Commission rate set per partner — calculated and tracked automatically per booking
- 24/7 booking receipt — no partner email to catch up on in the morning
- Fare quotes and availability via GET endpoints — partners can pre-check before booking
- Full API documentation and sandbox environment provided — partners integrate in days
<200ms
0
5
∞
How Partner Bookings Flow into Your Dashboard via API
From the moment a booking is placed on a partner platform to driver assignment and status confirmation, the entire process runs automatically from start to finish.
Partner Places Booking
Travel agency, OTA or mobility app creates a booking on their own platform.
API Push to Yelowsoft
Partner sends a POST request to Yelowsoft's REST API with full booking details.
Confirmed <200ms
Yelowsoft validates the request, creates the ride record and returns a booking ID instantly.
Driver Auto-Dispatched
Nearest available driver is assigned automatically. Booking appears in dispatch dashboard.
Status Pushed Back
Every status change including confirmed, driver assigned, started, and completed is pushed to partners through webhooks in real time.
Two Types of Partners Who Send Bookings via API
Yelowsoft’s booking API is designed to handle the two most common third party booking sources for taxi operators, including travel platforms and mobility applications.
Online Travel Agencies & Travel Management Companies
OTAs and corporate travel management companies use a taxi booking API to arrange ground transport as part of larger travel plans, including airport transfers, city to city rides, and hotel connections alongside flights and accommodation.
HOW THE BOOKING FLOW WORKS
API CAPABILITIES FOR OTAS
Ride-Hailing Apps & Transport Aggregators
Ride hailing platforms, white label mobility apps, and transport aggregators that require local fleet capacity are served by your drivers through Yelowsoft’s dispatch system.
HOW THE BOOKING FLOW WORKS
API CAPABILITIES FOR MOBILITY APPS
Complete Taxi Booking API Lifecycle from Request to Webhook
Here is a complete end to end taxi API integration flow showing what the partner sends, what Yelowsoft returns, and how status updates flow back automatically.
{
"pickup_address": "Gatwick Airport, South Terminal, RH6",
"destination_address": "Victoria Station, London SW1V",
"pickup_datetime": "2026-04-15T07:30:00Z",
"passengers": 1,
"luggage": 2,
"vehicle_type": "standard",
"passenger_name": "Sarah Williams",
"flight_number": "DA107",
"partner_ref": "TRIP-8842-WIL",
"commission_rate": 10
}{
"booking_id": "BKG-2026-0419",
"status": "confirmed",
"fare": 38.00,
"currency": "GBP",
"vehicle_type": "standard",
"partner_ref": "TRIP-8842-WIL",
"commission_amount": 3.80,
"eta_minutes": 8
}{
"event": "driver_assigned",
"booking_id": "BKG-2026-0419",
"driver_name": "Ahmad Khan",
"vehicle": "Toyota Camry · Silver · AR72 XYZ",
"driver_location": { "lat": 51.1557, "lng": 0.1821 },
"eta_minutes": 6
}{
"event": "trip_completed",
"booking_id": "BKG-2026-0419",
"fare_final": 38.00,
"duration_minutes": 34,
"distance_km": 47.2,
"commission_earned": 3.80
}Booking Created in Dashboard
Webhook Events Pushed to Partner
booking_confirmeddriver_assigneddriver_arrivedtrip_startedtrip_completedCommission Tracked Automatically
Technical Specifications & API Endpoints
Everything your development team needs to evaluate and integrate the Yelowsoft booking API.
Authentication
| Protocol | Bearer Token (API Key) |
| Scope | Per-partner API key |
| Format | Authorization header |
| Key prefix | yk_live_ / yk_test_ |
| Sandbox | Available on signup |
Performance
| Data format | JSON (UTF-8) |
| Booking confirm | < 200ms typical |
| Uptime SLA | 99.9% guaranteed |
| Rate limit | 1000 req/min per key |
| Retry policy | Exponential backoff |
Webhooks
| Transport | HTTPS POST |
| Events | 5 status events |
| Delivery | At-least-once |
| Retries | 3× with backoff |
| Signature | HMAC-SHA256 |
| Method | Endpoint | Description |
|---|---|---|
| GET | /v1/quote | Get a fare quote for a specific route, vehicle type and datetime before booking |
| GET | /v1/availability | Check real-time fleet availability for a given zone, vehicle type and pickup time |
| POST | /v1/bookings | Create a new booking from a partner platform — returns booking ID and confirmation within 200ms |
| GET | /v1/bookings/{id} | Retrieve full details and current status of any booking by ID |
| PATCH | /v1/bookings/{id} | Modify a pending booking — update pickup time, passenger count or vehicle type |
| DELETE | /v1/bookings/{id} | Cancel a booking before dispatch — cancellation policy applies per contract |
| GET | /v1/zones | List all operating zones and coverage areas configured for your account |
| POST | /v1/webhooks | Register a partner webhook endpoint URL to receive booking status event pushes |
| GET | /v1/partners/{id}/report | Pull commission report for a specific partner — bookings, revenue and commission amounts by date range |
What Operators Gain from API Booking Integration
From operators who connected their OTA and mobility platform partners to Yelowsoft via REST API.
0min
Manual work per API booking received from partner
<200ms
Booking confirmation response time from Yelowsoft API
2–5days
Typical partner integration time using provided API docs
500+
Operators using Yelowsoft booking channels globally
Testimonials
What Our Customers Say
Hear from operators who connected their partner platforms to Yelowsoft via API.
Okoye Ifeanyi, the CEO of CrabbyRide says he can offer cost-effective rides with the help of Yelowsoft. He is sharing his experience with the team and the software in the video.
Okoye Ifeanyi
Crabby Ride
Frequently asked questions
Yelowsoft offers a REST API over HTTPS with JSON support, API key authentication, and standard HTTP methods. It includes full documentation, webhook support, and a sandbox environment for quick and seamless integration.
Each partner API key includes a configurable commission applied per booking. Yelowsoft tracks it automatically, shows live summaries, and allows reporting via GET /v1/partners/{id}/report for any date range, exportable as CSV or PDF.
Basic integration using POST /v1/bookings and webhooks takes 2 to 5 days. Full setup with GET /v1/availability, GET /v1/quote, and reporting takes 1 to 2 weeks with sandbox and documentation support.
There is no limit on partner integrations. Create multiple API keys with unique commission and webhook settings. All bookings appear in one dashboard, and API access is included in your Yelowsoft subscription at no extra cost.
Yelowsoft offers GET /v1/quote for fare estimates and GET /v1/availability for driver availability and wait times. This ensures accurate pricing before POST /v1/bookings, reducing cancellations and improving booking reliability.
Yes. GET /v1/quote and GET /v1/availability provide real-time pricing and driver availability. These taxi booking API endpoints help partners reduce cancellations and ensure accurate bookings via POST /v1/bookings.
Connect Your Partners. Their Bookings, Your Dashboard, Real Time.
One API integration per partner replaces a daily manual process — forever. See Yelowsoft's booking API live in a 30-minute demo, or request access to the sandbox environment today.
