Skip to main content
Instead of polling the API, register a webhook endpoint and SocialAPI will POST a signed payload to your server whenever a new comment, DM, review, or mention arrives, or when a scheduled post is published (or fails).

Register an endpoint

Endpoints can be registered in the dashboard under WebhooksAdd Endpoint, or via the API:
curl -X POST https://api.social-api.ai/v1/webhooks \
  -H "Authorization: Bearer $SOCAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://app.example.com/webhooks/socapi",
    "events": ["comment.received", "dm.received", "post.published", "post.failed"]
  }'
Response (HTTP 201):
{
  "id": "wh_01HZ9X3Q4R5M6N7P8V2K0W1J",
  "url": "https://app.example.com/webhooks/socapi",
  "events": ["comment.received", "dm.received", "post.published", "post.failed"],
  "secret": "a3f8c2e1b9d4f7a6c5e0b3d2f1a8e7c4b9d6f3a2e5c8b1d4f7a0e3c6b9d2f5a8",
  "message": "Store the secret securely. It will not be shown again."
}
The secret is returned once. Store it immediately in your environment. It cannot be retrieved again. You use it to verify incoming signatures.
Endpoint URLs must use HTTPS. HTTP URLs are rejected with 400.

Event types

EventWhen it fires
comment.receivedA new comment arrives on any connected account
dm.receivedA new direct message arrives
review.receivedA new review arrives (Google Business Profile)
mention.receivedYour account is mentioned on a supported platform
post.publishedA scheduled post is successfully published to a platform
post.failedA scheduled post fails to publish
post.scheduledA new post is scheduled for future publishing
You can subscribe to any combination. Pass all seven event types to receive everything:
[
  "comment.received",
  "dm.received",
  "review.received",
  "mention.received",
  "post.published",
  "post.failed",
  "post.scheduled"
]

Payload format

Every webhook POST has a JSON body with an event field and a data field containing the full interaction object:
{
  "event": "comment.received",
  "data": {
    "id": "sapi_cmt_aW5zdGFncmFtOjE3ODQxNDA1",
    "type": "comment",
    "platform": "instagram",
    "platform_id": "17841405793187218",
    "account_id": "acc_01HZ9X3Q4R5M6N7P8V2K0W1J",
    "author": {
      "id": "10215054824",
      "name": "Jane Smith",
      "avatar_url": "https://example.com/avatar.jpg"
    },
    "content": {
      "text": "Love this product!",
      "media": []
    },
    "created_at": "2026-03-01T14:30:00Z",
    "metadata": {}
  }
}
The data object is the same Interaction shape returned by GET /accounts/{id}/comments (and the equivalent DM, review, and mention endpoints). The id field is a stable SocialAPI interaction ID - see Interaction IDs.

Request headers

Every webhook request includes:
HeaderValue
Content-Typeapplication/json
X-SocialAPI-Signaturesha256=<hmac-sha256-hex>
X-SocialAPI-EventThe event type, e.g. comment.received

Verifying signatures

Always verify the X-SocialAPI-Signature header before processing a webhook. This confirms the payload came from SocialAPI and was not tampered with. The signature is HMAC-SHA256 of the raw request body, using your endpoint secret as the key, prefixed with sha256=.
import crypto from "crypto";

function verifySignature(secret, rawBody, signatureHeader) {
  const expected = "sha256=" + crypto
    .createHmac("sha256", secret)
    .update(rawBody)
    .digest("hex");
  return crypto.timingSafeEqual(
    Buffer.from(expected),
    Buffer.from(signatureHeader)
  );
}

// Express example
app.post("/webhooks/socapi", express.raw({ type: "application/json" }), (req, res) => {
  const sig = req.headers["x-socapi-signature"];
  if (!verifySignature(process.env.SOCAPI_WEBHOOK_SECRET, req.body, sig)) {
    return res.status(401).send("Invalid signature");
  }
  const event = JSON.parse(req.body);
  // handle event.event and event.data
  res.sendStatus(200);
});
Use a constant-time comparison (timingSafeEqual / compare_digest / hmac.Equal) to prevent timing attacks. A simple string equality check is not safe.

Responding to webhooks

Your endpoint must return an HTTP 2xx status within 10 seconds. The webhook HTTP client enforces a 10-second timeout per delivery attempt. Any non-2xx response or a timeout is treated as a delivery failure. Return 200 immediately and process the event asynchronously if your handler does heavier work.

Retry behavior

Failed deliveries are automatically retried up to 5 attempts with exponential backoff:
AttemptDelay
1Immediate
2~30 seconds
3~5 minutes
4~30 minutes
5~3 hours
After 5 failed attempts, the delivery is marked failed and no further retries occur.

Managing endpoints

Endpoints can also be listed and deleted in the dashboard under Webhooks. List your endpoints:
curl https://api.social-api.ai/v1/webhooks \
  -H "Authorization: Bearer $SOCAPI_KEY"
{
  "data": [
    {
      "id": "wh_01HZ9X3Q4R5M6N7P8V2K0W1J",
      "url": "https://app.example.com/webhooks/socapi",
      "events": ["comment.received", "dm.received"],
      "is_active": true,
      "created_at": "2026-03-01T10:00:00Z"
    }
  ],
  "count": 1
}
Delete an endpoint:
curl -X DELETE https://api.social-api.ai/v1/webhooks/wh_01HZ9X3Q4R5M6N7P8V2K0W1J \
  -H "Authorization: Bearer $SOCAPI_KEY"
Deleting an endpoint stops all future deliveries immediately. In-flight jobs already queued may still attempt delivery once.

Security best practices

  • Always verify signatures - never trust a webhook payload without checking X-SocialAPI-Signature
  • Store your secret in an environment variable - never hardcode it or commit it to source control
  • Use HTTPS - HTTP endpoints are rejected at registration time
  • Respond quickly - return 200 before doing heavy processing to avoid timeouts and spurious retries
  • Make handlers idempotent - retries mean the same event may arrive more than once; use the interaction id to deduplicate