Docs / Webhooks
Webhook documentation boundaries
Brandloop uses webhook and callback patterns for provider-side events, but public webhook consumption should be described carefully. Private provider callbacks are not public integration endpoints.
Private callbacks
Provider callbacks and billing or channel webhooks are private operational surfaces. They should be excluded from sitemap entries and should not be treated as public docs pages.
Future external events
If Brandloop exposes customer-facing webhooks later, the contract should define event names, payload schema, signature verification, replay handling, and delivery status before launch.
Current integration guidance
Developers should use the public API reference and OpenAPI contract for current integrations. Do not infer a public webhook subscription API from private callback routes.
Limitations and boundaries
- Private provider webhooks are not public customer integration points.
- A customer-facing webhook product needs signed payloads and delivery semantics before public availability claims.
- This page is documentation of boundaries, not a promise that every event stream is externally subscribable today.
Common questions
- Can customers subscribe to Brandloop webhooks today?
- Do not assume that from public docs alone. Current public developer integration should start with `/developers/api` and `/openapi.json`.
- Are provider webhooks safe to crawl?
- No. Private callback paths should remain out of sitemap entries and public discovery surfaces.