Construa no seu próprio projeto.

Use os mesmos exemplos de SDK das páginas de produto do Bird e depois forneça ao seu agente de código um briefing que inclua os caminhos de falha que você praticou.

Prática interativa · Inglês

Make the unhappy path work.

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

Este exercício no navegador simula mensagens. O seu trabalho permanece aqui até sair. Inicie sessão para guardar o progresso e as avaliações.

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

Resultado da prática

Your practice output will appear here.
Mostrar uma dica

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

Continuar com a aprendizagem guardada

Um briefing para o seu agente de código

# 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.

Sua próxima ideia. Pronta para conectar.