curl --request GET \
--url https://api.aireserve.com/v1/sessions/confirmationimport requests
url = "https://api.aireserve.com/v1/sessions/confirmation"
response = requests.get(url)
print(response.text)const options = {method: 'GET'};
fetch('https://api.aireserve.com/v1/sessions/confirmation', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"error": "<string>",
"message": "<string>"
}{
"error": "<string>",
"message": "<string>"
}Cross-device authorization relay
The cross-device redirect_uri target. When the portal redirects the authorization code here (after the user approves on another machine), this endpoint 302-redirects to the portal confirmation page. That page displays standard Base64 of state=<url-encoded>&code=<url-encoded> — which the user copies and pastes back into the waiting aws login --remote prompt. There is no polling: the CLI waits for user input, not for a status response from this endpoint. No API key is required.
curl --request GET \
--url https://api.aireserve.com/v1/sessions/confirmationimport requests
url = "https://api.aireserve.com/v1/sessions/confirmation"
response = requests.get(url)
print(response.text)const options = {method: 'GET'};
fetch('https://api.aireserve.com/v1/sessions/confirmation', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"error": "<string>",
"message": "<string>"
}{
"error": "<string>",
"message": "<string>"
}Query Parameters
Authorization code from the portal, forwarded from the /v1/authorize redirect.
CSRF state token from the /v1/authorize redirect, forwarded unchanged.
Response
Redirect to the portal confirmation page. The page shows the Base64-encoded code and state string the user pastes into the CLI.