Commerce & Payments · Integration
Cardly
Add Cardly to your product for your customers, and give your AI agents governed access to it.
Cardly prints and posts real greeting cards in a chosen handwriting style, and its API runs on a different domain to the marketing site: requests go to api.card.ly/v2 while the product sits at cardly.net. Auth is an API-Key header, and keys are prefixed test_ or live_, where a test key validates a request and returns testMode true without printing or billing anything, so you can exercise the Place Order path safely. POST bodies must be JSON but the documented Content-type is text/json rather than application/json, which some strict clients refuse to send. Placing an order needs an artwork ID and usually a template ID that must already exist in the account, so a fresh customer cannot send anything until they have uploaded artwork, and orders should carry an Idempotency-Key because a retried send means a second physical card in the post. Rate limiting returns 429 and needs exponential backoff. fastn holds each customer's live and test keys separately, keeps idempotency keys stable across retries, and maintains the connection as the API changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Cardly account so your product can post a physical thank you card when a deal closes.
Send onboarding or renewal cards from a customer's own artwork and handwriting style without them leaving your app.
Sync recipient addresses from your product into Cardly contacts and lists so sends do not need manual data entry.
Show delivery and order status from Cardly against the customer record that triggered the send.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent place a card order for a named recipient using an approved artwork and template, with the order ID, cost and tenant written to a per-tenant audit log.
Have an agent run a proposed send against the test key first and report what would be printed before anything is committed.
Let an agent list recent orders and flag any that were sent twice to the same address.
Example prompt
Send a thank you card to this customer using our standard renewal artwork, and show me what it will say first.
Set up Cardly in 4 steps
- 01Enable the Cardly connector from your fastn dashboard.
- 02Have each customer authorise their own Cardly account, so calls run under their credentials rather than a shared key.
- 03Decide which orders, payments and customers your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Cardly integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Cardly integration without building it. Your customers connect their own Cardly account inside your product and work their orders, payments and customers there, with no per-customer code on your side.
- Handle the part that actually costs time: money and order state must never be double-applied, and reconciliation has to be possible. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Cardly update is not your on-call problem.
- One integration serves your product and your agents. The same governed Cardly connection powers in-product features and gives AI agents scoped, audited access, so you keep commerce and payment records in step with your product without wiring it twice.
Used by these teams
Compare with
Shopify
Stripe
BigCommerceOften used alongside
Tools the same teams tend to run next to Cardly, across other categories.
NetSuite
Notion
Box
DocusignCardly integration FAQ
How do I add a Cardly integration to my product?
Enable the Cardly connector in your fastn dashboard, then let each customer authenticate their own Cardly account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Cardly client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Cardly account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Cardly account and only ever sees their own orders, payments and customers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Cardly integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent place a card order for a named recipient using an approved artwork and template, with the order ID, cost and tenant written to a per-tenant audit log.
Who maintains the Cardly integration?
fastn does. When Cardly changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Cardly integration safe for payment and order writes?
Writes are idempotent, so a retry cannot double-charge or duplicate an order, and every call is logged per tenant so a transaction can be reconciled against the event that triggered it.
Can my product react to a new order, payment or refund immediately?
Yes, through event triggers, so fulfilment, entitlement or accounting steps run as soon as the event lands rather than on a nightly sync.
What can I build with the Cardly integration?
A common starting point: let a customer connect their own Cardly account so your product can post a physical thank you card when a deal closes. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Cardly integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Cardly does not change your per-connector cost. You can start free with 3 connected accounts.
Add Cardly to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.