canonical: https://jentic.com/apis/exclusivecars.ph/exclusivecars # Exclusivecars Ph Admin360 API The Admin360 API retrieves short-term car-rental reservation details for Hertz Philippines by transaction number. Its single operation returns the reservation together with the driver, vehicle, and billing details tied to it, as a JSON reservation response. It is a focused lookup endpoint for the Admin360 system rather than a booking or fleet-management surface. Access is authenticated with a bearer JWT. ## For AI agents Look up a Hertz Philippines short-term rental reservation by transaction number through Admin360, returning the reservation, driver, vehicle, and billing details in one call. ## Scope Does not handle creating, changing, or cancelling bookings, fleet management, or payments. Use for retrieving short-term rental reservation details by transaction number only. ## Capabilities - Look up a short-term rental reservation by its transaction_number via GET `/api/hertz_services/v1/admin360/shortterm/reservations/{transaction_number}` - Read the driver and vehicle details attached to a reservation in a single response - Read the billing details tied to a reservation for reconciliation or support follow-up ## Use cases ### AI agent reservation lookup A support assistant answers a renter's question by pulling their reservation on demand. Through Jentic it discovers the Admin360 lookup, passes the transaction number, and reads back the driver, vehicle, and billing details without an agent logging into Admin360. Jentic injects the bearer token at call time, so the agent never holds the credential. Example prompt: Search Jentic for 'look up a short-term rental reservation', then call GET `/api/hertz_services/v1/admin360/shortterm/reservations/{transaction_number}` with the renter's transaction number and summarise the details ### Billing reconciliation lookup Finance staff verifying a charge need the billing detail that sits behind a specific rental transaction. The Admin360 API returns that billing block alongside the reservation and vehicle, keyed on the transaction number, so a reconciliation job can confirm an amount against the source record. The single read keeps the integration simple and side-effect-free. Example prompt: Call GET `/api/hertz_services/v1/admin360/shortterm/reservations/{transaction_number}` for the disputed transaction and compare the returned billing details with the charge on file ### Customer-service reservation verification A contact-centre workflow confirms a caller's reservation before taking action. Admin360 returns the reservation, the driver on it, and the assigned vehicle from one transaction-number lookup, giving the agent enough to verify the caller and answer questions. Because the endpoint is read-only, it is safe to call on every verification. Example prompt: On an inbound call, call GET `/api/hertz_services/v1/admin360/shortterm/reservations/{transaction_number}` and read the driver and vehicle fields to verify the caller ## Key resources - **Short-term reservations** — Retrieve a reservation by transaction number with its driver, vehicle, and billing details ## 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:** 67 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 83 / 100 - AI-Readiness & Agent Experience: 39 / 100 - Agent Usability: 94 / 100 - Security: 75 / 100 - AI Discoverability: 75 / 100 - **View full report:** https://jentic.com/apis/exclusivecars.ph/exclusivecars/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 ``` ## Why Jentic - **Setup:** Wiring the Admin360 API by hand means obtaining and refreshing a bearer JWT, targeting the right host, and shaping the transaction-number lookup path yourself. Through Jentic you install once, import Admin360 from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Admin360 exposes a single read operation that takes the reservation's transaction_number in the URL path, so a rule can allow your agent just that lookup. You choose whether the operation is included, and because it is read-only the agent can read reservation details without changing anything. - **Credential handling:** Your Admin360 bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'look up a short-term rental reservation', and Jentic returns the Admin360 operation with its input schema so the agent supplies the transaction number and calls the right endpoint without browsing the reference docs. ## Related APIs - **Newbook OTA API** — Reservation and booking platform that creates and manages bookings, not just reads them - **Smily (BookingSync) API** — Rental booking management covering reservations, rentals, and billing across properties - **Wink API** — Broader travel inventory and booking API for assembling travel alongside car rentals ## FAQ ### What authentication does the Admin360 API use? The Admin360 API authenticates with a bearer JWT, per its OpenAPI spec, and the reservation lookup requires it. When you call it through Jentic, the token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt, logs, or context. ### Can I look up a reservation's driver and vehicle with the Admin360 API? Yes. Call GET `/api/hertz_services/v1/admin360/shortterm/reservations/{transaction_number}` with the reservation's transaction number, and the response returns the reservation along with the driver, vehicle, and billing details in one payload. There is no separate call needed to assemble those parts. ### Does the Admin360 API let me create or change a reservation? No. The spec exposes a single read operation that retrieves short-term reservation details by transaction number; it does not create, modify, or cancel reservations. Use it for lookups and verification, and handle booking changes through the Hertz booking system itself. ### What are the rate limits for the Admin360 API? The OpenAPI spec does not specify rate limits for the Admin360 API. Check the Exclusive Cars documentation for current limits, and have your agent retry with backoff when the API signals that it is being throttled. ### How do I look up a reservation through Jentic? Search Jentic for 'look up a short-term rental reservation' to load the Admin360 operation with its input schema, then call GET `/api/hertz_services/v1/admin360/shortterm/reservations/{transaction_number}` with the transaction number. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Can I limit what my agent is allowed to do with the Admin360 API? Yes. Because you run Jentic One yourself, you decide whether the agent may call the reservation lookup. The spec has one read operation that takes the reservation's transaction_number in the URL path, so allowing it lets the agent read reservation details and nothing else, and every call it makes is logged.