Confirms creation of a secret chat
API section: Working with secret chats
messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;
| Name | Type | Description |
|---|---|---|
| peer | InputEncryptedChat | The user or chat the request is about. |
| g_b | bytes | Public Diffie — Hellman value from the callee. |
| key_fingerprint | long | Fingerprint of the shared key: both sides compare it to confirm they derived the same one. |
Read out of the handler itself — this is what the server actually returns for this method.
| Code | Type | What it means |
|---|---|---|
| 400 | ENCRYPTION_ALREADY_ACCEPTED |
This secret chat has already been accepted. |
| 400 | ENCRYPTION_ID_INVALID |
No secret chat with this identifier exists. |
| 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. |