RU
Docs sections

Test mode

A test key works with its own events and tickets and emails only you. That lets you check the integration before sales start.

How test differs from live

  • A bt_test_… key sees test events, orders, tickets and devices only. A live key doesn't see them, and the other way round.
  • Emails for test orders go only to the organization's staff addresses and confirmed test addresses. Other addresses get no email, while the order and its tickets are issued as usual.
  • A test ticket's page carries the banner "ТЕСТ · билет не настоящий" (TEST, not a real ticket).
  • A door staff device works in one mode: a test device checks test events only, a live one checks live events only.
  • Everything else is the same: the same endpoints, responses, errors and limits.

Test events don't carry over to live mode. Before launch, create the events again with a live key.

Test recipients

You add the addresses that receive test emails in the dashboard: настройки → тестовые адресаты → Добавить адрес (Settings → Test recipients → Add address). The address gets an email with a link and becomes confirmed once someone opens it. The organization's staff addresses work without confirmation. The API can't change the recipient list.

How to check your integration

  1. Create a test key and an event, then publish it: quickstart.
  2. Send an order to your own address from the test recipients. Check the email and the ticket page.
  3. Repeat the same request with the same Idempotency-Key. You should get the same order and the Idempotent-Replayed: true header.
  4. Check how your site handles 409 sold_out: give a tier a small quota and buy more than that.
  5. Cancel a ticket with POST /v1/tickets/{id}/cancel: the QR stops working at the door and the guest gets an email.
  6. Pair a door staff phone in test mode and scan the QR at the door: door staff.
  7. Swap the key for a live bt_live_… key and create live events.