The endpoint that receives all Figma webhook event deliveries. The specific event type is identified by the event_type field in the payload. Figma webhooks are team-scoped and can subscribe to specific event types.
Test event sent when a webhook is first created to verify the endpoint is reachable.
Content-Type:
file_update
Triggered when a file in the team is saved or modified.
Content-Type:
file_version_update
Triggered when a named version is created in the file's version history.
Content-Type:
file_delete
Triggered when a file in the team is deleted.
Content-Type:
file_comment
Triggered when a new comment is posted on a file.
Content-Type:
library_publish
Triggered when a library file publishes new components or styles.
Content-Type:
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.