Travel Partner API

Name: Travel Partner API
Brand: Travel Partner API
Availability: InStock

✓ Official Vendor SpecE CommerceStorefrontoauth223 EndpointsREST

For Agents

Manage hotel listings, pricing accuracy, and booking link performance on Google Hotel Center. Pull performance reports, verify listings, and reconcile reservation data for travel partner accounts.

Connect the Travel Partner API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Travel Partner 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Travel Partner API.

Set hotels live on Google to enable booking links and price display in search results

Query free booking link performance reports with date-range filtering and aggregation

Retrieve price accuracy scores showing how listed prices compare to actual booking costs

Verify hotel listing data against Google's validation rules before publishing

GET STARTED

Start building with Travel Partner API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Travel Partner API for, with concrete tasks.

★ AI Agent Hotel Listing Management

AI agents monitor and optimize hotel listings on Google Hotel Center through Jentic. The agent searches for operations by intent (e.g., 'check hotel price accuracy'), receives the schema, and executes reporting and verification calls without manual configuration. Automated monitoring catches pricing discrepancies and listing verification failures before they impact search visibility.

Query the price accuracy report for account 'accounts/12345' for the last 7 days using /v3/{+name}/priceAccuracyViews and flag any hotels below 90% accuracy

Free Booking Links Performance Monitoring

Track click-through rates, impressions, and booking conversions for free booking links displayed in Google Search and Maps. The freeBookingLinksReportViews endpoint provides daily and weekly aggregates by property, allowing partners to identify underperforming listings and optimize pricing or availability data to improve visibility.

Query /v3/{+name}/freeBookingLinksReportViews for the past 30 days and aggregate click-through rates by property

Price Accuracy and Coverage Optimization

Monitor how accurately listed prices match actual booking costs and what fraction of hotel inventory has active pricing. The priceAccuracyViews endpoint scores each property's pricing reliability, while priceCoverageViews shows gaps in rate availability. Partners use these metrics to prioritize pricing feed fixes and maximize search result eligibility.

Retrieve the latest price coverage summary using /v3/{+parent}/priceCoverageViews:latest and identify properties with coverage below 80%

Reservation Reconciliation

Reconcile booking records between partner reservation systems and Google's data to ensure commission accuracy and resolve discrepancies. Upload reconciliation reports and run validation against Google's records. This prevents revenue leakage from mismatched bookings and supports accurate financial reporting between travel partners and Google.

Submit a reconciliation report for the current month using POST /v3/{+parent}/reconciliationReports and validate it with /v3/{+parent}/reconciliationReports:validate

Key Endpoints

23 endpoints — manage hotel listings, pricing data, and performance analytics on google hotel center through a restful interface with 23 endpoints.

METHOD

PATH

DESCRIPTION

POST

/v3/{+account}/hotels:setLiveOnGoogle

Set hotels live for display in Google search results

GET

/v3/{+name}/freeBookingLinksReportViews:query

Query free booking link performance metrics

GET

/v3/{+name}/priceAccuracyViews

Retrieve price accuracy scores by property

GET

/v3/{+name}/propertyPerformanceReportViews:query

Query property-level performance data

GET

/v3/{+parent}/priceCoverageViews:latest

Get the latest price coverage summary

GET

/v3/{+parent}/hotelViews

List hotel views for a partner account

POST

/v3/{+parent}/reconciliationReports

Upload a reconciliation report

POST

/v3/{+parent}/reconciliationReports:validate

Validate a reconciliation report

POST

/v3/{+account}/hotels:setLiveOnGoogle

Set hotels live for display in Google search results

GET

/v3/{+name}/freeBookingLinksReportViews:query

Query free booking link performance metrics

GET

/v3/{+name}/priceAccuracyViews

Retrieve price accuracy scores by property

GET

/v3/{+name}/propertyPerformanceReportViews:query

Query property-level performance data

GET

/v3/{+parent}/priceCoverageViews:latest

Get the latest price coverage summary

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google OAuth 2.0 service account credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw service account keys and private keys never enter the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'check hotel price accuracy on Google') and Jentic returns matching Travel Partner operations with their input schemas, including proper resource name formatting.

Time to first call

Direct Travel Partner API integration: 2-4 days for Google OAuth setup, resource name discovery, and report parsing. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Travel Partner API through Jentic.

What authentication does the Travel Partner API use?

The Travel Partner API uses Google OAuth 2.0 for authentication. Service accounts with the Travel Partner scope are typical for server-to-server integrations. Through Jentic, OAuth credentials are stored encrypted in the MAXsystem vault — agents receive pre-authorized access tokens without handling service account keys directly.

Can I check price accuracy for my hotel listings with this API?

Yes. The /v3/{+name}/priceAccuracyViews endpoint returns accuracy scores showing how closely your listed prices match actual booking costs. Use /v3/{+parent}/priceAccuracyViews:summarize for an aggregate summary across all properties. Scores below 90% typically indicate pricing feed issues.

What are the rate limits for the Travel Partner API?

The Travel Partner API follows standard Google API quotas. Default limits are approximately 1,000 requests per 100 seconds per project. Report query endpoints may have lower limits due to computational cost. The API returns HTTP 429 with quota information when limits are exceeded.

How do I pull a performance report through Jentic?

Search Jentic for 'query hotel booking link performance' to load the freeBookingLinksReportViews operation schema. Pass your account name and date range parameters to retrieve click, impression, and conversion data by property. Install with pip install jentic and sign up at https://app.jentic.com/sign-up.

Can I verify hotel listing data before publishing?

Yes. The /v3/{+parent}/listings:verify endpoint validates your hotel listing data against Google's requirements before going live. It checks for required fields, formatting issues, and data consistency. Use this to catch errors before they prevent listings from appearing in search results.

What data does the reconciliation report contain?

Reconciliation reports compare booking records between your system and Google's data. They include reservation IDs, dates, amounts, and status for a given period. Use POST /v3/{+parent}/reconciliationReports to upload your data and /v3/{+parent}/reconciliationReports:validate to check it against Google's records.

Travel Partner API

Connect the Travel Partner API to your agent

Capabilities

Start building with Travel Partner API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs