register and validate companycam webhooks for project, photo and document events
domain: docs.companycam.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a webhook via the Core API's Create Webhook endpoint, specifying a scope such as project.*, photo.*, or document.*.
Point the webhook at a publicly reachable URL that returns HTTP 200 on receipt.
Parse the POST body, which contains event_type, created_at, payload, and webhook_id fields.
Verify authenticity by computing a base64 SHA1 HMAC of the raw request body using your webhook token and comparing it to the X-CompanyCam-Signature header.
Handle retries: non-200 responses are retried with exponential backoff up to 10 attempts, and the webhook is disabled after 25 total errors.
Known gotchas
A webhook accumulating more than 25 total errors is automatically disabled.
Signature validation requires hashing the raw, unparsed request body — not a re-serialized JSON object.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?