Support webhooks

Hear about new cases, messages, status changes, escalations and ratings as they happen.

Add up to 5 HTTPS endpoints in Developer Portal › Settings › Support or with POST /api/v1/support/webhooks. Each endpoint subscribes to one or more topics. Notes and AI drafts are never sent.

Topic

When

support.case.created

A merchant, an app or an AI assistant opened a case about one of your apps or themes.

support.case.message_added

A merchant, your team, Tringify or an auto-reply added a message.

support.case.status_changed

The stored status changed (status.from, status.to).

support.case.escalated

The merchant asked Tringify to step in.

support.case.rated

The merchant rated a solved case.

Request#

Each delivery is a POST with Content-Type: application/json and these headers:

Header

Value

X-Tringify-Event

The topic.

X-Tringify-Event-ID

The event id: the same across retries and across your endpoints. Use it to drop duplicates.

X-Tringify-Delivery-ID

This delivery to this endpoint.

X-Tringify-Timestamp

Unix seconds when it was signed.

X-Tringify-Signature

t=<unix>,v1=<hex>: HMAC-SHA256 of <unix>.<raw body> with the endpoint’s secret.

support.case.message_added json
{
  "id": "8f1d…",
  "topic": "support.case.message_added",
  "created_at": "2026-11-20T09:41:00Z",
  "organization_id": "…",
  "case": {
    "id": "…", "display_number": "C-20418", "subject": "Orders from yesterday not syncing",
    "status": "open", "display_status": "needs_reply",
    "about": { "kind": "app", "id": "…", "name": "Shiprocket" },
    "store": { "id": "…", "name": "Printblow" },
    "dev_assignee_account_id": null, "escalated_at": null,
    "created_at": "…", "updated_at": "…"
  },
  "message": {
    "id": "…", "author": "customer", "author_name": "Riya",
    "body_text": "Two orders still show no tracking.",
    "attachments": [{ "id": "…", "filename": "orders.png", "content_type": "image/png", "size": 245760 }],
    "created_at": "…"
  }
}

message is present only on message_added, status only on status_changed, and rating ({ "rating": "good" | "bad", "comment" }) only on rated. Fetch attachments through the Support API.

Verify the signature#

Compute the HMAC over the timestamp, a dot and the raw request body, compare it in constant time with every v1 value, and reject timestamps more than 5 minutes old. During a secret rotation the header carries two v1 values (new first) for 72 hours.

verify.js javascript
import crypto from "node:crypto";

export function verify(rawBody, header, secret) {
  let t = "";
  const sigs = [];
  for (const item of header.split(",")) {
    const [k, v] = item.split("=");
    if (k === "t") t = v;
    if (k === "v1") sigs.push(v);
  }
  if (!t || Math.abs(Date.now() / 1000 - Number(t)) > 300) return false;
  const expected = crypto.createHmac("sha256", secret).update(`${t}.${rawBody}`).digest("hex");
  return sigs.some((s) => s.length === expected.length &&
    crypto.timingSafeEqual(Buffer.from(s), Buffer.from(expected)));
}

Retries and disabling#

Answer with any 2xx within 10 seconds. Anything else is retried after 30 seconds, doubling up to 1 hour between attempts, for 24 hours after the first attempt; then the delivery is parked and can be re-sent from its endpoint’s deliveries list. Each endpoint gets at most 4 deliveries at a time. An endpoint that has had only failures for 3 days is disabled and your organization’s owner is emailed; re-enable it after fixing it.

Endpoint URLs must use HTTPS on a public host name (no IP addresses, no *.tringify.com) and be at most 2,048 characters. The signing secret is shown once, when you create the endpoint or rotate its secret. Deliveries are kept for 30 days.