Intelliprint
MESSAGING · MESSAGING
Letters and postcards printed and posted in the UK from the account they connected.
Connect Intelliprint with Fabriq Developer
Your user pastes their Intelliprint 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 Intelliprint in practice
Intelliprint is essentially one endpoint — POST /prints — that turns HTML, text or a PDF into physical post, and the only safe way for an agent to exercise it is testmode=true, which runs the whole validation and processing pipeline without printing or charging. The constraint to design around is the 3pm cutoff for same-day dispatch rather than any request rate.
Scopes that draw scrutiny
Live API key (bearer)Every successful call spends real money on paper and postage and cannot be recalled once dispatched. Intelliprint issues separate keys per environment, so the test key is the only sane default for an agent.
Worth knowing
- One /prints call can carry thousands of recipients inline or reference a previously uploaded mailing list, with no extra charge for consolidating, so per-recipient calls are pure waste.
- Addresses are verified against the Royal Mail database at submission, so a malformed address fails loudly rather than being quietly mis-delivered.
- Webhooks are delivered through Svix, so signature verification follows Svix’s scheme rather than a house-built HMAC.
- Versioning is in the URL path (/v1/), breaking changes get a deprecation window, and non-breaking additions ship immediately — so clients have to tolerate new fields appearing without notice.
Checked against Intelliprint API (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 Intelliprint behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.