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

# AXA Partners Travel API

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.

## For AI 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.

## Scope

Does not handle health insurance, life insurance, or claims adjudication - use for quoting, binding, and servicing AXA Partners individual travel insurance policies only.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

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

## Key resources

- **Quotes Requests** — Priced quote responses for individual travel insurance
- **Orders** — Pre-policy orders capturing quote acceptance and customer details
- **Policies** — Travel insurance policy lifecycle: create, update, finalise, cancel, attachments
- **Payment Updates** — Post new payment information and rectify failed premium payments
- **Communication Requests** — Trigger outbound communications with the customer linked to an order

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **AXA Partners Travel API** — Same AXA Partners Travel API published under the axa-assistance.com vendor domain.
- **Allianz Trade API** — Allianz Trade exposes credit and trade insurance APIs as a competing carrier to AXA.
- **Wink Travel API** — Travel booking platform that pairs naturally with travel insurance issuance at checkout.

## FAQ

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