Ship opt-in Screen Blasts from your stack
Headless Partner API for CRM / SaaS backends. Full Client API for native macOS & iOS apps — the same contracts the Chrome extension uses in production.
https://api.blasts.app
/api/v1/partner/* · Client routes: /api/ping/*
https://b2b-leads-licenses.netlify.app
What’s in the box
Signed webhooks
Push message.read, dismiss, reaction, and enrollment events to your endpoint — Stripe-style HMAC verification.
Per-employee tokens
Mint revocable emp_live_… seat tokens so native sender apps never embed the org API key or HMAC secret.
Server outbox
GET /messages for partners; POST /api/ping/outbox for client apps — delivery status without a local-only journal.
Attachments
Upload images & PDFs via /api/ping/attach/upload, stamp URLs into the send payload (up to 5 per blast).
Near-realtime
Long-poll /api/ping/events/wait plus Web Push / FCM doorbells. No busy-spin inbox polling required.
Consent-first
No blast without recipient opt-in. Enrollment links + Invite Codes. Revoke anytime — senders discover via pairing-sync.
Two lanes — pick the right one
Partner API (server → Blasts)
- Org key + HMAC or employee seat token
- Enrollment → send → webhooks / outbox
- Prepaid partner credit ledger
- Ideal for FedEx-style transactional alerts
Client API (app → Blasts)
- Email + OTP +
machine_id+ session JWT - Inbox, send, pairing, outbox, attachments
- Same path the Chrome / Edge extensions use
- Ideal for native macOS / iOS recipient & sender apps
Industry
Property managers
Rent, maintenance, renewals for opted-in tenants. Landing →
Government
County & municipal citizen alerts. Landing →
Logistics
TMS / 3PL exceptions, ETA, POD. Landing →
FinTech
Fraud, ACH, KYC, statements. Landing →
Colleges
Enrollment, grades, financial aid, campus safety. Landing →
Newsletters
Issues, flash editions, renewals beside your ESP. Landing →
CRMs
Renewals, deal alerts, onboarding, dunning. Landing →
Get credentials
Partner credentials are provisioned by Tips Marketing (owner admin). Contact
AL@SavingsSites.com with your
partner_id, display name, and platform sender email.
Keys and signing secrets are shown once at create time.
Sandbox: ask for a pk_test_* partner to integrate without spending credits
(0 cost, 100 sends/UTC-day, bodies marked [SANDBOX]). See
Auth → Sandbox.