Webhook or API
A webhook sends a message when something happens. When your integration needs to read or change something in Idun, it uses the API.
Webhooks
You choose which events a webhook sends, and the receiving system gets only those. They can be new members, purchases, enrolments, completed lessons and courses, form responses, tags added or removed, email opens and clicks, page visits, bookings and cancellations, cancelled subscriptions, failed payments, trials about to end, members who haven’t been active for a while, and who came or didn’t come to a live event.
Every request is signed with the webhook’s signing secret (HMAC SHA-256), so the receiver can check that it came from Idun. The delivery history shows every delivery with the receiver’s response, and there you can filter by event and status code and send a test request.
API keys
You create API keys under Settings → For developers, which also holds your webhooks and the API documentation. A key reaches only your account. For each key you choose what it may read and change, and whether it may publish.
Your own AI through MCP
The same API is available as an MCP server, so your own ChatGPT or Claude can work in your account with the permissions you give it. Read more about AI in Idun.
