Skip to main content

Going Live

Connecting a supplier takes about a day of integration work on your side, then a catalog sync that runs unattended. Contact support@gomry.com to start.

Before you build

Answer these first. They decide how much of your inventory can be sold through Gomry, and they are the most common source of late surprises.
Measure the whole catalog, not the first few pages. Delivery-format mix can differ sharply between the start and the end of a catalog, and a sample from one end has misled us in both directions.

What we exchange

Gomry generates every key and secret. Never pick one yourself, and never send one back to us over email or chat in plain text.

Turning on webhook signing

The order matters. Doing the last step first rejects every webhook in between:
  1. Gomry generates the signing secret. It has no effect yet.
  2. Gomry installs it on Retail.
  3. You receive the secret and start signing.
  4. Gomry switches your supplier to signed mode.

Build checklist

1

Authenticate

Every endpoint requires X-API-Key and fails closed. A wrong key, a missing key, and Authorization: Bearer all answer 401. See Authentication and errors.
2

Catalog

GET /api/vendor/v1/catalog returns real events from your sandbox, pages to the end, and ends with nextPage: null. Each page answers within 30 seconds.
3

Listings

GET /api/vendor/v1/listings answers within 4.5 seconds, sends splits exactly as your system has them, and sets format and productKind correctly.
4

Buy on the sandbox

Quote, then place an order, then find it with GET /api/vendor/v1/orders?reference=…. Replay the same order with the same reference and confirm you return the existing order rather than placing a second one.
5

Delivery

Fulfilment moves from pending to ready (or shipped), and credentials return a barcode value, not a link or a PDF.

Switching on

Once your integration passes the checklist, Gomry sets your base URL and activates your supplier. Activation is the same decision as publishing your inventory: there is no setting that syncs your catalog without selling from it. The first catalog sync starts on the next 15-minute cycle, with its own share of the time budget so a large catalog cannot hold it up. A catalog of around 100,000 events takes days to sweep the first time. It runs unattended and resumes where it stopped.

Before inventory reaches buyers

We check these with you:
  • Start times are right. An event whose timezone could not be resolved is stored with the wrong wall clock. Send venue.timezone and an honest occursAt. See Catalog.
  • Published formats match purchasable formats. If a format appears in your listings but your order endpoint refuses it, a buyer sees the offer and the checkout fails. Either support it on orders, or tell us so it is withheld before it is published.
  • Non-admission items are labelled. Parking and other add-ons carry productKind, so they are never sold as a ticket.