> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gomry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delivery

> Get each ticket to the buyer: the code the door scans, and the buyer's Gomry link.

# Delivery

Gomry delivers the tickets itself, the way a mobile transfer works: the buyer gets an accept link, accepts, and the tickets become theirs. Every [order](https://docs.gomry.com/distribution-api/create-order.md) gives you that link, `claim_url`.

## `claim_url`: the accept link

**1. You deliver the link**

Give `claim_url` to the marketplace as the order's transfer URL. When you know the buyer, also send them as `transfer_to` when you place the order: Gomry emails them the same link and fills in the accept page.

**2. The buyer accepts**

They confirm their name and email and answer the organizer's questions, once for the whole order. They don't need a Gomry account first: accepting creates one.

**3. The tickets become theirs**

Gomry names every ticket of the order after them, emails them their QR codes and opens a page with all of them. The organizer sees them as an attendee.

There is one link per order, and it works once, for one person. Every ticket of the order carries the same `claim_url`.

> [!NOTE]
>
> **Keep the link for the buyer.** Whoever accepts first gets the tickets, so show it only to the person who bought them.

## `barcode`: what the door scans

One code per ticket. Use it only where a marketplace cannot take a link: draw it as a QR code on a PDF, or hand it over as the ticket's barcode. Gomry's scanners admit it once, and it stops admitting when the order is cancelled.

When the organizer asks a required question, `barcode` is `null` until the order is accepted, so nobody reaches the door without answering. Deliver the `claim_url` instead.

## Reading tickets again

[Read the order](https://docs.gomry.com/distribution-api/get-order.md) at any time for the same links and codes. They never change for the life of the ticket.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.