telegram api method · layer 233 · #18dd4e92

messages.acceptUrlAuth

usable by users

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

definition

messages.acceptUrlAuth#18dd4e92 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 tonconnect_session:flags.5?InputTonConnectOauthSession = UrlAuthResult;

parameters

nametypedescription
flags#Flags, see TL conditional fields
write_allowedflags.0?trueSet this flag to allow the bot to send messages to you (if requested)
share_phone_numberflags.3?true
peerflags.1?InputPeerThe location of the message
msg_idflags.1?intMessage ID of the message with the login button
button_idflags.1?intID of the login button
urlflags.2?stringURL used for link URL authorization, click here for more info »
match_codeflags.4?string
tonconnect_sessionflags.5?InputTonConnectOauthSession

returns

UrlAuthResult

errors (2)

codeerrordescription
400BUSINESS_CONNECTION_NOT_ALLOWEDThis 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.
401AUTH_KEY_UNREGISTEREDThe specified authorization key is not registered in the system (for example, a PFS temporary key has expired).

history

present in layers 100–233 · constructor id changed 3×

idlayers
#f729ea98100–124
#b12c7125125–222
#67a3f0de223–230
#18dd4e92231–233