canonical: https://jentic.com/apis/axa-assistance.com/axa-assistance

# Axa Assistance 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 lets distribution partners quote, sell, and service travel insurance policies underwritten by AXA Partners. It exposes endpoints for retrieving quotes, creating orders, issuing policy subscriptions, finalising or cancelling policies, posting payment updates, and rectifying failed payments. The sandbox environment runs at sandbox.api.axapartners.com and uses OAuth 2.0 client credentials.

## For AI agents

Quote, sell, and service travel insurance policies underwritten by AXA Partners. Agents can fetch quotes, create orders, issue and amend policies, and handle payment updates.

## Scope

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

## Capabilities

- Retrieve travel insurance quotes for individual customers based on trip parameters
- Create and update travel insurance orders before policy issuance
- Issue, amend, and cancel travel insurance policies for individual travellers
- Finalise pending policy subscriptions by completing missing applicant information
- Post payment updates and rectify failed payments against an existing policy
- List policy summaries and retrieve policy attachments tied to a policy id

## Use cases

### Travel Insurance Quote and Sale

Distribution partners can quote and sell AXA Partners travel insurance directly from a checkout or booking flow. The quotes_requests endpoint returns priced options based on trip dates and traveller details, and the orders + policies endpoints turn an accepted quote into an issued subscription. Integration is suited to OTAs, airlines, and broker portals that need to bind cover at the point of sale.

Example prompt: POST a quote request to `/sales/v2/individual/travel/quotes_requests` for a 10-day Italy trip and create a policy subscription via POST `/sales/v2/individual/travel/policies`

### Policy Servicing and Amendments

Service teams can retrieve, update, finalise, or cancel an existing travel policy without leaving their CRM. The PATCH and PUT endpoints on `/policies/{policy_id}` allow corrections to traveller data, while /finalize completes missing information and /cancel terminates cover. This is appropriate for partners who handle post-sale policy administration on behalf of customers.

Example prompt: PATCH `/sales/v2/individual/travel/policies/{policy_id}` to correct a traveller date of birth and confirm the change persisted

### Failed Payment Recovery

Finance and operations agents can detect failed premium payments and rectify them through dedicated endpoints. The /payment_updates endpoint posts new payment information and /rectify_failed_payment retries the charge so that cover is not lost. This is useful for partners running automated dunning workflows on travel insurance receivables.

Example prompt: POST a new card token to `/sales/v2/individual/travel/policies/{policy_id}/payment_updates` and trigger /rectify_failed_payment to retry the failed premium

### Agent-Driven Insurance Workflows via Jentic

An AI agent can quote, bind, and service travel insurance end-to-end via Jentic without holding raw AXA OAuth client secrets. Jentic stores the credentials, returns scoped tokens, and exposes the quote-order-policy chain as discoverable operations. This is suited to agentic booking assistants that bundle insurance with travel arrangements.

Example prompt: Search Jentic for 'quote travel insurance', load the quote and policy create operations, and execute them in sequence to bind cover for a customer 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 from an accepted quote |
| POST | `/sales/v2/individual/travel/policies` | Create a policy subscription |
| GET | `/sales/v2/individual/travel/policies/{policy_id}` | Get policy details |
| 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 payment |

## Key resources

- **Orders** — Pre-policy orders that capture quote acceptance and customer details before subscription
- **Policies** — Issued travel insurance policies, including create, update, finalise, cancel, and attachments
- **Quotes Requests** — Priced quote responses for travel insurance based on traveller and trip parameters
- **Payment Updates** — Endpoints for posting new payment information and rectifying failed payments on a policy
- **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, and policy lifecycle 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}/cancel` and /finalize, 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 issuing a policy, so cancellation 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 'cancel 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 axapartners.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 environment uses OAuth 2.0 client credentials (the spec defines a sandbox_auth0_cc scheme backed by Auth0). Through Jentic, the client credentials are stored encrypted and the agent receives a short-lived bearer token, so raw secrets never enter the agent's context.

### Can I issue and cancel travel policies with the AXA Partners Travel API?

Yes. Use POST `/sales/v2/individual/travel/policies` to create a policy subscription, PUT or PATCH `/sales/v2/individual/travel/policies/{policy_id}` to amend it, and POST `/sales/v2/individual/travel/policies/{policy_id}/cancel` to terminate cover.

### How do I retry a failed premium payment with the AXA Partners Travel API?

Post the new payment information to `/sales/v2/individual/travel/policies/{policy_id}/payment_updates`, then call `/sales/v2/individual/travel/policies/{policy_id}/rectify_failed_payment` to re-attempt the charge against the policy.

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

The published OpenAPI spec does not declare explicit rate limits; AXA Partners enforces partner-specific quotas via contract. For production access, confirm 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 details. Jentic handles token exchange against the AXA OAuth endpoint automatically.

### 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, so you can allow it to request a quote at `/sales/v2/individual/travel/quotes_requests` and issue a policy while withholding cancellation unless you add it. Since the policy id sits in the URL path, as in `/sales/v2/individual/travel/policies/{policy_id}/cancel` and /finalize, a rule can pin the agent to servicing one specific policy. Your client_id and client_secret stay stored by your instance and are injected at execution time, so the agent only ever exercises the exact operations and credentials you permit.