Let Alaska tell your systems what just happened
Webhooks notify an endpoint you choose when games, SKUs, companies or requests change, or when keys are ready. Every delivery attempt is logged, so you can always see what was sent.
Your systems shouldn't have to keep asking
Without events, keeping other tools in step with Alaska means polling or re-keying.
Polling for changes
Checking again and again for updates wastes resources and still leaves you behind.
Tools that don't talk
Your ERP, CRM and chat each know part of the picture, and nothing joins them up.
Did it send?
When an integration goes quiet, you need to see exactly what was sent and when.
Four steps to event-driven key ops
Choose events
Games, SKUs, companies, requests or keys ready.
Add an endpoint
Point them at a URL in your stack.
Alaska notifies
Event data is sent as changes happen.
Every attempt logged
See each delivery attempt and its response.
Simple to set up, easy to check
Run your own code when the events that interest you happen in Alaska.
Catalogue and request events
Get notified when your catalogue, partners or requests change, or when keys are ready.
Logged delivery
Every delivery attempt is logged, so you can see what was sent and how your endpoint responded.
Connect your tools
Keep your ERP, CRM, chat or BI tools in step with what's happening in Alaska.
Automation without friction.
“Alaska transformed a complex, manual and very long key ingestion process into an automation, without friction, saving our team hours of manual work on every request.”
Which events can trigger a webhook?
Changes to games, SKUs, companies or requests, and keys being ready.
Can we see what was sent?
Yes. Every delivery attempt is logged.
How are webhooks different from the API?
The API is how partner systems ask Alaska to do something. Webhooks are how Alaska tells your systems something has happened. Most teams use both.
See webhooks in action
Book a walkthrough and we'll show you how webhooks would work with the way your team already manages keys.