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.