Thanks.io API
Thanks.io runs an open direct mail API: public reference and OpenAPI spec, self-serve pay as you go signup, bearer tokens plus OAuth 2.0 clients, and webhook delivery. The gaps are small: sandbox and deprecation policy stay undocumented.
Frequently asked questions
Thanks.io scores B+ on Supergood's API Report Card. Thanks.io runs an open direct mail API: public reference and OpenAPI spec, self-serve pay as you go signup, bearer tokens plus OAuth 2.0 clients, and webhook delivery. The gaps are small: sandbox and deprecation policy stay undocumented.
Thanks.io has a workable official integration path. Most engineering teams can build against it directly. Solid API with minor gaps
Thanks.io is a direct mail automation platform that sends handwritten style postcards, letters, and notecards on behalf of businesses, with an AI Studio for creative generation according to its homepage.
Marketing and sales teams that want physical mail triggered from software rather than from a print vendor relationship, plus SaaS products and agencies that embed sending on behalf of their own customers. Teams create a Personal Access Token in API Settings and post to endpoints such as /api/v2/send/postcard with recipients, a message, and a front image URL to trigger a physical send.
Public sources carry no customer counts, revenue figures, or named logos for Thanks.io, so its footprint reads qualitatively as a focused direct mail automation tool that reaches wider workflows through its HubSpot, Zapier, Make, and n8n connections.
The system of record here holds recipient contacts and mailing lists, mailpiece send orders and their delivery status, creative templates and hosted image assets, automation workflow definitions that decide who gets mailed and when, and the prefunded API usage and billing records tied to each send.
The developer surface looks current rather than legacy: endpoints are versioned under /api/v2, the documentation site publishes an OpenAPI specification plus an llms.txt index built for machine consumption, and the pricing page references an MCP server for AI agents.
Common alternatives include Lob, PostGrid, Postalytics, Handwrytten. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Not that we could find. There is no official Thanks.io MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Thanks.io doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.