← Spec Hub | Category: Messaging & Bots
Developer documentation for integrating Slack API ➔ Tally Webhook Pipeline Specification webhooks into backend applications. Secure your endpoint with HMAC signature checking and payload validation.
Supported Events: message.new callback_query inline_query message.reaction
Security validation specs for Slack API ➔ Tally Webhook Pipeline Specification endpoints:
Authorization: Bearer sec_live_6d158387a916445d
const crypto = require('crypto');
const expected = crypto.createHmac('sha256', secret).update(rawBody).digest('hex');
const isValid = crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signature));
import hmac, hashlib
expected = hmac.new(secret.encode(), raw_body, hashlib.sha256).hexdigest()
is_valid = hmac.compare_digest(expected, incoming_sig)
{
"id": "evt_slack-to-tally.html_51939",
"event": "message.new",
"created_at": 1789764056,
"data": {
"resource_id": "res_887",
"status": "active"
}
}
curl -X POST https://your-domain.com/webhook/slack-to-tally.html \
-H "Content-Type: application/json" \
-H "Authorization: Bearer sec_live_6d158387a916445d" \
-d '{"id": "evt_slack-to-tally.html_51939", "event": "message.new", "created_at": 1789764056, "data": {"resource_id": "res_887", "status": "active"}}'
| Status Code | Status Meaning | Integration Action |
|---|---|---|
200 OK | Success | Event payload validated and queued. |
400 Bad Request | Malformed Payload | Check payload structure and JSON formatting. |
401 Unauthorized | Signature Mismatch | Verify secret key and digest computation. |
500 Error | Server Error | Triggers provider automated retry backoff. |
Always process incoming events asynchronously using a message queue. Never perform long-running DB queries or external API calls synchronously within the HTTP response handler.
Compute the HMAC SHA-256 hash on the raw request body using your shared secret and compare it against the incoming signature header using time-constant comparison.
A 429 status indicates your endpoint is being rate limited. Implement dynamic throttling or increase consumer worker threads in your queue worker.
Store processed event IDs in an atomic storage like Redis with a set expiration. If an incoming ID exists, acknowledge with 200 OK immediately without re-triggering logic.