# Paydro: start here

Paydro helps organizers sell tickets, collect registrations and manage events and attendees. Choose the goal below, then read its guide and only the reference material needed for the task.

## Access and supported approaches
- Public shop links, buttons and iframes need no organizer API credentials. Organizer API calls use the organization's HTTPS origin and authorized HTTP Basic credentials kept server-side.
- The developer host serves documentation, not account API requests. Event UUIDs and public shop slugs are different identifiers. Local `https://developer.test.test` is a development origin, not a public sandbox.
- Public API-key issuance, Paydro OAuth client registration and registration webhook subscriptions are not offered by the current documentation. Some workflows require organizer UI steps; do not invent endpoints.
- Establish organization, role and affected records. Read current capabilities before writing; inspect response bodies and verify outcomes before retrying uncertain writes. Respect the request's scope for publication, messages and financial changes.

## Interpret the request
- **Ticket / attendee / order:** entitlement, individual registration and payer-level booking. An invitation is an offer, not necessarily a reservation or completed registration.
- **Cancel / refund:** distinguish invalidating admission, correcting a price, creating a credit document and returning money.
- **Invoice / paid / payout:** distinguish an invoice after online payment, pay-later registration, a credit document and organizer settlement. Customer payment, provider payout and Paydro settlement are separate facts.
- **Limit / closed:** distinguish code uses, quantity per order, cumulative product allocation, stock and expiry; sales closure is not financial settlement.
Resolve ambiguity that changes the action. Historical support workarounds and account-specific exceptions do not establish current product behavior.

## Choose a goal
For website ticket sales, follow the conversation in the selling guide: ask for a missing shop link, then the widget choice, before generating code. Respect plan-only and no-file-change requests.
- [Sell tickets on my website](sell-tickets.md)
- [Use an existing shop link](use-shop-link.md)
- [Find my shop link in Paydro](find-shop-link.md)
- [Create a ticket shop for my website](create-ticket-shop.md)
- [Create a Paydro account](create-paydro-account.md)
- [Show our events](show-events.md)
- [Set up an event](set-up-event.md)
- [Manage ticket options](manage-tickets.md)
- [Collect attendee information](collect-attendee-information.md)
- [Match our branding and language](branding-and-language.md)
- [Manage guest registrations](guest-registrations.md)
- [Help customers with bookings](help-with-bookings.md)
- [Handle cancellations and refunds](cancellations-and-refunds.md)
- [Communicate with attendees](communicate-with-attendees.md)
- [Connect our other tools](connect-other-tools.md)
- [Understand event performance](event-performance.md)
- [Accept invoice payments](accept-invoice-payments.md)
- [Configure payment providers](configure-payment-providers.md)
- [Understand payouts and settlement](understand-payouts.md)
- [Prepare financial records](financial-records.md)
- [Manage entry at the event](manage-entry.md)
- [Fix and verify an integration](fix-integration.md)

## Broader documentation
- [API basics](https://developer.paydro.com/en-us/docs/api-basics.md), [authentication](https://developer.paydro.com/en-us/docs/authentication.md) and [permissions](https://developer.paydro.com/en-us/docs/permissions.md).
- [API coverage and limits](https://developer.paydro.com/en-us/docs/api-coverage.md), [OpenAPI contract](https://developer.paydro.com/openapi/v2.json) and [all guides](https://developer.paydro.com/llms.txt).
Every developer guide is available as `/en-us/docs/<topic>.md`; use the published contract for fields and response shapes.

## Completion
Verify the outcome with an authorized test setup; explain remaining UI steps or unsupported capabilities. Keep personal data, credentials and private download URLs out of public output.