Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SAP Concur Hotel Service API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fconcur.com%2Fconcur" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fconcur.com%2Fconcur" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with SAP Concur Hotel Service API.
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
GET STARTED
Patterns agents use SAP Concur Hotel Service API for, with concrete tasks.
★ 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.
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.
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.
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.
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
8 endpoints — 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.
METHOD
PATH
DESCRIPTION
/hotels/search
Search hotel availability
/hotels/details
Retrieve detailed hotel information
/hotels/rates
List available rate plans
/hotels/ratedetails
Retrieve detailed rate information
/hotels/reservation
Create a hotel reservation
/hotels/reservation/read
Read an existing reservation
/hotels/reservation/modify
Modify an existing reservation
/hotels/reservation/cancel
Cancel a reservation
/hotels/search
Search hotel availability
/hotels/details
Retrieve detailed hotel information
/hotels/rates
List available rate plans
/hotels/ratedetails
Retrieve detailed rate information
/hotels/reservation
Create a hotel reservation
/hotels/reservation/read
Read an existing reservation
/hotels/reservation/modify
Modify an existing reservation
/hotels/reservation/cancel
Cancel a reservation
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using SAP Concur Hotel Service API through Jentic.
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.
For Agents
Serve hotel inventory, rates, and reservations to the SAP Concur Online Booking Tool: respond to search, details, rate, and reservation lifecycle calls.
Use for: I want to expose my hotel inventory to SAP Concur, Search hotels in a destination for a corporate traveler, Retrieve full property details for a hotel selected in Concur, Quote rate plans for a date range and traveler
Not supported: Does not handle flights, car rentals, expense reports, or invoicing - use for SAP Concur Custom Hotel Source supplier integration only.
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.