Send gifts from Clay

• A partner key (Authorization: Bearer pk_live_...) bound to your Printonic account with the team_orders capability. Gifts are charged to that account exactly like team orders: prepaid wallet (then the saved card) or net terms.
• A Clay table with the recipient's name and email, plus a stable row id or CRM id for the idempotency_key.
• A gift: one of the four Printonic for Teams collections below, or your own product by sku_code.

The recipient enters their own address through a private claim link (emailed by Printonic) and picks options such as size there; nothing ships until the address arrives, and the link expires after claim_expiry_days.

In your Clay table click Add enrichment, search for HTTP API and open the Configure tab. Column values are referenced by typing / in a field and picking the column; Clay shows the reference as /Column Name, which is how the samples below are written. Put quotes around every string reference (Clay requires them; numbers and booleans go without).

• HTTP method POST
• API endpoint URL https://printonic.com/api/external/team-orders/quick
• Header fields add a header account instead of typing the key: Select header account > + Add account, key Authorization, value Bearer pk_live_..., name it and save. Clay stores it encrypted at the workspace level (Settings > Connections) and reuses it across columns; a header typed into the column is visible to everyone who can see the table. Content type is set by Clay (application/json).
• JSON body the template below with your columns referenced
• Field paths to return team_order_id, claim_status, order_id, charged_cents (or leave it empty and pick fields from the cell details afterwards with Add as column)
• Rate limiting for example request limit 30 per 60000 ms, below your key's limit

{
  "idempotency_key": "/Row ID",
  "recipient_name": "/Full Name",
  "recipient_email": "/Email",
  "recipient_company": "/Company",
  "collection": "welcome",
  "message": "/Gift message",
  "sender": "Acme Inc",
  "printed_card": true
}

A missing or blank required value answers a 400 for that row only. To ship your own product instead of a collection, swap collection for sku_code:

{
  "idempotency_key": "/Row ID",
  "recipient_name": "/Full Name",
  "recipient_email": "/Email",
  "sku_code": "PRNTC-7K2M-9QX4",
  "message": "/Gift message"
}

Click Test to run one row (use a colleague's email: the claim email arrives within a minute and money moves on every 201), then run the column on the rows you mean to send. Keep the table's auto-run off, or use Only run if with a formula that checks a "Send" column, so a new row does not send a gift by itself.

Every value is a scalar so a field path can pick it by name: team_order_id (keep it, the status poll uses it), claim_status, order_id, charged_cents. The full team order is nested under detail. A 200 with already_existed: true is the replay of a row that already ran; a 402 means the team order exists but is unpaid.

201 Created
{
  "team_order_id": 77,
  "status": "collecting_addresses",
  "reference": "row_8f3a",
  "recipient_id": 501,
  "recipient_name": "Jane Doe",
  "recipient_email": "jane@globex.com",
  "claim_status": "awaiting",
  "claim_label": "Waiting for address",
  "claim_expires_at": "2026-10-10T12:00:00.000Z",
  "invite_sent_at": "2026-09-10T12:00:01.000Z",
  "order_id": 9001,
  "order_external_id": "ord_00009001",
  "shipment_status": "submitted",
  "shipment_stage": "awaiting_address",
  "tracking_url": null,
  "shipped_at": null,
  "delivered_at": null,
  "total_cents": 5049,
  "charged_cents": 5049,
  "billing_mode": "net_terms",
  "collection": { "slug": "welcome", "name": "The Welcome" },
  "already_existed": false,
  "detail": { "team_order": { ... }, "recipients": [ ... ], "totals": { ... }, "billing": { ... } }
}

Poll. Add a second HTTP API enrichment with method GET and the URL below, inserting the team_order_id column from the first call into the path. Return claim_status (awaiting, claimed, expired), shipment_stage, tracking_url, shipped_at and delivered_at. Re-run it on a schedule (table settings > Run settings > re-run columns on a schedule: daily on every plan, hourly on Enterprise) and give it an Only run if formula such as {{delivered_at}} == "" (run while the delivered date is still empty), so it stops once the gift is delivered. There is no charge for reads.

GET /api/external/team-orders//Team order id/quick
(the URL with the team_order_id column inserted after /team-orders/)

200 OK
{
  "team_order_id": 77,
  "status": "shipped",
  "claim_status": "claimed",
  "claimed_at": "2026-09-11T15:02:00.000Z",
  "shipment_stage": "shipped",
  "carrier": "USPS",
  "tracking_number": "9400...",
  "tracking_url": "https://www.aftership.com/track/9400...",
  "shipped_at": "2026-09-14T17:40:12.000Z",
  "delivered_at": null,
  ...
}

Or receive webhooks. Register an https endpoint with POST /api/external/webhooks for team_order.claimedteam_order.shippedteam_order.deliveredteam_order.needs_attentionand Printonic sends a signed POST as each gift is claimed, shipped and delivered. A Clay table can be the receiver: in a workbook click + Add, search for Webhooks, choose Monitor webhook and copy its URL (add the optional authentication token if you want Printonic's calls checked; a webhook table takes up to 50,000 submissions). Every event lands as a new row carrying data.team_order.id, data.team_order.reference (your row id) and the shipment, which a Lookup single row column in the sending table can join on. Details and the signature sample are on the team orders page.

• idempotency_key is what makes re-running the column safe. Use a value that never changes for the row; never a timestamp. Clay re-runs cells when inputs change or when you update out-of-date cells, and it does not document automatic retries, so treat every run as a possible repeat: with the same key it is a replay, never a second gift.
• Money moves on every 201. Check your wallet balance or credit limit before running a whole table; a 402 leaves the gift unpaid until you fund the account and re-run the row with the same key.
• Cancel a gift before production with POST /api/external/team-orders/{team_order_id}/cancel; the charge goes back to the wallet.
• Clay does not document escaping of referenced values inside a JSON body. Keep free text (the message) short and free of double quotes, or build it with a formula column that strips them.