Daniil Gentili
e4a326e552
* refactor * Apply fixes from StyleCI * Implement https and http transport, add support for new req_pq_multi, send pending acks and objects in containers along with the next method call, remove dependency on the socket extension. * Apply fixes from StyleCI * Make types with empty constructors optional, fix phar archives (fixes #217) * Apply fixes from StyleCI * Update to layer 75 * Update github pages gemfile.lock
1.3 KiB
1.3 KiB
| title | description |
|---|---|
| rpc_drop_answer | rpc_drop_answer parameters, return type and example |
Method: rpc_drop_answer
Parameters:
| Name | Type | Required |
|---|---|---|
| req_msg_id | long | Yes |
Return type: RpcDropAnswer
Can bots use this method: YES
Example:
$MadelineProto = new \danog\MadelineProto\API();
$MadelineProto->session = 'mySession.madeline';
if (isset($token)) { // Login as a bot
$MadelineProto->bot_login($token);
}
if (isset($number)) { // Login as a user
$MadelineProto->phone_login($number);
$code = readline('Enter the code you received: '); // Or do this in two separate steps in an HTTP API
$MadelineProto->complete_phone_login($code);
}
$RpcDropAnswer = $MadelineProto->rpc_drop_answer(['req_msg_id' => long, ]);
Or, if you're using the PWRTelegram HTTP API:
As a bot:
POST/GET to https://api.pwrtelegram.xyz/botTOKEN/madeline
Parameters:
- method - rpc_drop_answer
- params -
{"req_msg_id": long, }
As a user:
POST/GET to https://api.pwrtelegram.xyz/userTOKEN/rpc_drop_answer
Parameters:
req_msg_id - Json encoded long
Or, if you're into Lua:
RpcDropAnswer = rpc_drop_answer({req_msg_id=long, })