A handwritten card is one API call.
Post the recipient and the exact words. We write it with a real pen, stamp it and mail it, and you can read its status at any time.
- POST /api/v1/notes. Recipient, the exact message (up to 500 characters) and optional context for your records.
- Idempotency-Key header. The same key and body returns the same note. A changed body under an old key is refused, never sent twice.
- Address checks. US addresses are verified and standardized; an undeliverable one is rejected and nothing is created.
- Readable status. GET a note to see created, written or mailed.
- Per-team workspace. Your own keys, card designs, return address and billing, plus a portal for everyone who is not writing code.
- Test keys. The same validation as live, but notes are never written, mailed or billed; they move to printed and mailed a minute apart so you can test your handlers.
- Signed webhooks. An event for every status change, signed with HMAC-SHA256, retried for about two days.
curl https://you.notecardhq.com/api/v1/notes \ -H "Authorization: Bearer $NOTECARDHQ_API_KEY" \ -H "Idempotency-Key: first-sale:usr_8213" \ -H "Content-Type: application/json" \ -d '{ "recipient": { "firstName": "Sam", "address1": "123 Main St", "city": "Austin", "state": "TX", "postalCode": "78701", "country": "US" }, "content": "Hey Sam, congrats on your first sale! ..." }'
Let an agent send the card.
- MCP server. Connect Claude or any MCP client to
https://app.notecardhq.com/api/mcpwith your API key; the key picks your workspace. Tools:send_noteandget_note. Listed in the official MCP Registry ascom.notecardhq/notecardhq. - OpenAPI spec.
/api/v1/openapi.jsonon your workspace, for SDK generators, Postman and agent frameworks. - Same safety rails. Agents go through the same validation, idempotency keys and address checks as your code.
{
"mcpServers": {
"notecardhq": {
"type": "http",
"url": "https://app.notecardhq.com/api/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Send a card when something happens in your tools.
Zapier
Send a card from any of thousands of apps with a Webhooks by Zapier step. A native notecardHQ app is coming.
See the recipe →Stripe
Thank customers after a Checkout payment with a webhook handler and one API call.
See the recipe →Shopify
Send a card for new orders or first-time customers from the orders/create webhook.
See the recipe →HubSpot
Send a card from a workflow with a custom code action, on Data Hub Professional or Enterprise.
See the recipe →Salesforce
Call a small Apex action from a record-triggered flow, with your key in a Named Credential.
See the recipe →Klaviyo
Add a webhook action to a flow; a relay step in n8n or Zapier adds the Idempotency-Key.
See the recipe →Pipedrive
Send won deals from an automation's webhook action through a relay step in n8n or Zapier.
See the recipe →Attio
Call the API straight from a workflow's Send HTTP request block.
See the recipe →n8n
Add an HTTP Request node to any workflow; retries never send twice.
See the recipe →Make
Use the HTTP Make a request module in any scenario.
See the recipe →Build with a test key, then go live.
Build with a test key
Same API, same validation, nothing written or mailed. Test retries, refused requests and your webhook handler.
Send one to yourself
Point the first real note at an address you control and watch it move through the portal.
Turn on the trigger
Wire the call to the event that should send a card, and let the robots take it from there.
Get your API key.
Tell us what you want to send and we will set up your workspace and key.