Costruiscilo nel tuo progetto.
Usa gli stessi esempi SDK delle pagine prodotto di Bird, poi fornisci al tuo coding agent un brief che includa i percorsi di errore che hai praticato.
Esercitazione interattiva · Inglese
Build trust into the first interaction.
Verification is a small interaction with an important job: establish that someone controls the destination.
Questo esercizio nel browser simula dei messaggi. Il tuo lavoro resta qui finché non esci. Accedi per salvare i progressi e le valutazioni.
Output esercitazione
Your practice output will appear here.
Mostra un suggerimento
Send a code, try 000000 to see a failed attempt, then enter the code shown on the phone.
Un brief per il tuo coding agent
# 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.