Bird supports API and SMTP delivery. The API transport needs both an access key and workspace ID; SMTP uses a single SMTP API key. For API delivery, the profile also lets you choose the API region. Use credentials from the Bird account that owns the intended sending workspace.
Before you begin#
Have a provider account and credentials for the transport you chose. Copy credentials from the provider’s own console or account settings; never put secret values in documentation. Check the provider’s documentation for account requirements and sender acceptance.
Supported transport and settings#
- Transport scheme: bird+api (default), bird+smtp, bird+smtps.
- Required settings: bird+api: Bird API access key (secret) and Bird API workspace ID. bird+smtp or bird+smtps: Bird SMTP API key (secret); it must begin with bk_eu1_ or bk_us1_.
- Optional settings: Bird API region is available for bird+api and defaults to eu. Choose eu or us to match the key/workspace region.
Jooosi Mail marks password, token, key, and private-key fields as secrets in the connection form. Enter only the fields shown for the selected scheme.
Create the connection#
- In WordPress admin, open Jooosi Mail → Connections and choose New connection.
- Enter a descriptive Connection name and select Bird in Profile.
- Choose the transport scheme you want to use. Enter its required fields listed above and leave fields for other schemes empty.
- Review the sender, routing, and advanced settings for this connection.
- Choose Create connection to save it.
For the shared form workflow, see Connect a provider.
Verify delivery#
Follow Send a test email and send to a mailbox you can check. A test sends a real email. Check the mailbox and Jooosi Mail → Logs for the attempt status. For supported webhooks, see the provider note and Provider webhooks guide.
Webhooks#
Bird webhooks are supported, including batched event payloads. Enable Webhooks under Advanced settings, save the connection, and configure the callback shown there using Bird’s webhook documentation. The adapter currently accepts the SparkPost-compatible batch format and does not verify request signatures.
Troubleshooting#
- For API delivery, check that the access key, workspace ID, and selected region belong together.
- For SMTP, confirm the key has the required bk_eu1_ or bk_us1_ prefix and that you selected the matching SMTP scheme.
Provider reference: https://docs.bird.com/api/email-api/transmissions.