canonical: https://jentic.com/apis/optimumcozum.com/optimumcozum

# Optimumcozum LeasePlan API

The Optimum Cozum LeasePlan API lists vehicle damage claim files from the ORP repair-tracking platform, so a fleet or leasing team can see where each car sits between notification, expert approval, repair, and delivery. A single read operation filters files by file code, uid, workflow status, and date windows for creation, service check-in, delivery, and last control. Each returned file carries the reporting contact, claim type, estimated and actual delivery dates, whether a temporary replacement car was requested, and the service and call-center notes recorded against it.

## For AI agents

Look up LeasePlan vehicle damage claim files on the Optimum Cozum ORP platform and filter them by status such as waiting-for-expert-approval, ready-to-repair, or delivered, or by creation, service check-in, and delivery date ranges.

## Scope

Does not create or update claim files, book service appointments, process insurance payouts, or report vehicle locations. Use for reading LeasePlan vehicle damage claim file status only.

## Capabilities

- Track vehicle damage claim files through repair stages such as in-service, waiting-for-expert-approval, ready-to-repair, and delivered using the status filter
- Find claim files opened within a date window with the createdAtFrom and createdAtTo query parameters
- List vehicles that checked into a service shop in a period using serviceCheckInAtFrom and serviceCheckInAtTo
- Check delivered or due repairs by comparing estimatedDeliveryDate and deliveryDate on each file filtered by deliveryAtFrom and deliveryAtTo
- Retrieve one claim file by its code or uid to read the reporting contact, claimType, serviceNotes, and temporaryCarRequested flag

## Use cases

### Agent status checks on repair claim files

A fleet coordinator asks their agent which damaged vehicles are still blocked. The agent calls the claimDetails operation through Jentic with status set to waiting-for-expert-approval or waiting-for-missing-documents and returns the matching files with their reporting contact and estimated delivery date. Because the credential is injected by your own Jentic One instance, the agent never handles the ORP username and password.

Example prompt: Call GET /claimDetails with status 'waiting-for-expert-approval' and summarise each returned file's code, contactPersonName, and estimatedDeliveryDate

### Delivery reporting for repaired vehicles

Leasing operations teams need to know which repaired cars were handed back and whether they met the estimated date. Filtering claim files by deliveryAtFrom and deliveryAtTo returns each file's estimatedDeliveryDate and deliveryDate, so the gap between promise and handover can be reported per file without exporting from the ORP dashboard.

Example prompt: Call GET /claimDetails with deliveryAtFrom '2026-10-01' and deliveryAtTo '2026-10-31', then list files where deliveryDate is later than estimatedDeliveryDate

### Service shop intake review

Service managers review which vehicles entered the shop in a period and what the driver asked for. The serviceCheckInAtFrom and serviceCheckInAtTo filters return the files checked in during that window, and each file includes customerDemandsFromService and customerDemandsFromCallCenter so requests made by phone and at the counter can be compared.

Example prompt: Call GET /claimDetails with serviceCheckInAtFrom '2026-11-01' and serviceCheckInAtTo '2026-11-07', then report each file's code, claimType, and customerDemandsFromService

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/claimDetails` | List claim files filtered by code, uid, status, or date ranges |

## Key resources

- **Claim files** — Vehicle damage claim files with workflow status, contact details, claim type, delivery dates, service notes, and replacement-car flag, read through one filtered list operation

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 0 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 15 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 0 / 100
- **View full report:** https://jentic.com/apis/optimumcozum.com/optimumcozum/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the LeasePlan API by hand means handling HTTP Basic credentials for the ORP integration path and decoding Turkish-labelled filters and nested date objects yourself. Through Jentic you install once, import it from the API Directory, store the username and password once, and your agent calls it.
- **Permission scoping:** The API exposes a single read operation on claim files, and the filters travel as query parameters rather than resource ids in the path, so rules bound which operations your agent may call, not which claim file. Allowing claimDetails gives the agent read access to claim lookups and nothing more.
- **Credential handling:** Your ORP username and password are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find claim files waiting for expert approval', and Jentic returns the claimDetails operation with its input schema so the agent fills the right status and date filters without reading the Turkish reference.

## Related APIs

- **Fleetwire** — Vehicle rental and fleet booking management with booking status changes and charges
- **NetworkFleet API** — Fleet telematics with vehicle locations and trip history
- **Tesla Fleet API** — Vehicle and energy fleet data for Tesla-owned assets

## FAQ

### What authentication does the LeasePlan API use?

The LeasePlan API on Optimum Cozum ORP authenticates with HTTP Basic auth per its OpenAPI spec: a username and password sent in the Authorization header. Through Jentic the username and password are stored encrypted by your own Jentic One instance and injected at call time, so they never enter the agent's prompt or logs.

### Can I filter LeasePlan claim files by repair status?

Yes. The claimDetails operation accepts a status query parameter with values such as available-for-sending-to-service, in-service, waiting-for-expert-approval, waiting-for-missing-documents, ready-to-repair, started-to-repair, and delivered. You can combine it with date windows such as createdAtFrom and createdAtTo, which take dates in Y-m-d format.

### What does each claim file record contain?

Each file in the output array includes its id and code, the createdAt timestamp, the reporting contact's name, phone number, and email, the claimType, estimatedDeliveryDate and deliveryDate, the temporaryCarRequested flag, serviceNotes, and the customer requests captured at the service shop and by the call center.

### How do I list LeasePlan claims waiting for approval through Jentic?

Install Jentic One, add the LeasePlan API from the Jentic API Directory, and store your ORP username and password once. Your agent then searches for 'list LeasePlan claim files by status', gets the claimDetails operation with its input schema, and calls GET /claimDetails with status set to waiting-for-expert-approval. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a LeasePlan API MCP server?

You don't need an MCP server to give your agent the LeasePlan API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

### Can I limit what my agent is allowed to do with the LeasePlan API?

Yes. Write a rule that allows the claimDetails read operation, and your agent can look up claim files by status or date and nothing else through this binding. Every call it makes is recorded in your own Jentic One audit log.