A valid request URL is required to generate request examples{
"status": "pending"
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}{
"error": {
"code": "not_found",
"message": "<string>"
}
}{
"error": {
"code": "payload_too_large",
"message": "<string>"
}
}{
"error": {
"code": "slow_down",
"message": "<string>",
"intervalMs": 1001
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}Poll a CLI sign-in, and collect its key
Poll every intervalMs with the poll token from POST /v1/cli-sessions. While nobody has answered, the status is pending. Once a person approves, the NEXT poll mints the key and returns it with status: approved, and every poll after that answers consumed. The key is delivered exactly once: if that response is lost, the key still exists (revoke it on the Keys page) and you have to sign in again.
denied and expired are final too. Stop polling on any status but pending.
Hosted deployments only. A local checkout does not mount this route, so calling it there is a 404.
A valid request URL is required to generate request examples{
"status": "pending"
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}{
"error": {
"code": "not_found",
"message": "<string>"
}
}{
"error": {
"code": "payload_too_large",
"message": "<string>"
}
}{
"error": {
"code": "slow_down",
"message": "<string>",
"intervalMs": 1001
}
}{
"error": {
"code": "backend_resolution_failed",
"message": "<string>",
"retryable": true
}
}Body
The poll token.
The pbcs_ token.
Response
Where the sign-in is, with the key on the one poll that collects it.
- Option 1
- Option 2
A poll that delivers no key.
pending: keep polling. denied, expired, consumed: stop; run the sign-in again if you still need a key.
pending, denied, expired, consumed