API & webhooks
LiveAn event management API with signed webhooks.
Read events, guests, replies and check-ins, add and update guests from your own systems, and receive a signed message the moment something happens at the event.
- REST API v1
- Thirteen webhook events
- Professional and Agency
POST /winglark HTTP/1.1
Winglark-Signature: t=1762338012,v1=5f2b…c9e1
Winglark-Event: rsvp.submitted
Winglark-Delivery: 7c1e9a42-…
{
"type": "rsvp.submitted",
"created_at": "2026-11-05T18:40:12.481Z",
"event_id": "6f1c2a7e-…",
"data": {
"response": "yes",
"party_size": 2,
"guest": { "first_name": "Ada", "email": "a•••@example.com" }
}
}Contact details stay masked unless the endpoint is allowed to see them.
What it does
Your systems, kept up to date by the event itself.
Everything here works today on the Professional and Agency plans.
- Read the event
- Events, guests, replies and check-ins, paged with a cursor so a large list arrives in pieces.
- Write the list
- Add or update guests from a ticket site, a CRM or a form. An idempotency key makes a retry harmless.
- Hear it happen
- Webhooks for replies, invitations, the door, tickets, seating and badges, signed with a timestamp.
- See every delivery
- A log with each status and attempt, redelivery, a test event, and failing endpoints paused.
How it works
Three steps.
- Create a keyIn Integrations, choose its scopes and, if you like, an expiry date. Copy it: it is shown once.
- Add an endpointGive the HTTPS address and the events it should hear. Send a test event to check the signature.
- Build on itCall the API with the key and act on each webhook. The developer reference has every route and field.
In the product
Keys, webhooks and every delivery, on one screen.
Integrations sits in the workspace settings. A key is created with the scopes it needs and shown once; an endpoint is given the events it should hear; the delivery log shows what was sent, what came back and what is being retried.
Illustrative workspace, keys and deliveries. The screens are drawn from the product as it works.
What you need
A workspace on the Professional or Agency plan, and someone who can receive an HTTPS request. Free, Starter and the Single Event do not include the API.
Open the developer reference →Integrations →Compare the plans →
The events an endpoint can subscribe to
- guest.created
- guest.updated
- guest.archived
- rsvp.submitted
- invitation.sent
- invitation.delivered
- invitation.bounced
- checkin.admitted
- ticket.issued
- event.published
- event.cancelled
- seatmap.published
- badge.printed
Questions
Is there a REST API for event guest lists?
Yes: list, read, create and update guests per event, and read replies and check-ins. Responses are JSON, lists use cursor pagination, and creates accept an idempotency key.
How are webhooks signed?
With an HMAC over a timestamp and the raw body, sent in the Winglark-Signature header. Rotating the secret keeps the old one valid for an overlap, so nothing is dropped while you switch.
Are there rate limits?
Yes, per key. A request over the limit is answered with status 429 and can be repeated after the wait the response gives.
Can a key be limited to reading only?
Yes. A key carries only the scopes it was created with — for example events and replies to read, and nothing to write.
Give your systems a key.
On Professional and Agency, from the workspace settings.