Generates domain name variants based on the organization name and returns only those that are currently available for registration.

How it works:

1. Strips common Estonian legal forms from the name (AS, OU, FIE, MTU, etc.)
2. Generates variants: concatenated (examplecompany) and hyphenated (example-company)
3. Combines variants with all available .ee zone origins
4. Checks each variant against the domain registry (EPP) for availability
5. Filters out domains that are already reserved by other users
6. Returns only the available domain names

Note: Expired reservations are automatically cleaned up during the availability check, so a previously reserved domain may become available again after its reservation period ends.

Creates free short-term domain reservations (7 days). Reserved domains receive a unique registration code (password) that the entrepreneur must use to register the domain at an accredited .ee registrar.

Important behaviors:

• Only domains that are currently available (not registered and not reserved) will be reserved
• If some requested domains are unavailable, they are silently skipped — only available ones are reserved
• If none of the requested domains are available, a 422 error is returned
• Each reserved domain gets its own unique registration code
• The reservation expires after 7 days — after that, the domain becomes available again

What to store: Save the user_unique_id from the response. You will need it to retrieve the registration codes later via GET /reserve_domains/{user_unique_id}.

Retrieves the current state of domains from a short-term (free) reservation.

Each domain in the response includes a status field that reflects its current state:

• reserved — Domain is still reserved. The response includes the password (registration code) and expire_at date. The entrepreneur can use the registration code to register the domain at a registrar.
• registered — Domain has already been registered through a registrar using the registration code. No password or expire_at is returned.
• expired — The 7-day reservation period has ended. The domain is no longer held and may be taken by someone else. No password or expire_at is returned.

Typical usage: Display only domains with status: "reserved" to the user — these are the ones that still need to be registered at a registrar.

Note: For long-term (paid) reservations, use GET /api/v1/business_registry/long_reserve_domains_status instead.

Creates a paid long-term domain reservation (1 year). This endpoint does not reserve the domains immediately — it creates an invoice and returns a payment link.

Flow:

1. Call this endpoint with the desired domain names
2. Receive linkpay_url, invoice_number, user_unique_id, reference_no and due_date
3. Either redirect the user to linkpay_url to complete payment in Everypay, or give the user the invoice PDF (GET /reserved_domains_invoice_pdf) to pay by bank transfer using reference_no
4. Poll GET /long_reserve_domains_status?invoice_number=...&user_unique_id=... to check payment status
5. Once paid, the domains are reserved and registration codes become available

Important behaviors:

• Only available domains are included in the invoice (unavailable ones are filtered out)
• The available_domains field in the response shows which domains were actually included
• Price: currently 10 EUR per domain
• If some requested domains overlap with existing unpaid invoices, the system reuses the same invoice number
• If overlapping domains already have a paid invoice, the request is rejected

What to store: Save both invoice_number and user_unique_id — they are required to check payment status and retrieve registration codes later.

Checks the payment status of a long-term domain reservation invoice and returns registration codes once paid.

How to use:

1. After redirecting the user to the Everypay payment page, poll this endpoint periodically
2. When the response status changes to paid, the registration codes are available
3. Display the reserved_domains array to the user, filtering by status: "reserved"

Response variants:

• paid — Invoice is paid. The response includes reserved_domains with registration codes and domain statuses (reserved, registered, or expired).
• Any other status (pending, unpaid, failed, error, cancelled) — Invoice is not yet paid. The response includes the names array (plain list of domain names without registration codes).

Side effect: When the invoice status is paid, calling this endpoint also triggers the creation of reserved domain records if they haven't been created yet (idempotent operation).

Note: For short-term (free) reservations, use GET /api/v1/business_registry/reserve_domains/{user_unique_id} instead.

Generates and returns a PDF invoice for a long-term (paid) domain reservation. The PDF is produced on the fly — the registry does not persist it.

Preconditions:

• The invoice must be pending (not paid yet) or paid. A cancelled or failed invoice returns 422 Unprocessable Entity.
• The invoice_number + user_unique_id pair must match an existing invoice, otherwise 404 Not Found is returned.

PDF layout: The PDF header shows the invoice number and the EIS logo. The details block contains the invoice number, invoice date (Arve kuupäev), due date (Maksetähtaeg), payment reference number (Viitenumber) and payment status (Makse staatus: Tasumata before payment, Tasutud after payment). The customer block (Arve saaja) shows name, address and VAT number. The main table lists the domain names with their status (Ootab tasumist before payment, Reserveeritud after payment) and price, followed by "Ridade summa", "Käibemaks" (VAT, rate read from registry settings), "Summa kokku" and either "Tasuda" (amount due, before payment) or "Tasutud summa" (amount paid). The footer lists EIS's own billing details (juridical name, address, reg. no, VAT, contacts, bank/IBAN/SWIFT). To pay by bank transfer, use the IBAN from the footer and the reference number from the details block. An unpaid invoice also contains a notice (in Estonian and English) that issuing the invoice does not guarantee the reservation: reservation is first-come-first-served, and if it is no longer possible when the payment arrives, the invoice is cancelled and the payment is refunded.

Customer details (optional query parameters): The Business Registry passes the customer name, address and VAT number as query parameters so that the PDF reflects the actual invoice recipient. If these are omitted, placeholders ([Kliendi nimi], [Kliendi aadress], [Kliendi VAT number]) are rendered. For private individuals, pass private_individual=true — the customer block is replaced with the single word eraisik and the other customer fields are ignored.

Response: Binary PDF with Content-Type: application/pdf and Content-Disposition: attachment; filename="invoice-<invoice_number>.pdf".