authenticate and build a checkout flow with the vivenu api
domain: docs.vivenu.dev · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create, update, or delete API keys from the vivenu Dashboard; keys are intended for server-side use only and must never be exposed to browser JS.
Send the key as a Bearer token in the Authorization header on every request to https://vivenu.com/api (or https://vivenu.dev/api for the dev environment); unauthenticated calls to private endpoints return 401.
Use the Events resource to manage events, noting that some endpoints are explicitly marked PUBLIC (no auth required) versus requiring an Organization ('ORG') API key.
Build a purchase path with the Checkout, Products, and Tickets resources, using Purchase Intents to capture buyer intent before finalizing a checkout.
Paginate bulk 'get all' calls with skip and top (default page size 25, some endpoints support up to top=100), using array (param[]=a¶m[]=b) or nested-key (object[key]=value) query syntax for advanced filters.
Known gotchas
API keys can carry admin-equivalent privileges, so leaking one is a serious exposure — vivenu is explicit that keys must stay server-side only.
Some endpoints require Organization ('ORG') API keys versus general private endpoints — using the wrong key type fails even though both are 'authenticated'.
Default page size on list endpoints is only 25 records; forgetting to page through with skip/top will silently truncate large result sets like transactions or tickets.
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?