AXA Partners Travel API

Name: AXA Partners Travel API
Brand: AXA Partners Travel API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingoauth215 EndpointsREST

For Agents

Quote, bind, and amend AXA Partners travel insurance policies for individual travellers. Agents can drive the full quote-to-policy lifecycle including payment updates and cancellations.

Install Jentic One Beta

Connect the AXA Partners Travel API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AXA Partners Travel 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: 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 AXA Partners Travel API.

Request priced travel insurance quotes for an individual traveller and trip

Create and update travel insurance orders ahead of policy issuance

Issue, amend, and cancel individual travel insurance policies

GET STARTED

Start building with AXA Partners Travel API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AXA Partners Travel API for, with concrete tasks.

★ Embedded Travel Insurance at Checkout

OTAs and airline partners can embed AXA Partners travel insurance into their booking flow by calling /quotes_requests for pricing and POST /policies to bind cover once the customer accepts. The order endpoints allow the partner to capture intent before payment and convert to a subscription cleanly. This use case suits booking engines that need to attach cover at the point of sale.

POST /sales/v2/individual/travel/quotes_requests for an upcoming trip, then POST /sales/v2/individual/travel/policies with the selected quote to bind cover

Policy Lifecycle Management

Operations teams can manage in-force AXA Partners policies — amending traveller details, finalising incomplete subscriptions, retrieving policy attachments, and cancelling on request. The PATCH and PUT operations on /policies/{policy_id} cover corrections, /finalize completes pending policies, and /cancel terminates cover. Suited to partners running back-office policy administration.

PATCH /sales/v2/individual/travel/policies/{policy_id} with corrected traveller details and verify the policy state is updated via GET on the same path

Premium Payment Recovery

Finance teams can detect and recover failed premium payments on travel policies. POST /policies/{policy_id}/payment_updates accepts new payment instrument details, and /rectify_failed_payment retries the charge so cover is not lost. Useful for partners that automate dunning on travel insurance receivables.

Post a new payment token to /sales/v2/individual/travel/policies/{policy_id}/payment_updates and trigger /rectify_failed_payment to recover the unpaid premium

Agent-Driven Insurance Bundling via Jentic

An AI booking assistant can bundle travel insurance with a trip it has just arranged, calling AXA Partners through Jentic without holding raw OAuth secrets. Jentic exposes the quote, order, and policy operations as discoverable tools and handles token exchange. Suited to agentic travel agents that want to attach cover automatically.

Search Jentic for 'quote travel insurance', load the quote and policy create operations, and chain them to bind cover for a booked trip

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for axa partners travel api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/sales/v2/individual/travel/quotes_requests

Get travel insurance quotes

POST

/sales/v2/individual/travel/orders

Create an order

POST

/sales/v2/individual/travel/policies

Create a policy subscription

PATCH

/sales/v2/individual/travel/policies/{policy_id}

Amend an existing policy

POST

/sales/v2/individual/travel/policies/{policy_id}/cancel

Cancel a policy

POST

/sales/v2/individual/travel/policies/{policy_id}/finalize

Finalize a pending subscription

POST

/sales/v2/individual/travel/policies/{policy_id}/rectify_failed_payment

Retry a failed premium

POST

/sales/v2/individual/travel/quotes_requests

Get travel insurance quotes

POST

/sales/v2/individual/travel/orders

Create an order

POST

/sales/v2/individual/travel/policies

Create a policy subscription

PATCH

/sales/v2/individual/travel/policies/{policy_id}

Amend an existing policy

POST

/sales/v2/individual/travel/policies/{policy_id}/cancel

Cancel a policy

Why Jentic?

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

Credential isolation

AXA Partners OAuth 2.0 client credentials are stored encrypted in the Jentic vault. Agents receive scoped, short-lived bearer tokens — raw client secrets never enter the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'quote travel insurance', 'cancel travel policy') and Jentic returns the matching AXA Partners operations with input schemas attached.

Time to first call

Direct AXA Partners integration: 1-2 weeks for OAuth onboarding, sandbox testing, and policy lifecycle handling. Through Jentic: under 1 hour from search to first executed quote-to-policy call.

FAQs

Specific to using AXA Partners Travel API through Jentic.

Why is there no official OpenAPI spec for AXA Partners Travel API?

AXA Partners does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AXA Partners Travel API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the AXA Partners Travel API use?

The sandbox uses OAuth 2.0 client credentials (sandbox_auth0_cc, backed by Auth0). Through Jentic, those client credentials sit in the Jentic vault and the agent receives a short-lived bearer token, so secrets never enter the agent context.

Can I quote and bind a travel policy with the AXA Partners Travel API?

Yes. POST /sales/v2/individual/travel/quotes_requests returns a priced quote, POST /sales/v2/individual/travel/orders captures intent, and POST /sales/v2/individual/travel/policies issues the subscription.

How do I rectify a failed premium with the AXA Partners Travel API?

Send the new payment instrument to /sales/v2/individual/travel/policies/{policy_id}/payment_updates, then call /sales/v2/individual/travel/policies/{policy_id}/rectify_failed_payment to retry the charge.

What are the rate limits for the AXA Partners Travel API?

The OpenAPI spec does not declare explicit rate limits; AXA Partners enforces partner-specific quotas via contract. Confirm production limits with your AXA Partners integration manager.

How do I quote travel insurance through Jentic?

Search Jentic for 'quote travel insurance', load the schema for POST /sales/v2/individual/travel/quotes_requests, and execute it with traveller and trip parameters. Jentic handles the OAuth token exchange under the hood.

AXA Partners Travel API

Connect the AXA Partners Travel API to your agent

Capabilities

Start building with AXA Partners Travel API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs