Constrúyelo en tu propio proyecto.
Usa los mismos ejemplos del SDK que las páginas de producto de Bird y luego dale a tu agente de código un brief que incluya las rutas de error que practicaste.
Práctica interactiva · Inglés
Follow the message beyond send.
Accepted is the beginning of the story. Explore delivery, bounces, and complaints without reaching a real customer.
Este ejercicio del navegador simula mensajes. Tu trabajo permanece aquí hasta que salgas. Inicia sesión para guardar tu progreso y evaluaciones.
Resultado de la práctica
Your practice output will appear here.
Mostrar una pista
Try Delivered, Hard bounce, and Complaint. Notice that they share the first two events.
Un brief para tu agente de código
# Build with Bird: Email deliverability Read these current sources before proposing an implementation: - Deliverability · Email: https://bird.com/docs/guides/email/deliverability - What are bounced emails?: https://bird.com/explained/deliverability/what-are-bounced-emails - Email deliverability: https://bird.com/email-api/features/deliverability ## Task Help me implement Email deliverability 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.