AXA Partners Travel API
Agent-ready OpenAPI document · curated by JenticFinanceAccountingoauth215 EndpointsREST
Know of an official OpenAPI document? Contribute it →
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.
Use for: Quote a travel insurance policy for a 7-day trip to France, Create a travel insurance order for an individual customer, I want to bind an AXA travel policy from an accepted quote, Cancel a travel insurance policy by its policy id
Not supported: Does not handle health insurance, life insurance, or claims adjudication - use for quoting, binding, and servicing AXA Partners individual travel insurance policies only.
Jentic publishes the only available OpenAPI specification for AXA Partners Travel API, keeping it validated and agent-ready. The AXA Partners Travel API gives distribution partners programmatic access to quote, sell, and service travel insurance policies underwritten by AXA Partners. Endpoints cover quote requests, order creation, policy subscription, finalisation, cancellation, payment updates, and failed-payment recovery. The sandbox runs at sandbox.api.axapartners.com behind OAuth 2.0 client credentials.
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.
1
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%2Faxapartners.com%2Faxapartners" | sh2
Step 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%2Faxapartners.com%2Faxapartners" | 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.
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
Finalise pending policy subscriptions with missing applicant data
Post payment updates and rectify failed premium payments on a policy
Retrieve policy summaries and attachments associated with a policy id
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
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the AXA Partners Travel API by hand means running its OAuth2 client-credentials flow, refreshing short-lived bearer tokens yourself, and sequencing the quote, order, bind, and policy-servicing payloads correctly. Through Jentic you install once, import the AXA Partners Travel API from the API Directory, store the client_id and client_secret once, and your agent calls it.
Permission scoping
AXA Partners puts the policy id in the URL path, such as /sales/v2/individual/travel/policies/{policy_id} for a PATCH update and /cancel for cancellation, so a rule can pin the agent to servicing a specific policy. You choose which operations it may call, such as requesting a quote or creating an order, so cancellation or a policy update is not included unless you add it.
Credential isolation
Your AXA Partners client_id and client_secret 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 'quote travel insurance' or 'bind a travel policy', and Jentic returns the matching AXA Partners operation with its input schema so the agent calls the right lifecycle endpoint without browsing the partner docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 with Jentic One, the self-hosted execution layer.
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 your Jentic One instance 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.
Can I limit what my agent is allowed to do with the AXA Partners Travel API?
Yes. Because you run Jentic One yourself, your own rules decide which AXA Partners operations the agent may call and which credentials it may use, so you can allow quoting via POST /sales/v2/individual/travel/quotes_requests and order creation while withholding a policy update (PATCH /sales/v2/individual/travel/policies/{policy_id}) or a cancellation (/cancel) unless you add it. Since the policy id sits in the URL path, a rule can also pin the agent to servicing one specific policy. Your client_id and client_secret stay in your instance and are injected only at execution time, never entering the agent's context.
GET STARTED