Get started with the Vinoshipper server-to-server API
domain: vinoshipper.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In the Vinoshipper dashboard, open the Integrations page and generate an API Key and Secret.
Use HTTP Basic Authentication on every server-to-server call: the API Key as the username and the Secret as the password.
Confirm the products you intend to order already exist in the Vinoshipper account, and note their productId or SKU.
Choose between the client-side Cart/Product Feed APIs (hand off to vinoshipper.com for checkout) or the full server-to-server order APIs for a completely custom checkout.
For AI-agent or automated tooling, pull https://developer.vinoshipper.com/llms.txt for a machine-readable index of guides and OpenAPI endpoints.
Test calls against a sandbox/test account (Vinoshipper's own docs use an internal test account, Slender Wines) before pointing at production.
Known gotchas
API Key/Secret pairs are generated per Vinoshipper account from the Integrations page — there is no separate app-registration step like some other platforms.
Products must already exist in the Vinoshipper catalog; the order APIs don't create new product records.
Client-side (Cart/Product Feed) and server-to-server order APIs solve different problems — mixing them without understanding the handoff to vinoshipper.com checkout can produce duplicate or orphaned carts.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?