Your Ads Flow into Highly Targeted
& Consented Messages, that Get Read!
A server-to-server REST API for ad networks, affiliate platforms, DSPs — and advertisers placing their own offers directly. Push offers programmatically from your stack — each one rides as a clearly labeled sponsored footer at the end of Blasts messages, whether business, personal, family, or friends, that recipients explicitly opted in to receive. Geo, demographic, and business-category targeting included. Post-paid billing off a per-ad ledger.
POST https://api.blasts.app/api/ping/ads/placement
create · update · delete · list · ledger
— authenticated with a Bearer API key + HMAC-SHA256 request signature.
What your advertisers' ads look like
Blasts is opt-in, screen-to-screen messaging — business and personal alike. When a Blast is delivered, one matched sponsored offer is appended after the message body — labeled, separated, and never replacing or interrupting the message itself.
AD
Why ad networks & advertisers integrate
Pure server-to-server
Your platform calls one REST endpoint. No SDK, no pixel, no browser code, no creative hosting on our side required — a standard HTTPS POST from your ad server.
Consented audience
Every recipient explicitly opted in to receive Blasts from the sender. Your advertisers' offers reach real, engaged conversations — not cold inventory.
Real targeting
ZIP lists, ZIP-radius (mile-based), resident demographics (gender, age band), and business firmographics (org size, role, B2B/B2C, 29 business categories).
Weighted auction
Each placement carries a payout_weight. Among ads that match a recipient,
the highest weight wins the slot; ties break randomly.
Post-paid ledger billing
No prepay. Pull your per-ad sends, views, and clicks any time with the
ledger action and settle monthly. A hard monthly send cap bounds your exposure.
Instant retraction
Delete a placement and it leaves rotation within about a minute. Every ad also carries a mandatory expiry (30 days max) — nothing runs stale.
Audio commercials, too
A placement can carry an optional hosted audio spot (HTTPS audio_url, up to
10 minutes) instead of — or alongside — text creative. Recipients see a labeled
"Sponsored — audio from advertiser" block with a Listen player.
How onboarding works
- Email us at AL@SavingsSites.com with your company name and expected monthly volume. We provision your partner account with ads enabled and agree on your payout ceiling and monthly send cap.
- Receive credentials — an API key (
Authorization: Bearer …) and an HMAC signing secret. They are shown once; store them like any other production secret. Sandbox credentials are available on request for integration testing. - Push placements —
POST /api/ping/ads/placementwithaction: "create". Up to 100 live placements at a time, updated or retracted whenever you like. - Reconcile — call
action: "ledger"for per-deal sends, views, clicks, 7-day and month-to-date rollups. Billing is post-paid from these numbers.
What this API is not
- It does not send messages. Senders write their own Blasts; your ad is a footer on messages that were already being sent.
- It is not an open exchange. Partners are provisioned manually, content passes a family-safe filter, and payout weights are server-clamped to your agreed ceiling.
- It does not expose recipient data. Targeting is evaluated on our servers; you never see who received an ad — only aggregate sends, views, and clicks.
Read the API Reference, grab the signed-request examples, then email AL@SavingsSites.com for credentials. Most platforms are live in under a day — it's one endpoint.