curl --request POST \
--url https://uat-api.clinkbill.com/agent/platform/authorizations \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"request_id": "platform-ref-001",
"title": "Office supplies budget",
"description": "Monthly office supplies purchase",
"payment_instrument_id": "pi_...",
"is_recurring": false,
"effective_until_time": "2026-12-31 23:59:59",
"shipping_address": {
"name": "Example User",
"line1": "1 Market Street",
"line2": "Suite 100",
"line3": null,
"city": "San Francisco",
"state": "CA",
"zip": "94105",
"country_code": "US"
},
"mandates": [
{
"description": "Purchase office supplies",
"amount_limit": "100.00",
"currency_code": "USD",
"recurring_frequency": null,
"merchant_category_code": "5732",
"preferred_merchant_name": null,
"effective_until_time": null
}
]
}
'{
"code": 200,
"msg": "Success",
"data": {
"instruction_id": "inst_...",
"status": "CREATED",
"payment_instrument_id": "pi_...",
"activation_url": "https://agent.clinkbill.dev/sign/ss_...",
"activation_expires_at": "2026-11-09T10:30:00Z"
}
}Authorizations
Create instruction
Creates a purchase instruction (spending authorization) for the token’s customer and returns a short-lived activation link that the user opens to approve it with a Passkey. Requires portal:write.
POST
/
agent
/
platform
/
authorizations
curl --request POST \
--url https://uat-api.clinkbill.com/agent/platform/authorizations \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"request_id": "platform-ref-001",
"title": "Office supplies budget",
"description": "Monthly office supplies purchase",
"payment_instrument_id": "pi_...",
"is_recurring": false,
"effective_until_time": "2026-12-31 23:59:59",
"shipping_address": {
"name": "Example User",
"line1": "1 Market Street",
"line2": "Suite 100",
"line3": null,
"city": "San Francisco",
"state": "CA",
"zip": "94105",
"country_code": "US"
},
"mandates": [
{
"description": "Purchase office supplies",
"amount_limit": "100.00",
"currency_code": "USD",
"recurring_frequency": null,
"merchant_category_code": "5732",
"preferred_merchant_name": null,
"effective_until_time": null
}
]
}
'{
"code": 200,
"msg": "Success",
"data": {
"instruction_id": "inst_...",
"status": "CREATED",
"payment_instrument_id": "pi_...",
"activation_url": "https://agent.clinkbill.dev/sign/ss_...",
"activation_expires_at": "2026-11-09T10:30:00Z"
}
}payment_instrument_id selects one of two signing modes:
- Sign with an existing card: send
payment_instrument_id. The instruction isCREATED, and the activation link opens the authorization page for that card. - Bind a card and sign: omit
payment_instrument_id. The instruction isPENDING, and the activation link opens the card-binding and authorization flow, where the user binds a card and authorizes in one Passkey ceremony.
payment_instrument_id from List payment methods. In the second mode, do not send a card number, CVV, or any other card field; the user enters card details on the Clink page. Customer identity always comes from the token; the request body has no customer or email field.
After the activation link’s signing session is exchanged, an existing-card instruction continues to /authorize/{paymentInstrumentId}?instructionId=...; a bind-and-sign instruction continues to /bind-authorize?instructionId=..., where the user binds a card and authorizes in one Passkey ceremony.
Treat the activation link as a credential. Do not forward it, screenshot it, or write it to logs; anyone who has the link can open it while it is valid and obtain a Clink browser login session for that customer. Deliver it only to the intended user.
Activate the instruction
Creating an instruction is not an authorization. An instruction with an existing card isCREATED; an instruction that will bind a card is PENDING. Both become ACTIVE only after the user completes Passkey verification on Clink’s page. The link can be reopened or refreshed while it is valid, but the instruction can be signed only once.
- Send the user to
activation_urlin a browser. - For
CREATED, the user reviews the card and completes Passkey verification. ForPENDING, the user binds a card and completes Passkey verification in the same ceremony. The page establishes the browser session and continues to the authorization step. - Poll
GET /agent/platform/authorizations/{instructionId}untilstatusisACTIVE.
CREATED or PENDING and authorizes no spending. Only send the link to the intended user; it is an activation link, not a portal token.
Idempotency
request_id is the idempotency key, and the rules are identical in both signing modes. Clink keeps the idempotency record for 24 hours by default; after that window, retrying the same request_id creates a new instruction. Within the window, retrying with identical parameters returns the same instruction_id; a normal retry on an instruction that is not yet signed returns a fresh activation link. If the retried request_id refers to an instruction that is already signed or final, Clink returns the instruction without a new activation_url or activation_expires_at (both fields are omitted); read GET /agent/platform/authorizations/{instructionId} for the current status. Reusing a request_id with different parameters returns 409 with code 71211011 (portal_conflict).Authorizations
Body
application/json
Last time the instruction can be used, in UTC yyyy-MM-dd HH:mm:ss. Ignored in bind-and-sign mode: Clink overrides it (and each mandate's effective_until_time) with now + pendingActivationWindowMinutes (7 days by default), so read the effective value from the instruction.
Example:
"2026-12-31 23:59:59"