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
Build trust into the first interaction.
Verification is a small interaction with an important job: establish that someone controls the destination.
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.
Resultado da prática
Your practice output will appear here.
Mostrar uma dica
Send a code, try 000000 to see a failed attempt, then enter the code shown on the phone.
Um briefing para o seu agente de código
# Build with Bird: Customer verification Read these current sources before proposing an implementation: - Verify your first customer: https://bird.com/docs/get-started/verify-your-first-customer - What does OTP mean? One-time passwords explained: https://bird.com/explained/verify/what-does-otp-mean - Customer verification: https://bird.com/verify-api ## Task Help me implement Customer verification 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.