canonical: https://jentic.com/apis/allianz-trade.com/allianz-trade

# Allianz Trade API

Jentic publishes the only available OpenAPI specification for Allianz Trade API, keeping it validated and agent-ready. Allianz Trade (formerly Euler Hermes) is a global trade credit insurer, and the API exposes buyer search, buyer risk lookup, cover requests, claims filing, and portfolio exposure reporting. Authentication uses OAuth 2.0 client credentials, suitable for system-to-system integration in finance and treasury workflows. The endpoint set is focused on the credit-cover lifecycle rather than general policy administration.

## For AI agents

Search buyers, pull buyer risk scores, request and inspect trade credit covers, file claims, and read portfolio exposure for an Allianz Trade-insured book.

## Scope

Does not handle policy issuance, premium billing, or non-credit insurance lines - use for buyer risk lookup, cover requests, claims, and portfolio exposure only.

## Capabilities

- Search the Allianz Trade buyer database by name or identifier
- Pull a buyer risk score by buyer ID for credit decisions
- Request a new trade credit cover for a buyer
- List existing covers and inspect a single cover by coverId
- File a new claim against an existing cover
- Track an open claim by claimId and read its status
- Read aggregate portfolio exposure for risk monitoring

## Use cases

### Pre-invoice credit check

Finance teams pull a buyer risk score before extending payment terms to a new customer. The agent calls GET /buyers/search to find the buyer, then GET /buyers/{buyerId}/risk to retrieve the risk grade. The flow takes seconds and prevents extending uninsured credit to deteriorating buyers.

Example prompt: Search for buyer 'ACME Industrial GmbH' via GET /buyers/search, take the top match, then call GET /buyers/{buyerId}/risk and return the risk grade.

### Cover request workflow

When a sales deal exceeds an internal threshold, the agent files a cover request via POST /covers and tracks the decision via GET /covers/{coverId}. This automates the back-and-forth between sales operations and the credit insurer, removing email-based requests from the cover lifecycle.

Example prompt: Submit a cover request for buyer ID B-9912 and amount EUR 250,000 via POST /covers, then poll GET /covers/{coverId} until the decision status is final.

### Claim filing and tracking

When an invoice goes unpaid past terms and is covered, the agent files a claim via POST /claims with the cover and invoice references, then monitors progress via GET /claims/{claimId}. This consolidates claims handling into the same system that originates the underlying cover request.

Example prompt: File a claim against cover ID C-4421 for invoice INV-7733 totalling EUR 18,500 via POST /claims, then store the returned claimId.

### AI agent receivables monitoring

An AI agent in a treasury workflow can read portfolio exposure on a daily cadence, pull risk updates for top buyers, and flag deteriorating positions. Through Jentic the agent searches by intent and the OAuth client credentials never enter the prompt context. This turns Allianz Trade into a programmable risk feed rather than a portal.

Example prompt: Use Jentic to search 'get portfolio exposure', call GET /portfolio/exposure, and post the top 10 highest-exposure buyers to a Slack treasury channel.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /buyers/search | Search buyers by name or identifier |
| GET | /buyers/{buyerId}/risk | Get buyer risk score |
| POST | /covers | Request a new credit cover |
| GET | /covers | List existing covers |
| GET | /covers/{coverId} | Get cover details |
| POST | /claims | File a new claim |
| GET | /claims/{claimId} | Get claim status |
| GET | /portfolio/exposure | Read portfolio exposure |

## Key resources

- **Buyers** — Search the buyer directory and retrieve risk scores
- **Covers** — Request, list, and inspect trade credit covers
- **Claims** — File new claims and track existing claim status
- **Portfolio** — Read aggregate exposure across the insured book

## Why Jentic

- **Setup:** Wiring the Allianz Trade API by hand means running its OAuth2 token exchange, refreshing access tokens against api.allianz-trade.com, and encoding buyer, cover, and claim calls yourself. Through Jentic you install once, import the Allianz Trade API from the API Directory, store the OAuth2 credentials once, and your agent calls it.
- **Permission scoping:** The Allianz Trade API puts the buyer, cover, and claim ids in the URL path (/buyers/{buyerId}/risk, /covers/{coverId}, /claims/{claimId}), so a rule can pin your agent to one buyer or cover. You choose the operations it may call, so submitting cover requests or filing claims is not included unless you add them.
- **Credential handling:** Your Allianz Trade OAuth2 credentials 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 'look up buyer credit risk' or 'check portfolio exposure', and Jentic returns the matching Allianz Trade operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Plaid** — Plaid provides bank account and transaction data that complements credit risk decisions
- **Stripe** — Stripe handles the actual payment collection on insured invoices
- **Mollie** — Mollie handles European payment collection alongside trade credit

## FAQ

### Why is there no official OpenAPI spec for Allianz Trade API?

Allianz Trade does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Allianz Trade 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 Allianz Trade API use?

OAuth 2.0 client credentials, with the token endpoint at https://api.allianz-trade.com/oauth/token. Through Jentic, the client ID and secret are stored in the encrypted vault and the token exchange runs inside the execution layer.

### Can I pull a buyer risk score before extending credit?

Yes. GET /buyers/search returns matching buyers, and GET /buyers/{buyerId}/risk returns the risk grade. Together they form the standard pre-invoice credit check flow.

### How do I request a cover via the Allianz Trade API through Jentic?

Run pip install jentic, search 'request a credit cover from Allianz Trade', load the input schema for POST /covers, and execute with the buyer ID and requested amount. Poll GET /covers/{coverId} for the decision.

### Can I file an insurance claim through this API?

Yes. POST /claims files a claim against an existing cover. Track progress via GET /claims/{claimId} and list claims via GET /claims to reconcile open positions.

### Does the Allianz Trade API expose portfolio exposure?

Yes. GET /portfolio/exposure returns aggregate exposure across the insured book, suitable for daily treasury reporting and concentration checks.

### Can I limit what my agent is allowed to do with the Allianz Trade API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The buyer, cover, and claim IDs sit in the URL path (/buyers/{buyerId}/risk, /covers/{coverId}, /claims/{claimId}), so a rule can pin the agent to a single buyer or cover. You also choose which operations it may call, so write actions like submitting a cover request via POST /covers or filing a claim via POST /claims are excluded unless you grant them, leaving the agent with read-only buyer risk and portfolio exposure lookups.