List the machines authorized through CLI browser login
const url = 'https://api.aetherpush.com/v1/cli/devices';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://api.aetherpush.com/v1/cli/devices \ --header 'Authorization: Bearer <token>'Session-only. Lists credentials whose origin is cli_browser or
cli_device. Dashboard sessions and manually created access keys are
managed under /v1/access-keys instead.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”Authorized devices.
object
object
True for the credential the request itself is authenticated with.
Example
{ "devices": [ { "credentialOrigin": "cli_browser" } ]}The bearer token is missing, invalid, or expired.
object
Human-readable error message.
Unique identifier for the request, also exposed as the X-Request-Id response header.
Example
{ "error": "The requested resource was not found.", "requestId": "req_abc123"}API keys and named access keys cannot access this endpoint; a login session is required.
object
Human-readable error message.
Unique identifier for the request, also exposed as the X-Request-Id response header.
Example
{ "error": "The requested resource was not found.", "requestId": "req_abc123"}Internal server error.
object
Human-readable error message.
Unique identifier for the request, also exposed as the X-Request-Id response header.
Example
{ "error": "The requested resource was not found.", "requestId": "req_abc123"}