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

# Concur SAP Concur Hotel Service API

The SAP Concur Hotel Service v4 API is the supplier-side integration surface for Custom Hotel Source providers feeding inventory, rates, and bookings into the SAP Concur Online Booking Tool. SAP Concur calls the supplier endpoints to search hotels, retrieve detail and rate information, create reservations, and modify or cancel them. It is intended for hotel suppliers and travel-tech intermediaries that want their inventory bookable inside Concur's corporate travel flow.

## For AI agents

Serve hotel inventory, rates, and reservations to the SAP Concur Online Booking Tool: respond to search, details, rate, and reservation lifecycle calls.

## Scope

Does not handle flights, car rentals, expense reports, or invoicing - use for SAP Concur Custom Hotel Source supplier integration only.

## Capabilities

- Respond to hotel search requests with available properties for a corporate traveler
- Return detailed hotel information for a selected property
- Provide rate plans and rate detail for a property and date range
- Create a hotel reservation under a corporate traveler's profile
- Read, modify, and cancel an existing hotel reservation

## Use cases

### Custom Hotel Source Inventory Integration

Make a hotel chain's or aggregator's inventory available to corporate travelers using SAP Concur. The `/hotels/search` and `/hotels/details` endpoints answer Concur's outbound discovery calls, and `/hotels/rates` and `/hotels/ratedetails` return live pricing. Hotel suppliers and consolidators use this to enter the Concur distribution channel without building bespoke connectors per customer.

Example prompt: Respond to a search request for hotels in Berlin between 2026-07-15 and 2026-07-18 for one adult, returning ten properties with thumbnail rates

### Reservation Lifecycle for Corporate Bookings

Create, modify, and cancel hotel reservations triggered by a Concur user booking through the Online Booking Tool. `/hotels/reservation` creates the booking, `/hotels/reservation/modify` changes dates or guests, `/hotels/reservation/cancel` voids the booking, and `/hotels/reservation/read` returns the current status. This keeps the supplier-side reservation in sync with the corporate booking record.

Example prompt: Create a reservation for traveler ID t_4421 at hotel HX-9 from 2026-08-02 to 2026-08-04, then read the reservation back to confirm the confirmation number

### Rate Quoting and Compliance

Return rate plans that respect a customer's negotiated corporate rates and travel policy at the time of search. The `/hotels/rates` endpoint returns the rate codes available, and `/hotels/ratedetails` returns per-rate inclusions, cancellation rules, and taxes. Travel-program owners use this surface to enforce policy at the point of booking rather than during reconciliation.

Example prompt: Quote rate details for property HX-9 between 2026-08-02 and 2026-08-04 with corporate code BIGCO-2026 and report cancellation policy

### Agent-Driven Travel Operations via Jentic

Let an AI assistant act as the corporate travel concierge that talks to the Concur supplier surface on behalf of an internal travel desk. Through Jentic the agent searches by intent, loads the schema for the relevant Concur Hotel operation, and executes the call without the developer wiring auth or pagination. This is suited to internal travel-ops bots that triage exception bookings.

Example prompt: On the prompt 'change reservation R-7711 to check in a day later', call `/hotels/reservation/modify` with the new check-in date and confirm the updated dates

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/hotels/search` | Search hotel availability |
| POST | `/hotels/details` | Retrieve detailed hotel information |
| POST | `/hotels/rates` | List available rate plans |
| POST | `/hotels/ratedetails` | Retrieve detailed rate information |
| POST | `/hotels/reservation` | Create a hotel reservation |
| POST | `/hotels/reservation/read` | Read an existing reservation |
| POST | `/hotels/reservation/modify` | Modify an existing reservation |
| POST | `/hotels/reservation/cancel` | Cancel a reservation |

## Key resources

- **Hotel search and details** — Supplier responses to Concur's hotel discovery calls
- **Hotel rates** — Rate plans and rate detail for a property and stay
- **Reservation lifecycle** — Create, read, modify, and cancel hotel reservations

## Why Jentic

- **Setup:** Wiring the SAP Concur Hotel Service API by hand means learning its basic auth, building the Custom Hotel Source search, rates, and reservation calls, and managing reservation state yourself. Through Jentic you install once, import the SAP Concur Hotel Service API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** The SAP Concur Hotel Service API sends hotel and reservation details in the request body, so limit the agent to the operations it needs, such as searching hotels or reading a reservation. You choose the operations it may call, so you can allow search and rate lookups while leaving reservation modify or cancel out unless you add them.
- **Credential handling:** Your SAP Concur credentials 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 'search hotel availability' or 'read a hotel reservation', and Jentic returns the matching SAP Concur operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amadeus Hotel Booking** — GDS-style hotel booking API across the Amadeus content platform
- **Amadeus Hotel Search** — Hotel availability and shopping API across Amadeus content
- **Booking.com** — Leisure-focused hotel inventory and booking platform

## FAQ

### What authentication does the SAP Concur Hotel Service API use?

The API uses HTTP basic authentication: a base64-encoded username and password in the Authorization header. Through Jentic the credentials are stored encrypted in the vault and injected at execution time, so the raw values never enter the agent's prompt or logs.

### Can I create a hotel reservation with this API?

Yes. POST `/hotels/reservation` creates a reservation linked to the traveler and rate selected from a prior `/hotels/rates` response. The reservation can then be read, modified, or cancelled via the dedicated endpoints under `/hotels/reservation.`

### Who is this API for?

It is the supplier-side integration for Custom Hotel Source providers feeding inventory into SAP Concur. SAP Concur calls these endpoints; the supplier implements them. If you are a Concur customer rather than a hotel supplier, use the corresponding consumer-side Concur APIs instead.

### What are the rate limits for the Concur Hotel Service API?

SAP Concur applies supplier-specific throughput agreed during onboarding rather than a published global limit. Suppliers should be ready to handle bursts during peak booking windows; agents calling on behalf of the supplier should add backoff on HTTP 429 responses, which Jentic surfaces as structured errors.

### How do I quote rates through Jentic?

Run the Jentic search query 'quote SAP Concur hotel rates', load the returned operation (POST `/hotels/ratedetails`), and execute it with the property id, stay dates, and any corporate rate code. The response includes per-rate inclusions and cancellation policy.

### Can I modify an existing reservation?

Yes. POST `/hotels/reservation/modify` accepts the original reservation reference along with the changed fields such as new check-in or check-out dates. Use `/hotels/reservation/read` first to retrieve the current state, then submit only the fields that change.

### Can I limit what my agent is allowed to do with the SAP Concur Hotel Service API?

Yes. Jentic One is self-hosted, so you run it under your own rules and decide which SAP Concur Hotel operations the agent may call. You can grant read-only access such as searching hotels, retrieving details, and looking up rates and rate details, while leaving reservation create, modify, and cancel out unless you explicitly add them. The credentials stay with your own instance and are injected only for the operations you allow, so the agent can never reach an endpoint you have not enabled.