Source type
Telegram Source Configuration
Telegram sources receive Bot API webhook updates and verify Telegram's optional secret token header without reading the raw body.
Telegram configuration
Create a Telegram source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Secret Token values for provider signature. FastHook uses these settings to validate each Telegram delivery before it enters the routing workflow.
Source TypeTELEGRAM
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsSecret Token
{
"type": "TELEGRAM",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "TELEGRAM",
"webhook_signing_secret": "secret-token"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}Telegram request contract
FastHook compares x-telegram-bot-api-secret-token with the configured secret token before queueing.
Telegram headers
Preserve x-telegram-bot-api-secret-token when sending Telegram test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.
x-telegram-bot-api-secret-tokenStatic secret token configured in setWebhook.
Telegram setup
- Call setWebhook with the FastHook Source URL.
- Set secret_token in Telegram and the same Secret Token in FastHook.
- Use one source per bot or environment so token rotation stays isolated.
Telegram routing hints
- Bot API updates usually route by message, callback_query, channel_post, or edited_message fields.
- Use one source per bot or environment so secret token rotation stays isolated.