AsyncAPI Specification
generated: '2026-10-31'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.pictify.io/concepts/webhooks.md
sources:
- https://docs.pictify.io/concepts/webhooks.md
- https://docs.pictify.io/security/webhook-verification.md
- https://docs.pictify.io/api-reference/webhooks.md
- https://docs.pictify.io/api-reference/endpoints/webhooks/list.md
description: Pictify webhooks deliver real‑time HTTP notifications for render and binding events.
events:
- event: render.completed
description: Image, GIF, or PDF render finished successfully
- event: render.failed
description: Render failed with an error
- event: binding.updated
description: Binding data refreshed
- event: binding.failed
description: Binding data fetch failed
delivery:
signature: X-Pictify-Signature
content_type: application/json
note: All webhook requests also include X-Pictify-Event and X-Pictify-Delivery-Id headers as shown in the payload examples. The signature is an
HMAC‑SHA256 of "{timestamp}.{payload}" using the secret returned when the subscription is created. Timestamp is provided in the same header
as `t=` and must be within 5 minutes of receipt.
docs: https://docs.pictify.io/concepts/webhooks.md
Work with this as data
Every AsyncAPI spec here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for asyncapi
4 MCP tools reach this
find_asyncapisBrowse and filter every AsyncAPI spec in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/pictify-io-webhooks"
All asyncapi
curl "https://apis.io/api/v1/asyncapis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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.
A second provider on the same verified email joins the account you already have.