telegram api method · layer 229 · #3dbc0415

messages.acceptEncryption

usable by users

Confirms creation of a secret chat

definition

messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;

name	type	description
`peer`	InputEncryptedChat	Secret chat ID
`g_b`	bytes	B = g ^ b mod p, see Wikipedia
`key_fingerprint`	long	64-bit fingerprint of the received key

code	error	description
400	BUSINESS_CONNECTION_NOT_ALLOWED	This method was invoked over a business connection using invokeWithBusinessConnection, but either (1) we're a user, and users cannot invoke methods over a business connection; (2) we're a bot, but business mode was disabled in @botfather or (3); we're a bot, but this method cannot be invoked over a business connection.
400	CHAT_ID_INVALID	The provided chat id is invalid.
400	ENCRYPTION_ALREADY_ACCEPTED	Secret chat already accepted.
400	ENCRYPTION_ALREADY_DECLINED	The secret chat was already declined.
401	AUTH_KEY_UNREGISTERED	The specified authorization key is not registered in the system (for example, a PFS temporary key has expired).

present in layers 8–229

id	layers
#3dbc0415	8–229