Chat provider webhooks

How Slack, Microsoft Teams, Discord, Telegram and GitHub deliver messages to Veyra, how each delivery is verified, and the limits that apply.

Veyra Docs TeamUpdated 1 min readVersion 3 · History

When you connect a chat channel, the provider sends each message and event to Veyra at:

HTTP
POST https://intelligence-api.veyra.so/api/chat-webhooks/{publicId}/{provider}

provider is one of slack, microsoft-teams, discord, telegram or github. publicId identifies your endpoint; the console fills in the full address during setup and you paste it into the provider's app settings.

Verification

Veyra verifies every delivery with the provider's own mechanism before reading it:

Provider Verified with
Slack The app's signing secret (X-Slack-Signature and X-Slack-Request-Timestamp).
Microsoft Teams The Bot Framework token on the request.
Discord The application's public key (Ed25519 signature headers).
Telegram The secret token set when the webhook was registered.
GitHub The GitHub App's webhook secret (X-Hub-Signature-256).

A delivery that fails verification is refused and nothing in it is read. Verification secrets are entered by a person during setup, never by an agent.

Limits

Each endpoint accepts up to 600 requests per minute per source address. Responses carry X-RateLimit-Limit and X-RateLimit-Remaining; over the limit, Veyra answers 429 with Retry-After, and providers retry on their own schedule.

Responses

Veyra answers in the form each provider expects (for example Slack's URL verification challenge, or Discord's interaction acknowledgement). A provider that is not supported, or that has its own route (email, voice), gets 400.

Delivery and retries

Providers retry failed deliveries. Veyra recognizes repeats by the provider's event or delivery id, so a retry never creates a second task or reply.

What happens to a message

  1. The sender's identity is matched to a linked Veyra member. Unlinked senders get a link to confirm who they are.
  2. A new thread becomes a task for the endpoint's agent; a reply continues the task.
  3. The agent's answer is posted back to the same thread.

See Chat channels in the API reference for endpoint management.

Chat channelsInboundWebhooks