Stello for developers
Webhooks
Stello sends a signed HTTPS POST to your server whenever something happens in an organisation you work with, so your own systems can stay in step without anyone retyping anything.
API version 2026-09-01
The contract is additive. New fields and new event types appear over time; existing field names and their meanings do not change. You do not need to pin a version, and there is nothing to migrate when we ship something new.
Anything marked Removed is a change that can break a working receiver. We contact affected organisations before shipping one, and it should be vanishingly rare. Everything else is safe to ignore until you want it.
- AddedNew family `person` with one type, `person.email_changed`. Sent when someone changes the email on their Stello account, and only to organisations where they currently hold a membership or a ticket to an upcoming event. It carries a new `person` object with `id`, the new `email` and `previous_email`. As a new family it reaches nobody until you subscribe to it; `membership.*` and the other wildcards do not include it.
- Added`order.buyer.id` and `membership_pass.member.id`: a stable identifier for the person, `per_…`. People can now change the email on their Stello account, so an email is no longer a safe key for a member register. The id never changes, and it is unique to your organisation. Match on it; keep the email for contact.
- Changed`membership_pass.order_id` can now be null. An organisation can hand a membership out for free from their dashboard, and such a pass has no order behind it — no receipt, no payment. Every other field is unchanged, and a pass that was bought still carries its order as before. If you parse the payload against a strict schema, widen this field before enabling the feature for your organisation.
- Added`membership_pass.issued_reason`: the organisation’s own short label for why they gave the membership away ("æresmedlem", "styret"). Null on a pass that was bought, so the pair of fields tells a comped member from a paying one.
- RemovedThe `order` object no longer carries `total_amount`, `fee_amount` or `source`. The buyer’s charge includes the service fee and, on a Klarna order, a flat premium that is ours rather than the organisation’s — so two identical orders differed by 10 kr depending on how the buyer chose to pay, which made the payment method inferable from the amount. Read `listed_amount` for the sale price and `amount_to_org` for the organisation’s share.
- Added`order.listed_amount`: subtotal minus discount, in øre. What the organisation sold it for, and the same basis their own dashboard reports revenue on.
- AddedEndpoints can be scoped to specific memberships or specific events. Scoping is invisible to the receiver: a scoped endpoint simply receives fewer deliveries, and the payload is unchanged.
- api_version 2026-09-01
- AddedFirst public release. Multiple endpoints per organisation, one signing secret each, and the seven event types across memberships, orders and events.