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.7 KiB
1.7 KiB
| title | description |
|---|---|
| messages.searchGlobal | messages.searchGlobal parameters, return type and example |
Method: messages.searchGlobal
Parameters:
| Name | Type | Required |
|---|---|---|
| q | string | Yes |
| offset_date | int | Yes |
| offset_peer | InputPeer | Optional |
| offset_id | int | Yes |
| limit | int | Yes |
Return type: messages_Messages
Can bots use this method: NO
Errors this method can return:
| Error | Description |
|---|---|
| SEARCH_QUERY_EMPTY | The search query is empty |
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);
}
$messages_Messages = $MadelineProto->messages->searchGlobal(['q' => 'string', 'offset_date' => int, 'offset_peer' => InputPeer, 'offset_id' => int, 'limit' => int, ]);
Or, if you're using the PWRTelegram HTTP API:
As a user:
POST/GET to https://api.pwrtelegram.xyz/userTOKEN/messages.searchGlobal
Parameters:
q - Json encoded string
offset_date - Json encoded int
offset_peer - Json encoded InputPeer
offset_id - Json encoded int
limit - Json encoded int
Or, if you're into Lua:
messages_Messages = messages.searchGlobal({q='string', offset_date=int, offset_peer=InputPeer, offset_id=int, limit=int, })