Search events

Developer: API Keys and Webhooks

Set up Seaty's developer tools for your organisation: create API keys, try endpoints in the playground, and send signed webhook notifications to your own systems.

Overview

The Developer area is where you connect Seaty to your own systems. It has three parts:

  • API keys , credentials your systems use to read your organisation's data (events, orders, attendees, payments) and record external balance payments through the Seaty API.
  • Playground , a place to try the live API endpoints from your browser, with your own key, before you write any code.
  • Webhooks , so Seaty notifies your systems the moment something happens (an order is placed, a ticket is checked in, a payment is recorded), instead of you polling for changes.

Who uses this: an organisation super-admin, usually working with a developer. The deep technical reference lives in the Developer API docs; this page is the organiser-facing how-to for the dashboard.

Finding it: in your organisation admin, open Tools -> Developer. If you do not see it, the Developer API may not be enabled for your organisation yet, contact support@seaty.co.uk.

API keys

  1. In Developer, choose Create a key and give it a recognisable name (for example "Accounts sync").
  2. Decide what it may do. Keys are read-only by default; you can additionally allow recording balance payments and refunds and updating an order's admin note.
  3. The key is shown once. Copy it then and store it somewhere safe (a secrets manager or environment variable). Seaty keeps only a hashed copy, so it can never be shown again.
  4. To rotate or retire a key, revoke it from the list. Use a separate key per integration so you can revoke one without disrupting the others.

Treat a key like a password. Never put it in a public website, a mobile app, or a support message.

Playground

The playground lets you call the live endpoints with one of your keys and see the real responses, a quick way to confirm things work before building an integration. Pick an endpoint, fill in any parameters, and send.

Webhooks

A webhook sends a signed message to a URL you control whenever a subscribed event happens.

  1. Open the Webhooks tab and Add endpoint.
  2. Enter your endpoint URL. It must be https:// and publicly reachable, Seaty will not deliver to localhost or private/internal addresses.
  3. Tick the events you want (for example order placed, ticket checked in, balance payment recorded).
  4. Save. A signing secret (whsec_...) is shown. Your system uses it to verify each delivery really came from Seaty. You can reveal and copy it again from the list at any time.

From the same screen you can disable/enable, edit, delete, and send a test ping to an endpoint. The delivery log shows recent attempts with their status and response code; open one to see what was sent and what your endpoint returned, and to resend it. For successful deliveries the payload is not retained, so a delivered row shows no body.

Your developer should read Verifying the signature and the event catalogue before going live.

When an endpoint keeps failing

If your endpoint keeps returning errors or is unreachable, Seaty retries with increasing delays and then, after repeated failures (about 20 in a row, or failing for roughly a day), automatically disables it and emails your administrators. Fix the endpoint, then re-enable it from this screen, that clears the failure count and resumes delivery. Events missed while it was disabled are not back-filled.

If you ever see a "Webhooks suspended by Seaty" banner, all webhooks for your organisation have been paused (a rare measure). Contact support@seaty.co.uk.