Bento setup
Bento is Mimeo's first supported sending provider. Connecting it takes three credentials and a verification click.
Connect it
- Go to Settings → Provider.
- Choose Bento.
- Enter your Site UUID, publishable key, and secret key from your Bento account.
- Click Verify connection. Mimeo makes a live call to confirm the credentials work — don't skip this and find out at send time.
- Assign it the one-off sending duty. Until a provider holds that duty, nothing sends.
All three credentials are encrypted at rest in your instance database. They're never displayed back to you in full after saving.
What Bento does
- One-off and broadcast sending. Bento accepts the finished message and delivers it.
- Send-time suppression. Bento checks its own suppression list at send time, a second line of defense behind Mimeo's.
- Per-address suppression read. Mimeo can ask Bento whether a specific address is suppressed on its side.
- Unsubscribe push. When someone unsubscribes in Mimeo, the opt-out is pushed to Bento via its commands API so both sides agree.
-
RFC 8058 headers. Bento injects its own
List-Unsubscribeheaders, giving mail clients the native one-click unsubscribe button.
What Bento can't do, and how core covers it
No webhooks — suppression syncs by polling
Bento doesn't push status changes to Mimeo, so Mimeo pulls. Suppression state is reconciled two ways: lazily, when you open a person who was emailed recently, and on a nightly sweep. Practically, that means a bounce or provider-side unsubscribe shows up in Mimeo within a day, or immediately if you happen to look at that person.
Silent suppression drops
Accepted is not delivered. If Bento has an address suppressed on its side, it accepts the send and then drops the message silently — no error comes back. Your send log will show the send as accepted. This is why suppression sync matters and why the send log is labeled as acceptance, not delivery.
No engagement read API
Bento won't tell Mimeo who opened or clicked. It doesn't need to — Mimeo injects its own open pixel and wraps its own links, and Mimeo's tracking is authoritative. Any engagement numbers you see in the Bento dashboard are Bento's separate measurement of the same sends; the stats in Mimeo are the ones its own features act on. See Tracking.
No deletion API
Bento offers no way to delete a subscriber programmatically. When you erase a person in Mimeo for a GDPR request, Mimeo surfaces a manual-cleanup notice telling you what to remove in Bento yourself. The request isn't complete until you do.
Rate limits
Bento's limits are respected automatically — Mimeo batches and paces sends for you, so there's nothing to configure and no way to accidentally exceed them from the UI.
| Limit | Value |
|---|---|
| Emails per request | 60 |
| Emails per minute | 60 |
For technical detail on how sends through Bento behave — including the UTM parameters and pixel Bento adds on its own — see Bento API notes.