MoovLogic BookingAPI
A RESTful JSON API for requesting ride prices, creating bookings, and managing journeys programmatically. Designed for external partners, travel platforms, and internal applications.
What you can build
| Use case | External partner | Internal app |
|---|---|---|
| Display live price quotes to customers | ✓ | ✓ |
| Create and manage bookings | ✓ | ✓ |
| List available vehicle types with images | ✓ | ✓ |
| Update ride status in real time | ✓ | ✓ |
| Retrieve booking details by reference | ✓ | ✓ |
| Cancel or amend a booking | ✓ | ✓ |
Who is this for?
Any business that wants to embed MoovLogic ride bookings into their own platform — travel agents, hotel concierge systems, corporate travel tools, or white-label booking engines. You get a single API for pricing, booking creation, and journey management.
How it works
- Obtain an API key and secret from your MoovLogic account manager.
- Exchange them for a 24-hour JWT at
/api/v1/auth/token. - Include the token as a
Bearerheader on every subsequent request. - Call
/api/v1/pricing/quotesto retrieve live fare estimates. - Call
POST /api/v1/bookingsto confirm the booking. - Use the returned
tagNameto retrieve, update, or cancel the booking.
https://api.moovlogic.com. All requests and responses use JSON with UTF-8 encoding.Base URL and versioning
https://api.moovlogic.com/api/v1/
All endpoints are prefixed /api/v1/. Breaking changes will be versioned under /api/v2/
with a minimum 90-day deprecation notice for v1.
Rate limits
| Policy | Limit | Applies to |
|---|---|---|
| AuthPolicy | 10 requests / minute | POST /api/v1/auth/token |
| ApiPolicy | 60 requests / minute | All other endpoints |
429 Too Many Requests. Implement exponential back-off — wait at least 1 second before retrying, doubling on each attempt.Health check
/api/ping
Returns 200 OK with body "pong" when the API is reachable. Use this to test connectivity before making authenticated requests.