TelegramPHP Documentation

Http

Table of Contents

Namespaces

Drivers
Exceptions

Interfaces

DriverInterface
Executes a single prepared {@see Request} and resolves with the raw {@see ResponseInterface} - success or error status alike. Retries, the `retry_after` hold-off, envelope unwrapping, and exception mapping are {@see Http}'s job, not the driver's.
HttpInterface
The contract {@see Http} fulfils. Depend on this rather than the concrete class so the transport can be decorated or faked (test doubles, alternative drivers, a local Bot API server).

Classes

Endpoint
This file is generated from spec/openapi.json (Bot API 10.3) by tools/generate.php.
Http
Non-blocking transport for the Telegram Bot API.
Multipart
Encodes a Bot API payload as `multipart/form-data`, which is the only way to upload a file.
Request
One prepared Bot API call: the method name, the absolute URL, the encoded body, the headers, and the {@see Deferred} that {@see Http} settles with the unwrapped `result`.
On this page

Search results