Allianz Trade API
★ Only Publicly Available OpenAPI DocumentFinanceBankingoauth29 EndpointsREST
For 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.
Use for: I need to check the credit risk of a new customer before invoicing, Search for a buyer by company name in the Allianz Trade directory, Request a credit cover for a major new customer, List all open covers in our portfolio
Not supported: Does not handle policy issuance, premium billing, or non-credit insurance lines — use for buyer risk lookup, cover requests, claims, and portfolio exposure only.
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.
Install Jentic One Beta
Connect the Allianz Trade API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Allianz Trade 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Allianz Trade API.
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
Patterns agents use Allianz Trade API for, with concrete tasks.
★ 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.
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.
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.
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.
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
9 endpoints — jentic publishes the only available openapi specification for allianz trade api, keeping it validated and agent-ready.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
OAuth 2.0 client credentials for Allianz Trade are stored encrypted in the Jentic vault. Token exchange runs inside the execution layer so the agent never sees the client secret or bearer token.
Intent-based discovery
Agents search 'check buyer credit risk' and Jentic returns the matching Allianz Trade buyer-risk operation with its input schema, so the agent calls the right endpoint without parsing docs.
Time to first call
Direct Allianz Trade integration: 3-5 days for OAuth client onboarding, token rotation, and webhook handling. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe
Stripe handles the actual payment collection on insured invoices
Use Stripe when an invoice covered by Allianz Trade also needs an online payment surface
FAQs
Specific to using Allianz Trade API through Jentic.
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 at https://app.jentic.com/sign-up.
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.
GET STARTED