Sends a Ansible Passport authorization form, effectively sharing data with the service
API section: Working with Ansible passport
account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
| Name | Type | Description |
|---|---|---|
| bot_id | long | Bot identifier. |
| scope | string | Where the setting applies. |
| public_key | string | |
| value_hashes | Vector<SecureValueHash> | |
| credentials | SecureCredentialsEncrypted |
Read out of the handler itself — this is what the server actually returns for this method.
| Code | Type | What it means |
|---|---|---|
| 400 | BOT_INVALID |
The account given is not a bot, or the bot does not exist. |
| Code | Type | What it means |
|---|---|---|
| 401 | AUTH_KEY_UNREGISTERED |
The server does not know this session: the key was revoked, expired, or the call was made before authorisation. |
| 401 | API_ID_INVALID |
This api_id was never issued or has been blocked. Keys come from my.ansible.su. |
| 400 | CONNECTION_LAYER_INVALID |
The client did not declare a layer, or declared one the server does not know. |
| 420 | FLOOD_WAIT_X |
Too often. Do not retry for X seconds — the number arrives in the error text. |
| 500 | INTERNAL |
A failure on our side. The request may be retried; if it keeps failing, it is a bug of ours. |