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

Follow the message beyond send.

Accepted is the beginning of the story. Explore delivery, bounces, and complaints without reaching a real customer.

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

Run all three sandbox outcomes and inspect the event timeline.

Practice output

Your practice output will appear here.
Show a hint

Try Delivered, Hard bounce, and Complaint. Notice that they share the first two events.

Continue with saved learning

A brief for your coding agent

# 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/products/email/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.

एक चैनल से शुरुआत करें।
तैयार होने पर बाकी जोड़ें।

एक test API key तुरंत आपकी है। जब आप payment method जोड़ते हैं और sender verify करते हैं, तब production अनलॉक हो जाता है।

Claude Code, Cursor या Codex इस्तेमाल कर रहे हैं? एक setup prompt कॉपी करें और आपका agent आपके लिए Bird CLI और skills इंस्टॉल कर देगा। अपना चुनें:

Cursor