Developer path
Install WalletAlert with one line.
Give your team a small first integration: mount WalletAlert, pass wallet context, receive delivery events, and port notification history when rollout needs it.
One-line mount
The first integration is intentionally small.
Start with a script beside the wallet control. Add webhooks, notification history, and richer event sources only when rollout needs them.
<script src="https://api.ekko.zone/static/provider/walletalert.js" data-walletalert-id="provider_live" data-wallet-context="approved"></script>- Mount
- Provider widget
- Context
- Wallet/session
- Return path
- Webhook events
What engineers need to evaluate
Evaluate the integration from the first mount to the first measured action.
- 01
Pass wallet context
Send approved wallet, account, cohort, and product-state context to Ekko.
- 02
Receive webhook events
Route delivered, suppressed, acted, dismissed, and missed outcomes into your systems.
- 03
Port notification history
Bring previous notification records into Ekko so the next alerts start with context.
- 04
Widen integration
Add APIs and event sources after the first WalletAlert flow proves value.
Developer surfaces
APIs and webhooks support the flow; they are not the headline.
WalletAlert Integration
Mount the user-facing alert surface beside the wallet control.
Webhooks
Send delivery and action outcomes into support, product, and ops systems.
API Overview
Evaluate message plans, audiences, routing, and proof with current public paths.
Ship the small integration first.
Prove one wallet-scoped alert in your product before committing to deeper API work.