Beta

The Partner Trading API v1 is in beta — endpoints and response shapes may still change.

Developers
 Cru World Wine

Configure connection

Choose how to authenticate your requests.

For Production · United States · USD — change these in the toolbar.

Use a credential without an IP allowlist: calls reach Cru from this site’s server.

How authentication works

Cru issues partners a CLIENT-KEY and CLIENT-SECRET, sent as headers on every request. There is no token to fetch first. Writes run at once and carry a reference the playground generates.

Partner credentials →

No credentials yet?

Credentials are kept for this session only, never included in copied examples, and redacted from everything the playground shows.

API playground

Build a request, over REST or MCP, and inspect the response.

Tool reference
Partner key

Production environment · Write requests require confirmation

Request

Warehouses outside Cru where a customer's wine may be stored: inbond_address_id, name, company, street, city, region, postcode, country, telephone, its lcb_site_code if it has one, and whether it is bonded (is_bonded; a few are duty-paid storage). Documentation ↗

POSTtools/call · list_inbond_warehouses

https://us.cruworldwine.com/api/mcp

This tool takes no arguments.

Response

Nothing sent yet. The response appears here.

API credentials

Enter the client key and secret issued by Cru. They are kept for this browser tab’s session — a reload keeps them, closing the tab or clearing them ends them.

Credentials are never included in copied examples, and are redacted from anything the console prints back.

Request API access

Tell us who you are and what you want to build. Cru issues a client key and secret for your organisation, scoped to what you need.

Markets you trade in (choose one or more)

We use what you send here to reply about API access, and for nothing else. Cloudflare Turnstile checks the form for bots (privacy policy).