Ola Corporate API

Name: Ola Corporate API API
Brand: Ola Corporate API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask ManagementapiKey12 EndpointsREST

For Agents

Manage corporate users, retrieve ride history, download ride invoices, and configure expense codes on the Ola Corporate platform. API-key authentication via X-CORPORATE-TOKEN header.

Quickstart

Get started with Ola Corporate API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list Ola corporate rides"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Ola Corporate API API.

Add, update, and delete individual corporate users so HR systems can keep ride entitlements aligned with employment status

Bulk-upsert a batch of corporate users in a single call to support HRIS-driven provisioning at scale

List corporate rides with filters and pagination to power monthly travel reports and audit trails

Download a per-ride invoice that finance teams can attach directly to journal entries

GET STARTED

Start building with Ola Corporate API API

Explore with Jentic

View OpenAPI Document

Use for: I need to add a new employee to our Ola Corporate account, List all corporate rides taken in the last month, Retrieve the invoice for a specific corporate ride, I want to bulk-upload a CSV of new employees to Ola Corporate

Not supported: Does not handle consumer ride booking, driver onboarding, or non-Ola transport modes — use for Ola Corporate user, ride, invoice, and expense-code management only.

Jentic publishes the only available OpenAPI document for Ola Corporate API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Ola Corporate API, keeping it validated and agent-ready. The Ola Corporate API lets businesses manage employees, rides, invoices, and expense codes on the Ola Corporate ride-booking platform. It exposes 12 endpoints for adding or removing corporate users individually or in bulk, listing rides taken under a corporate account, downloading per-ride invoices, and managing expense codes that route ride spend into the right cost centre. Authentication is handled via an X-CORPORATE-TOKEN header issued to registered Ola Corporate partners.

Use Cases

Patterns agents use Ola Corporate API API for, with concrete tasks.

★ HRIS-Driven User Provisioning

Sync the corporate ride entitlement list with the HR system so that new joiners gain Ola access on day one and leavers are removed automatically. The bulk upsert endpoint handles batches of users in a single call, which keeps the sync job simple even for large companies.

Read the latest active employee list from the HRIS, then call POST /v1/api/corporate/users with the bulk payload to add or update users, and DELETE /v1/api/corporate/user for any leavers.

Monthly Expense Reconciliation

Pull every corporate ride for the previous month, group by expense code, and reconcile against the company's accounting system. The download invoice endpoint produces a per-ride invoice that finance can attach to the journal entry, removing manual export work.

Call GET /v2/api/corporate/rides with the previous-month date range, then for each ride call GET /v1/api/corporate/rides/downloadInvoice and post the invoice plus expense code into the accounting system.

Expense Code Lifecycle Management

Spin up and retire expense codes as cost centres change, and adjust which employees are allocated to which code over time. The dedicated PATCH operation on the expense code endpoint handles allocation changes without rewriting the whole expense code record.

Call POST /v2/api/corporate/expenseCode to create a new code, PATCH /v2/api/corporate/expenseCode to add user allocations, and DELETE /v2/api/corporate/expenseCode when the cost centre is retired.

AI Agent Travel Reporting via Jentic

An AI agent answers questions like 'how much did the sales team spend on Ola last quarter?' by searching Jentic for the rides operation, calling it with the right filters, and aggregating the results. The agent does not need to know the path or the header name — Jentic returns the schema and credentials are injected at execution time.

Search Jentic for 'list Ola corporate rides', load the GET /v2/api/corporate/rides operation, execute it scoped to the requested team, and summarise the spend in natural language.

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for ola corporate api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/api/corporate/user

Add a new corporate user

POST

/v1/api/corporate/users

Add or update users in bulk

GET

/v2/api/corporate/rides

List corporate rides (v2)

GET

/v1/api/corporate/rides/downloadInvoice

Download invoice for a ride

POST

/v2/api/corporate/expenseCode

Create an expense code

PATCH

/v2/api/corporate/expenseCode

Adjust expense code allocation

POST

/v1/api/corporate/user

Add a new corporate user

POST

/v1/api/corporate/users

Add or update users in bulk

GET

/v2/api/corporate/rides

List corporate rides (v2)

GET

/v1/api/corporate/rides/downloadInvoice

Download invoice for a ride

POST

/v2/api/corporate/expenseCode

Create an expense code

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Ola Corporate X-CORPORATE-TOKEN is stored encrypted in the Jentic vault (MAXsystem). Agents receive a scoped execution handle — the raw partner token is injected into the header at call time and never enters the agent's prompt or logs.

Intent-based discovery

Agents search by intent (e.g., 'list Ola corporate rides' or 'add corporate user') and Jentic returns the matching operation with input and response schemas, so the agent picks the right endpoint without browsing Ola partner docs.

Time to first call

Direct Ola Corporate integration: 2-4 days for partner onboarding, auth wiring, and bulk-user error handling. Through Jentic: under 1 hour once the partner token is provisioned — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Ola Cabs API

Consumer-facing Ola Cabs API for ride booking and tracking outside the corporate context.

Choose the consumer Ola API when the workflow is individual rider booking; use Ola Corporate when expense routing and corporate user lifecycle are required.

Alternative

Lyft API

US-focused ride-hailing platform with developer APIs for ride booking and history.

Use Lyft when the workflow is US-only and consumer-facing; use Ola Corporate when the requirement is India-based corporate ride spend management.

Complementary

Xero Accounting API

Accounting platform that can ingest reconciled Ola Corporate ride invoices as bills or expenses.

Pair with Ola Corporate when an agent needs to push reconciled ride spend into a general ledger.

FAQs

Specific to using Ola Corporate API API through Jentic.

Why is there no official OpenAPI spec for Ola Corporate API?

Ola does not publish an OpenAPI specification for its corporate platform. 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 at https://app.jentic.com/sign-up.

What authentication does the Ola Corporate API use?

The Ola Corporate API uses an API-key scheme: every request must include an X-CORPORATE-TOKEN header containing the partner key issued by Ola. Through Jentic the token is held in the encrypted vault and added to the header at execution time, so it never enters the agent's context.

Can I bulk-add corporate users with the Ola Corporate API?

Yes. POST /v1/api/corporate/users accepts a batch payload that adds or updates multiple users in a single call, which is the recommended path for HRIS sync jobs rather than calling the single-user POST repeatedly.

How do I download an invoice for a specific ride?

Call GET /v1/api/corporate/rides/downloadInvoice with the ride identifier returned by the rides listing endpoint. The response is the invoice payload that can be attached to a finance record.

What are the rate limits for the Ola Corporate API?

The OpenAPI spec does not declare numeric rate limits. Treat HTTP 429 responses as authoritative and back off according to the Retry-After header where present, and confirm production limits with Ola Corporate before high-volume sync jobs.

How do I list corporate rides through Jentic?

Search Jentic for 'list Ola corporate rides', load the GET /v2/api/corporate/rides operation, and execute it with your date range and filters. Jentic returns the operation schema so the agent does not need to parse Ola documentation.