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

Make your first message land.

A customer places an order. Give them a clear, personal confirmation, and know what happens after you send.

Este ejercicio del navegador simula mensajes. Tu trabajo permanece aquí hasta que salgas. Inicia sesión para guardar tu progreso y evaluaciones.

Personalize the order confirmation, then send it to the practice inbox.

Resultado de la práctica

Your practice output will appear here.
Mostrar una pista

Use a customer name and an order number. Then send the message and watch the status change.

Continuar con el aprendizaje guardado

Enviar al sandbox de email

Configura el SDK y la clave de API en tu propio entorno de servidor. Este ejemplo usa el destinatario de prueba autorizado por Bird.

1
2
3
4
5
6
7
8
9
10
// Install the SDK
// npm install @messagebird/sdk

const msg = await bird.email.send({
  from: { email: "onboarding@messagebird.dev", name: "Bird" },
  to: ["delivered@messagebird.dev"],
  subject: "Hello from Bird",
  html: "<p>My first Bird email.</p>",
});
console.log(msg.id, msg.status); // "em_…", "accepted"

Un brief para tu agente de código

# Build with Bird: Email

Read these current sources before proposing an implementation:

- Send your first email: https://bird.com/docs/get-started/send-your-first-email
- Email: https://bird.com/email-api

## Task

Help me implement Email 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.

Tu próxima idea. Lista para conectar.