Create local runner pairing token

POST/v1/local-runner-pairing-tokens

Mint a short-lived token that a local daemon can exchange for a scoped runner API key.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
None.
Query parameters
None.

Body schema

Content type: application/json · Optional

FieldTypeRequiredDescription
namestringNoHuman-readable name.
ttlSecondsintegerNo

What the API returns

Each response code below includes the documented payload shape for the ACP API.

201Pairing token createdapplication/json
FieldTypeRequiredDescription
pairingTokenobjectNo
pairingToken.idstringNoUnique identifier.
pairingToken.userIdstringNoUser ID.
pairingToken.tokenPrefixstringNo
pairingToken.namestringNoHuman-readable name.
pairingToken.statuspending | completed | expired | revokedNoCurrent lifecycle status.
pairingToken.deviceIdstringNo
pairingToken.expiresAtstringNo
pairingToken.completedAtstringNoISO 8601 timestamp.
pairingToken.createdAtstringNoISO 8601 timestamp.
pairingToken.updatedAtstringNoISO 8601 timestamp.
tokenstringNoOne-time raw pairing token. Returned only at creation time.
Create local runner pairing token
Loading...
Response 201
Loading...
See the ACP quickstart and SDK flow