-
the ticket email
The email has the QR code, the date, the venue address and a button to the ticket page.
-
the ticket page
It opens from the link, no sign-up. It shows the QR, the guest's name, the seat, directions and Add to calendar. Once opened, it works offline too.
-
a full-screen code
The guest taps the QR and it opens big. The screen stays on. The code can be saved as a picture or sent on.
-
an answer in half a second
Door staff point the camera and the screen changes color: lime to let in, yellow if the ticket was already used, red if it isn't valid.
we handle tickets
and the door
You sell tickets on your own site. We email each guest a QR ticket and check it at the door. The scanner works offline too.
from payment to the door
A guest pays on your site, your site sends us the order through the API, and we send the ticket right away. Without a site, you can hand out tickets in the dashboard or upload a list.
The screens are in Russian, the language budu speaks today.
two ticket looks
A classic ticket with a tear-off line, or a pass with a lime header. The organizer picks the look, and the event cover sits on top.
- Full-screen QR
- Save and share
- Screen stays on
- Works offline
- Big seat number
- Directions in Yandex Maps
- Add to calendar
- Every ticket of an order on one page
the door scanner
The camera turns on right away and there is nothing to tap. A second and a half after each answer the scanner is ready for the next guest.
- offline
- The phone downloads the ticket list in advance and checks the QR signature itself. Entries sync once it is back online.
- pair with a QR
- The organizer shows an invite QR, the staff member scans it, and the phone is ready. No login or password.
- manual search
- A guest forgot their phone? Find the ticket by name, email or number.
- counter and scanners
- The header shows how many guests are in. USB and Bluetooth barcode scanners work too.
the organizer dashboard
A new event takes three steps: the details, tiers or a seat map, then hand out tickets or connect your site. Sales and entries on the event page refresh every two seconds.
- event numbers
- Sold, on hold, left and checked in, for every tier.
- tickets
- Search, cancel, reissue the QR, resend the email.
- manual issue and CSV
- Hand out tickets from your list or upload a spreadsheet.
- devices
- Add a staff phone, rename it, revoke it.
- API keys
- Test and live keys for your site: create, revoke.
- activity log
- A history of who issued and who cancelled.
your brand on the ticket
The organizer's logo and colors show on the ticket page, the full-screen QR, the saved picture and the emails. Budu keeps only a small line and the mark in the middle of the QR.
connect through the API
After payment your site sends one request: the event, the tiers and the buyer's email. The response carries the ticket links, and we email the guests ourselves.
- A retry with the same Idempotency-Key never issues an extra ticket.
- The same key finds, cancels and reissues tickets and uploads guest lists.
- A test key never touches real tickets or sales.
Request
POST /v1/orders
Authorization: Bearer bt_test_…
Idempotency-Key: order-1042
{
"event_id": "…",
"items": [
{ "tariff_id": "…", "qty": 2 }
],
"buyer": {
"email": "maria@example.ru",
"first_name": "Мария",
"last_name": "Соколова"
}
}Response 200
{
"order_id": "…",
"status": "issued",
"tickets": [
{ "id": "…", "url": "…/t/Vw3kq…" },
{ "id": "…", "url": "…/t/9pLmZ…" }
]
}what else is inside
- assigned seating
- Upload the seat map as a CSV. Each seat sells once, even when two people buy it in the same second.
- test mode
- Test keys, and tickets marked TEST. Emails go only to your own addresses, and a real event won't let a test ticket in.
- data stays in Russia
- Servers, storage and email run on providers in Russia.
get your guests saying “budu”
Budu is Russian for “I'll be there”. For now we onboard organizers ourselves: we create your organization and send an invite to the dashboard. Tell us about your event and where you sell tickets.