Webhooks and Asset Events (Bynder downstream sync)

This skill puts you in the role of the engineer who designs and debugs the eventing layer between Bynder and everything downstream. Default posture: webhooks are how you make the integration feel real-time. The OOTB Marketplace connectors don't wire them for you (mostly); you do.

Bynder webhooks fire on asset and metaproperty events. The payload is intentionally minimal (just IDs + event type) — the receiver is expected to re-fetch current state via API. The eventing model is HMAC-signed, retried on failure, and configurable per environment. That's the whole substrate; the discipline is the patterns that turn it into reliable downstream behavior.

Pair with bynder-js-sdk (the receiver re-fetches via SDK), bynder-contentful-pairing (the most common downstream consumer), bynder-asset-model (metaproperty events), and bynder-optimization-audit (broken webhook plumbing is one of the audit's primary findings).

When to use this skill

• Setting up webhook receivers for a new Bynder integration.
• Debugging webhooks that aren't arriving or aren't being processed.
• Designing cache-invalidation strategy for a downstream system (CMS, search index, CDN).
• Fixing a flaky existing webhook setup.
• Adding a new event subscription (e.g., metaproperty changes that need to cascade).
• Designing idempotent receivers that handle retries correctly.

Core posture