Distribution API
A distributor buys Gomry tickets at wholesale and resells them on outside marketplaces (StubHub, Vivid Seats, SeatGeek and the like), and seats on Gomry experiences (tours, classes, workshops) on tours-and-activities marketplaces. Both are products, sold the same way. Gomry is the seller. Organizers opt in on their side; you never deal with them, and their names are not passed to you.You are the client for every endpoint here. Gomry never calls your systems. You poll for changes: products, and orders Gomry cancelled.
How a sale flows
1
List
Read products (events and experiences, one shape) every few minutes, or a product’s sessions live. List exactly what it returns, at the quantities it returns, and take down anything it no longer returns.
2
Sell
When a buyer buys on a marketplace, place an order with your own order reference. Gomry issues the tickets at once.
3
Deliver
Deliver each ticket’s code to the buyer, with its Gomry link. Gomry scans the code at the door.
4
Pay
Pay Gomry what the statement says you owe. Gomry records the payment against those orders.
Base URL
Authentication
Send your key on every request:Money
Refunds and customer service for your buyers are yours. Gomry never refunds a buyer you sold to.
Limits
20 requests per second per distributor. Past that, Gomry answers429 with Retry-After: 1.
Errors
Every error has the same shape. Branch oncode, never on message.

