Webhooks
Studio admins add webhooks in Admin → Integrations. Choose Your service (JSON) or Discord channel, paste the address, and tick the events you want.
Events
Section titled “Events”task.created, task.updated, task.status_changed, task.commented, submission.created, submission.reviewed, sprint.started, sprint.completed, doc.created, asset.published, invoice.submitted, invoice.paid.
Invoice events never include payout details.
Payload
Section titled “Payload”{ "id": "6f1c…", "event": "task.status_changed", "studio": "kotzuki", "occurredAt": "2026-11-16T10:12:03.000Z", "data": { "key": "OBBY-12", "title": "Lava stage", "status": "In Review", "url": "/t/OBBY-12" }}Each request also has Baseplate-Event and Baseplate-Delivery headers.
Checking the signature
Section titled “Checking the signature”Every request has a Baseplate-Signature: t=<unix seconds>,v1=<hex> header. v1 is the HMAC-SHA256 of t.body with your webhook’s signing secret, which is shown once when you add the webhook.
async function verify(Secret: string, Header: string, Body: string) { const [, Time, Mac] = /t=(\d+),v1=([0-9a-f]+)/.exec(Header) ?? []; if (!Time || Math.abs(Date.now() / 1000 - Number(Time)) > 300) return false; const Key = await crypto.subtle.importKey('raw', new TextEncoder().encode(Secret), { name: 'HMAC', hash: 'SHA-256' }, false, ['sign']); const Expected = Buffer.from(await crypto.subtle.sign('HMAC', Key, new TextEncoder().encode(`${Time}.${Body}`))).toString('hex'); return Expected === Mac;}Delivery
Section titled “Delivery”Answer with any 2xx within 10 seconds. Anything else is retried up to five times with growing gaps. The last ten deliveries of each webhook, with the answer your server gave, are listed in Admin → Integrations. Test sends a ping event.
Webhooks must use a public https:// address.