Connect in-app, react to events, call the API
In-app notifications
Client-side. Drop the SDK into your dApp, authenticate the wallet (EVM or Solana), and show live notifications. The fastest path to a visible result, about ten minutes.
Webhooks
Server-side, receive. Subscribe your endpoint to platform events, delivered, viewed, contact created, and verify the signature. React from your backend without polling.
Server-side API
Server-side, send. Authenticate with a secret key and call the API: register wallets, ingest consented captures, send pushes, launch campaigns.
Which one do I need?
The two credentials are not interchangeable. A publishable key (
pk_…) is safe in the browser and only runs wallet auth. A secret key (sk_…) is server-only and grants full API access. Never ship a secret key to a client. See API keys.A typical build order
1
Add the SDK
Wallet-authenticated notifications in your dApp, in two lines. Start here.
2
Send events from your product
Push signups, deposits, and upgrades with a secret key, and let automations turn them into messages. See custom events.
3
Collect email, with consent
Bind a capture form to a list so wallet-first contacts become email-reachable.
4
Close the loop with webhooks
Receive platform events at your endpoint and react. See webhooks.