Find the cause. Take the next step.
Practical answers for setup, authentication, delivery, and events.
The next useful check.
Look at the evidence before changing the integration.
Authentication fails
Check that you are using the workspace’s regional host and a valid credential with the required permission. Keep API keys on your server.
The request is accepted, but nothing arrived
Read the message and recipient events using the returned ID. Check the sender, destination, and any rejection reason. An accepted request is not a delivery receipt.
A sending domain is still pending
Compare the requested DNS records with the published records. Allow time for DNS propagation, then verify again.
A webhook did not reach my endpoint
Inspect the endpoint’s response, TLS configuration, and request logs. Separate event-delivery failures from the underlying message state.
An agent lists tools but cannot use them
Complete the client’s Bird sign-in. Check the delegated permissions and selected workspace, then retry a read operation.
A retry returned an unexpected result
Inspect the original operation before starting a new send. For an idempotent retry, preserve its request body and key.
Keep the reference close.
Find the exact contract for the behavior you are investigating.
MCP server
Connect your assistant to Bird through a hosted endpoint.
Agent skills
Give your agent the product context for its next task.
API reference
Inspect requests, responses, and supported operations.
SDKs
Work in Node.js, Python, Go, or PHP.
CLI
Run product operations from your terminal.
Webhooks
Connect asynchronous events to your application.
Integrations
Bring Bird into your existing tools.
No matches. Try a product name or a shorter phrase.