Get local runner pairing token
GET
/v1/local-runner-pairing-tokens/{pairingTokenId}Poll the status of a short-lived local runner pairing token.
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
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| pairingTokenId | path | string | Yes | Local runner pairing token ID |
Query parameters
None.
Body schema
This endpoint does not require a request body.
None.
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Pairing token statusapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| pairingToken | object | No | — |
| pairingToken.id | string | No | Unique identifier. |
| pairingToken.userId | string | No | User ID. |
| pairingToken.tokenPrefix | string | No | — |
| pairingToken.name | string | No | Human-readable name. |
| pairingToken.status | pending | completed | expired | revoked | No | Current lifecycle status. |
| pairingToken.deviceId | string | No | — |
| pairingToken.expiresAt | string | No | — |
| pairingToken.completedAt | string | No | ISO 8601 timestamp. |
| pairingToken.createdAt | string | No | ISO 8601 timestamp. |
| pairingToken.updatedAt | string | No | ISO 8601 timestamp. |
404Resource not foundapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| error | string | No | — |