Integrations / Vercel Marketplace
Your Bird key, already in Vercel
Install from the Vercel Marketplace or from the Bird dashboard. Either way Bird creates an API key and writes it, with your workspace's regional endpoint, into the Vercel projects and environments you select. Nothing to copy between dashboards.
Drag an icon onto the dots. Use arrow keys to move a focused icon. Press Escape to cancel a drag.
Two variables, no copy-paste
The integration saves BIRD_API_KEY and BIRD_API_BASE_URL as encrypted environment variables. The key carries channel-sending scopes and the normal default expiry; the base URL is the regional endpoint for your workspace, so the same code runs against the right region.
- Marketplace
- Bird
- Install
- Scopes
- Projects, environment variables
The same flow starts from Integrations in the Bird dashboard.
What the integration sets up.Credentials in the right place, and nothing else moved out of Bird.
Read them like any other env var. Server-side only. Use them in Route Handlers, Server Actions and edge functions, never in client code.
$ BIRD_API_KEY
$ BIRD_API_BASE_URL
Scoped where you choose. Keep Preview on a test sender and Production on your real one by installing twice with different selections.
$ Per project
$ Per environment
What this is not. No Marketplace billing, no provisioned resources. Senders, numbers and billing stay in Bird. For runtime tokens instead of a stored key, use Vercel Connect.
$ Not included
Put it into practice.
Continue with the documentation, guides and examples for this topic.