title: “Use Cases” description: “End-to-end integration flows for the Channel Manager API — built for marketplaces and multi-venue operators.” ---The Channel Manager API is scoped to your channel’s partner venues. The use cases below walk through the most common integration patterns with complete request/response examples. ---## Use Case 1 — Verify Your Channel & List Partner Venues Goal: Confirm your API key is valid and discover which venues (hosts) have granted your channel access.
Step 1 — Authenticate
hosts array lists every venue that has authorized your channel. Use the _id values to filter events and resources by organization.
---## Use Case 2 — Browse Events & Ticket Rates
Goal: Display an event catalog to end users with real-time pricing and availability.
Step 1 — List events across all partner venues
Step 2 — Get a specific event with full ticket rate detail
ticket_rates with pricing and availability:
price is always in cents (e.g. 1200 = €12.00). Use current_price as the active price to show users — it reflects the currently valid pricing tier.Step 1 — Get list rates for the event
Step 2 — Create the list entry
code field is the unique identifier for check-in at the door.
---## Use Case 4 — Full Ticket Checkout Flow
Goal: Let users purchase tickets through your marketplace, receive payment confirmation and handle refunds.
See the complete step-by-step guide in the Creating a Checkout Process recipe. Here is a summary of the steps:
1. Fetch events + ticket rates — GET /events
2. Create checkout session — POST /tickets/checkout with redirect_url, error_url, ticket data and optional discount_code
3. Redirect user to payment_url from the response
4. Receive webhook — Fourvenues sends a payment.success event to your endpoint when payment completes
5. Verify webhook signature — see Webhook Authentication
6. Issue refund (if needed) — POST /tickets/{id}/refund
Minimal checkout request
If
conditions_changed: true in the response, the price shown to the user no longer matches the active price. Display an updated summary before redirecting to payment.