---
title: "Your Bird key, already in Vercel"
canonical: "https://bird.com/integrations/vercel"
---

[Integrations](/integrations)

# 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.

[Connect on Vercel](https://vercel.com/marketplace/bird)

[See the setup](#setup)

## 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.

**Vercel**

Marketplace → Bird → Install

- Scopes: Projects, environment variables

The same flow starts from Integrations in the Bird dashboard.

**Bird**

Integrations → Vercel → Choose projects

- Workspace: Acme Production (eu1)
- Environment: Preview · Production

One installation per selection; install again for a different environment.

**Environment variables**

- BIRD_API_KEY: bk_eu1_…
- BIRD_API_BASE_URL: https://eu1.platform.bird.com

Encrypted, per project, per environment.

## 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.
- Scoped where you choose. Keep Preview on a test sender and Production on your real one by installing twice with different selections.
- 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.](/integrations/vercel-connect)

### Worth building

- Send a signup confirmation from a Route Handler.
- Email a receipt from a Server Action after checkout.
- Text a one-time code from an edge function.
- Keep Preview deployments on a test sender.
- Check delivery in Bird before closing the support ticket.
- Alert the on-call phone when a cron job fails.



## Related resources

- [Workflow automation](/automate/workflows) (product)
- [How do I use Bird from a low-code tool like n8n or Zapier?](/explained/platform/how-do-i-use-bird-from-a-low-code-tool-like-n8n-or-zapier) (answer)

[Get an implementation brief](/learn/workspace?topic=integrations)