A real REST API, not a CSV export
Contacts, events, tickets, sponsors and speakers — accessible with your own API key and HMAC-signed webhooks, to connect Aluna with what you already use (your CRM, your BI, your automation). Available on the Business plan.
List your contacts with one call
curl https://aluna.events/api/v1/contacts \
-H "Authorization: Bearer ck_live_xxxxxxxxxxxxxxxx"
{
"data": [
{ "id": "cta_...", "name": "Elena Vasquez",
"emails": [{ "value": "elena@example.com", "type": "work" }],
"company": "Northstar Analytics", "title": "VP of Product" }
],
"next_cursor": "eyJ1cGRhdGVkX2F0Ijoi..."
}Contacts
GET/POST /api/v1/contactsGET/PUT/DELETE /api/v1/contacts/:id
Events
GET /api/v1/eventsGET /api/v1/events/:id
Tickets
GET /api/v1/tickets
Sponsors
GET/POST /api/v1/deals
Speakers
GET /api/v1/speakers
Activities
GET/POST /api/v1/activities
Cursor-based pagination (keyset over updated_at,id) for large lists without duplicating
or skipping rows under concurrent writes — traditional offset/limit is also available
for compatibility.
Find out the moment it happens, not on your next sync
Subscribe to events (contact created, ticket sold, sponsor moved to a new stage) and receive a POST signed with HMAC using a secret unique to your organization — you verify the signature before trusting the payload, just like Stripe or GitHub.
About the API
What resources does the public API expose?
Contacts, activities, events, tickets, sponsors (deals) and speakers — all authenticated with your own API key (Bearer ck_live_...) with configurable permissions (scopes).
Which plan includes API access?
The Business plan. Other plans use Aluna's interface directly, with no extra usage limit because of that.
How do I know a webhook really comes from Aluna?
Every webhook is signed with HMAC using a secret unique to your organization — you verify the signature before trusting the payload, just like Stripe or GitHub.