Build it in your own project.

Use the same SDK examples as Bird's product pages, then give your coding agent a brief that includes the failure paths you practised.

Interactive practice · English

Make the unhappy path work.

Events can arrive more than once. A trustworthy integration verifies the sender and processes each event appropriately.

This browser exercise simulates messages. Your work stays here until you leave. Sign in for saved progress and assessments.

Reject an invalid signature and prevent a replayed event from updating an order twice.

Practice output

Your practice output will appear here.
Show a hint

Enable signature verification and deduplication. Test an invalid event, then replay a valid one.

Continue with saved learning

A brief for your coding agent

# Build with Bird: Reliable webhooks

Read these current sources before proposing an implementation:

- Webhooks & events: https://bird.com/docs/guides/webhooks
- How do I verify a webhook signature?: https://bird.com/explained/platform/how-do-i-verify-a-webhook-signature

## Task

Help me implement Reliable webhooks in my project. First inspect the application and identify the relevant server, framework and existing Bird integration. Confirm the exact workflow and supported surface against the linked documentation. Some operations are available only in the dashboard. Do not invent endpoints or derive API contracts from a learning simulation.

## Implementation

Use the official Bird SDK or CLI where supported. Keep credentials on the server and request the smallest necessary permissions. Follow the channel's documented test procedure before proposing any external send or production change.

Keep request acceptance separate from delivery. For incoming events, verify signatures using the original request body, deduplicate stable identifiers, and apply valid state transitions. Respect recipient preferences and channel requirements.

## Acceptance

Show the implementation and relevant tests. Exercise the documented failure paths, invalid signatures and duplicate events where applicable. Explain any dashboard steps or missing prerequisites. Ask for approval before sending to real recipients or changing production.

Starten Sie mit einem Kanal.
Fügen Sie die anderen hinzu, wenn Sie bereit sind.

Ein Test-API-Key steht Ihnen sofort zur Verfügung. Der Produktivzugang wird freigeschaltet, sobald Sie eine Zahlungsmethode hinzufügen und einen Absender verifizieren.

Sie nutzen Claude Code, Cursor oder Codex? Kopieren Sie einen Setup-Prompt und Ihr Agent installiert die Bird CLI und Skills für Sie. Wählen Sie Ihren:

Cursor