telegram api method · layer 229 · #67a3f0de
messages.acceptUrlAuth
Use this to accept a Seamless Telegram Login authorization request, for more info click here »
definition
messages.acceptUrlAuth#67a3f0de flags:# write_allowed:flags.0?true share_phone_number:flags.3?true peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string match_code:flags.4?string = UrlAuthResult;
parameters
| name | type | description |
|---|---|---|
flags | # | Flags, see TL conditional fields |
write_allowed | true | Set this flag to allow the bot to send messages to you (if requested) |
share_phone_number | true | |
peer | InputPeer | The location of the message |
msg_id | int | Message ID of the message with the login button |
button_id | int | ID of the login button |
url | string | URL used for link URL authorization, click here for more info » |
match_code | string |
returns
errors (2)
| 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. |
| 401 | AUTH_KEY_UNREGISTERED | The specified authorization key is not registered in the system (for example, a PFS temporary key has expired). |
history
present in layers 100–229 · constructor id changed 2×
| id | layers |
|---|---|
| #f729ea98 | 100–124 |
| #b12c7125 | 125–222 |
| #67a3f0de | 223–229 |