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.6 KiB
1.6 KiB
| title | description |
|---|---|
| messages.startBot | messages.startBot parameters, return type and example |
Method: messages.startBot
Parameters:
| Name | Type | Required |
|---|---|---|
| bot | InputUser | Optional |
| chat_id | InputPeer | Optional |
| start_param | string | Yes |
Return type: Updates
Can bots use this method: NO
Errors this method can return:
| Error | Description |
|---|---|
| BOT_INVALID | This is not a valid bot |
| PEER_ID_INVALID | The provided peer id is invalid |
| START_PARAM_EMPTY | The start parameter is empty |
| START_PARAM_INVALID | Start parameter invalid |
Example:
$MadelineProto = new \danog\MadelineProto\API();
$MadelineProto->session = 'mySession.madeline';
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);
}
$Updates = $MadelineProto->messages->startBot(['bot' => InputUser, 'chat_id' => InputPeer, 'start_param' => 'string', ]);
Or, if you're using the PWRTelegram HTTP API:
As a user:
POST/GET to https://api.pwrtelegram.xyz/userTOKEN/messages.startBot
Parameters:
bot - Json encoded InputUser
chat_id - Json encoded InputPeer
start_param - Json encoded string
Or, if you're into Lua:
Updates = messages.startBot({bot=InputUser, chat_id=InputPeer, start_param='string', })