canonical: https://jentic.com/apis/olacabs.com/olacabs # Olacabs Ola Corporate API Jentic publishes the only available OpenAPI specification for Ola Corporate API, keeping it validated and agent-ready. The Ola Corporate API lets companies manage their employee ride programme on Ola Cabs across India, including onboarding corporate users, tracking ride history, downloading invoices, and allocating expense codes. It exposes 17 endpoints covering corporate user CRUD, bulk user upload, ride listings across two API versions, invoice downloads, and granular expense-code management with allocation and bulk operations. Authentication uses the X-CORPORATE-TOKEN header issued to corporate accounts. ## For AI agents Manage corporate Ola Cabs ride programmes - add or remove employees, pull ride history, download invoices, and assign expense codes for ride billing. ## Scope Does not handle consumer ride booking, driver onboarding, or fleet management - use for corporate ride programme administration only. ## Capabilities - Onboard or offboard corporate employees authorised to book Ola rides - Bulk-upload up to hundreds of corporate users in a single call - Pull v1 or v2 ride listings for reporting and reconciliation - Download corporate invoices as downloadable artefacts for accounting - Create and update expense codes used to tag rides at booking time - Allocate or revoke expense codes against specific corporate users in bulk ## Use cases ### Corporate Employee Onboarding When a new hire joins, automatically add them to the company's Ola Corporate account so they can book rides charged to the company. Use POST `/v1/api/corporate/user` for individual additions or POST `/v1/api/corporate/users/bulk` for batch HR system syncs. The bulk endpoint handles hundreds of employees in a single request, removing the need for click-by-click admin work. Example prompt: POST a new corporate user with name, mobile number, and home location to `/v1/api/corporate/user`, then verify the user appears in GET `/v1/api/corporate/users.` ### Monthly Ride Reconciliation Pull a full list of corporate rides for the previous month from `/v2/api/corporate/rides` and reconcile them against expense codes and employee assignments. The v2 endpoint returns richer ride metadata than v1, useful for finance teams running cost-centre reports across departments. Example prompt: Call GET `/v2/api/corporate/rides` with a date range covering the previous month and group results by expense code for a finance report. ### Expense Code Governance Maintain a clean, current list of expense codes that map rides to internal cost centres or projects. Use POST `/v1/api/corporate/expense-codes` to create codes, the bulk endpoints to import dozens at a time from a finance ERP, and POST `/v1/api/corporate/expense-codes/allocations` to bind codes to specific employees so they show up at booking. Example prompt: Create three expense codes (CLIENT, INTERNAL, EVENT) via POST `/v1/api/corporate/expense-codes/bulk`, then allocate them to the sales team via POST `/v1/api/corporate/expense-codes/allocations/bulk.` ### AI Agent Travel Operations Assistant An AI agent integrated through Jentic can manage a company's Ola Corporate account end to end - onboarding new joiners from the HRIS, generating monthly cost-centre reports, and downloading invoices for the accounting system. Jentic stores the X-CORPORATE-TOKEN encrypted, so the agent only sees scoped operation handles, not the raw token. Example prompt: Search Jentic for 'manage ola corporate users', load the user-management operations, and run a sync that adds 12 new employees while removing 3 leavers based on a CSV input. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/v1/api/corporate/user` | Add a corporate user | | POST | `/v1/api/corporate/users/bulk` | Bulk-add or edit corporate users | | GET | `/v2/api/corporate/rides` | List corporate rides (v2) | | GET | `/v1/api/corporate/invoices/download` | Download corporate invoice | | POST | `/v1/api/corporate/expense-codes/bulk` | Bulk-create expense codes | | POST | `/v1/api/corporate/expense-codes/allocations/bulk` | Bulk-allocate expense codes to users | ## Key resources - **Users** — Add, update, delete, list, and bulk-upload corporate employees on the Ola Corporate account. - **Rides** — Retrieve ride history with v1 and v2 endpoints, including driver, fare, and route metadata. - **Invoices** — Download corporate billing invoices as files for accounting workflows. - **Expense Codes** — Create, update, and delete expense codes; allocate them in bulk to users for ride tagging. ## Why Jentic - **Setup:** Wiring the Ola Corporate API by hand means setting up its static X-CORPORATE-TOKEN header, targeting the devapi.olacabs.com host, and navigating 17 endpoints across users, rides, invoices, and expense codes yourself. Through Jentic you install once, import Ola Corporate from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The Ola Corporate API carries its targets in the request body and query rather than the URL path, so scoping is by operation: you limit the agent to the operations it needs, such as reading corporate rides or downloading an invoice, and it can call nothing else. You choose the operations it may call, so adding a corporate user is not included unless you add it. - **Credential handling:** Your Ola Corporate token is stored once, encrypted, by your own Jentic One instance and injected into the X-CORPORATE-TOKEN header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'add a corporate user to Ola' or 'download a corporate invoice', and Jentic returns the matching Ola Corporate operation with its input schema so the agent calls the right endpoint without browsing the developer pages. ## Related APIs - **Lyft API** — US-focused ride-hailing platform with rider, driver, and business APIs. - **Twilio API** — Send ride confirmation SMS or driver-arrival alerts to employees. - **Salesforce API** — Sync Ola corporate ride data into CRM for client-visit logging. ## FAQ ### Why is there no official OpenAPI spec for Ola Corporate API? Olacabs does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Ola Corporate API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Ola Corporate API use? Every request must include the X-CORPORATE-TOKEN header, a static API key issued by Olacabs to your corporate account. Jentic stores this token in the encrypted vault and injects it at execution time, so agents never see the raw header value. ### Can I bulk-onboard employees with the Ola Corporate API? Yes. Use POST `/v1/api/corporate/users/bulk` to add or edit many employees in one call, which is the recommended path when syncing from an HRIS rather than calling `/v1/api/corporate/user` one record at a time. ### What are the rate limits for the Ola Corporate API? The OpenAPI spec does not document explicit rate limits. Treat the bulk endpoints as the preferred path for high-volume operations and contact Olacabs corporate support if you encounter throttling on user or ride listing calls. ### How do I tag a ride with an expense code through Jentic? Create the expense code with POST `/v1/api/corporate/expense-codes`, then allocate it to the relevant users via POST `/v1/api/corporate/expense-codes/allocations.` Through Jentic, search for 'allocate ola expense code' and the SDK returns both operations as a ready-to-execute pair. ### Does the Ola Corporate API include driver or fleet management? No. The Corporate API is scoped to the customer-side corporate ride programme (users, rides, invoices, expense codes). Driver onboarding and fleet operations are handled in a separate Ola partner programme and are not part of this spec. ### Can I limit what my agent is allowed to do with the Ola Corporate API? Yes. Because Jentic One runs self-hosted on your own infrastructure, your rules decide which of the 17 Ola Corporate operations the agent may call and which credentials it may use. Since this API carries its targets in the request body and query rather than the URL path, you scope by operation: you can allow the agent to read corporate rides or download an invoice while blocking everything else. Adding or removing a corporate user is not available to the agent unless you explicitly grant that operation.