Partner Trading API
Connect your business to Cru’s fine wine market. Verify your access, explore the live bid book, and retrieve individual bids through one versioned API.
Explore the bid book
3 live read endpoints, with request parameters and PHP and Python examples.
PHP SDKStart building in PHP
Download the source package and make your first authenticated request.
Your first integration
Get your API credentials
Ask Cru for a client key and secret with meta:read and market:read. Confirm your API environment and permitted markets.
Check your connection
Call GET /ping to verify your credentials and granted scopes.
Read the market
Page through GET /market/bids. Re-read a bid to confirm the price and fulfilment conditions before acting.
The request sequence, end to end
5 STEPSYour server
Confirm what your credentials can do
GET /pingOne authenticated call that returns your account, your granted scopes and the credential’s expiry, and no trading data at all. Run it in your setup checks.
KEEP
scopes, expires_atYour server
Read the bid book
GET /market/bidsPage through the wines buyers are looking for. limit, offset and total count wines, not bid levels — use depth=all to see every price level within each wine.
KEEP
The code of each bid you care aboutYour server
Re-read the bid immediately before acting
GET /market/bids/{code}The book moves. Retrieve the single bid by its code to confirm the price, the quantity still available and the fulfilment requirements as they are right now.
KEEP
price, quantity, requirementsYour server
Match the bid against your stock
Check requirements before you commit: local_website_only, landed_stock_only and warehouse_id decide whether the stock you hold can fill this bid at all.
Cru
Executing against a bid — planned
POST /offersCreating an offer against a bid is documented and reserved, not implemented. Until it ships, the last step of an integration is a human acting on what you read.
The supplied reference marks 3 endpoints live and 11 planned. Trading, your orders, wine reference data, and webhooks are documented as planned.