Flicker sends your product's transactional email so you don't have to wire up a separate provider. Verify a sending domain, send through one API call, and see every message and its delivery state in one searchable log.
Verify a sending domain
Add a domain under Mail and Flicker gives you the DKIM and SPF
records to drop into your DNS. Once they verify, mail sends as your own domain
(noreply@yourapp.com), not a shared relay address.
Send a message
Send from any app with a single authenticated request to POST /api/v1/mail/send. No SDK to install.
$ curl -s https://flickercloud.com/api/v1/mail/send \ -H "Authorization: Bearer $FLICKER_TOKEN" \ -d from=noreply@acme.com -d to=jo@acme.com -d subject=Welcome -d text=Welcome
Pass text, html, or both. With both, the message carries
each version and the reader's mail client picks the one it can show, which also
scores better with spam filters than HTML alone.
Each organization can send up to 100 requests per minute. Additional requests
receive 429 with a Retry-After header. To protect shared
delivery reputation, Flicker pauses sending if an organization has at least 100
sent messages in the last 30 days and its suppression rate is above 5%. A paused
send receives 403 with the reason; the Domains settings page explains
how to contact Flicker to restore sending.
The message log
The Mail surface lists every message with its status (queued, sent, delivered, bounced) and the domain it sent from. Hard bounces land on a suppression list automatically, so you stop sending to addresses that fail.