Optional allowedOptional dropOptional webhookConfiguration options for when the bot is run via webhooks
Optional cb?: RequestListener<typeof IncomingMessage, typeof ServerResponse>Optional certificate?: InputFileUpload your public key certificate so that the root certificate in use can be checked. See self-signed guide for details.
Domain for webhook.
Optional hookWebhook url path; will be automatically generated if not specified
Pass path instead
Optional host?: stringOptional ipThe fixed IP address which will be used to send webhook requests instead of the IP address resolved through DNS
Optional local?: booleanLocal bot api is used
Optional maxMaximum allowed number of simultaneous HTTPS connections to the webhook for update delivery, 1-100. Defaults to 40. Use lower values to limit the load on your bot's server, and higher values to increase your bot's throughput.
Optional path?: stringWebhook url path; will be automatically generated if not specified
Optional port?: numberOptional secretA secret token to be sent in a header “X-Telegram-Bot-Api-Secret-Token” in every webhook request.
1-256 characters. Only characters A-Z, a-z, 0-9, _ and - are allowed.
The header is useful to ensure that the request comes from a webhook set by you.
Optional tlsTLS server options. Omit to use http.
List the types of updates you want your bot to receive