UniOne
MESSAGING · MESSAGING
Transactional email sends, templates, suppressions, and sending domains on their key.
Connect UniOne with Fabriq Developer
Your user pastes their UniOne credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting UniOne in practice
UniOne pins a request to 10 MB and 500 recipients, and its email validation path is separately capped at two concurrent requests with a five-second server response limit, so validating a list is inherently serial. The base URL also pins the data region — api., eu1. and us1.unione.io are three different hosts, not one endpoint with a parameter.
Scopes that draw scrutiny
X-API-KEY header (or the api_key JSON field)UniOne accepts the key either way, which means it can end up in a logged request body as well as a header.user API keyTaken from account settings and valid across the account’s projects, so it is the wider of the two key types.project API keyTaken from the Projects page and scoped to one project. The narrower choice for an agent, and the one to ask for.
Rate limits
- Maximum request size: 10 MB. Over it returns 413.
- Up to 500 recipients per email request.
- Email validation: maximum 2 concurrent requests, with a 5-second server response limit.
- Over the rate limit returns 429 Too Many Requests, with the instruction to slow the request rate.
Worth knowing
- The three base URLs are regional; picking one decides where the data is processed, so it is a compliance choice rather than a latency one.
- 413 for an oversized request and 429 for too many requests are different failures with different fixes — split the batch, or slow down — and code that retries both identically will loop on the first.
- 403 Forbidden means insufficient rights on a valid key, distinct from 401 for a bad key, so permission problems and credential problems are distinguishable if you check.
- Two concurrent validation requests with a five-second ceiling each means list hygiene runs at roughly 24 addresses a minute in the worst case.
Checked against UniOne Web API reference (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put UniOne behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.