integrate convious's rest api for cart-based ticket checkout on attractions
domain: developer.convious.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
authenticate by POSTing client_id, client_secret, and grant_type=client_credentials (application/x-www-form-urlencoded) to https://identity.convious.com/oauth/token/ to obtain a Bearer access_token, then send it as an Authorization: Bearer header on all subsequent API calls
look up products and categories via GET https://api.convious.com/api/v1/products/ and GET .../categories/ to find productId and categoryId values, and check timeslot/day availability via the products or accounts availability endpoints
create a cart with POST https://api.convious.com/api/v1/accounts/<account_slug>/carts/, supplying categoryId, eventDate/startTime/endTime, and items (productId + amount); this reserves inventory for a limited time and can be updated (PATCH) or removed (DELETE)
optionally attach real pricing by first calling the Pricing API to obtain a pricingToken, then include it on cart creation/update so the cart reflects actual prices instead of defaulting to 0
convert the cart into a paid order with POST https://api.convious.com/api/v1/accounts/<account_slug>/bookings/, passing cartId and customer details — payment itself is handled outside Convious by the integrator
poll or sync orders via GET https://api.convious.com/api/v1/orders/ (filterable by from_updated_at) or cancel a completed order with POST https://api.convious.com/api/v1/orders/<order_id>/status/ (status: cancelled)
Known gotchas
convious explicitly states payment is handled outside Convious — the 'Making a booking' endpoint only converts an already-paid/authorized cart into an order; Convious's API is not itself a payment processor
if pricingToken is omitted when creating or updating a cart, all items default to a price of 0, and the pricingToken's cart contents/eventDate/times must exactly match what the Pricing API returned or the request fails
beyond the REST Orders/Products/Categories/Pricing/Scanning API, Convious also documents a separate embeddable checkout widget — these are two different integration paths (headless API vs. widget) and should not be conflated
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?