# Set up an event

Create or copy an event, then configure and review it before opening sales.
Start with [summary](summary.md); obtain the company, name, dates, timezone and currency.

## Workflow
1. Check organizer permissions and the correct company hostname.
2. POST `/events/add.json` with the documented `Event` fields.
3. Require `ok:true` and retain the returned `event_id`; read the event back.
4. Alternatively POST `/events/duplicate/{event_id}.json` for an authorized existing event; retain the returned `id`.
5. Configure [ticket options](manage-tickets.md) and [registration questions](collect-attendee-information.md).
6. PUT `/{event_id}/events/edit.json` for allowed changes; send both dates when changing dates.
7. Review public information, ticket availability, sender details and checkout in the organizer UI.
8. When opening sales is within the request, PUT `/{event_id}/events/status/open.json` and verify the shop.

## Limits
Creation and publication are separate operations. Opening can require company clearance.
Transitioning a concept/test event can clean concept test state; review before publishing.
Use `close` or `sold_out` only for the intended shop status change.
Protected settings are filtered; a successful response does not prove every submitted field changed.
Do not retry a timed-out creation until checking whether an event was already created.

## Duplication and lifecycle consequences
After duplication, review the destination organization, payment setup, invoice details, sale dates, copied questions and integrations.
Do not assume source payment credentials or external mailing connections carry over; validate the destination's configuration before publication.
Use [provider setup](configure-payment-providers.md) for readiness checks and the actual collection route.

Closing sales, marking the shop sold out and financial settlement are different states; follow [payout guidance](understand-payouts.md) for the financial outcome.
A future ticket sale date can hide tickets even during preview. Inspect it without changing the event date just to make a test succeed.
Opening a concept event can remove its test registrations; review that consequence before publishing and do not use real payments to test it.
Date changes can affect reporting and financial documents. Do not move the event date as an undocumented workaround for payment or settlement restrictions.
Do not assume an event with existing orders can be deleted; preserve its order and financial relationships.

## Verify
Read the resulting ID, name, dates, timezone and currency; verify ticket configuration and shop status separately.

## More documentation
- [Events and writable fields](https://developer.paydro.com/en-us/docs/events.md)
- [Event/catalog recipe](https://developer.paydro.com/en-us/docs/integration-recipes.md)
- [Writing data](https://developer.paydro.com/en-us/docs/writing-data.md)