OAuth Guide
← All guides

Vercel

Moderate

Third-party API access to a user's Vercel account goes through a connectable-account Integration: you fill a long listing-style form (logo, EULA, privacy policy, gallery image) in the Integrations Console, and it can then be installed by anyone via its URL with a Community badge, with no review.

Agent-researched, not yet reviewed by a personResearched 2026-10-20

Working in dev

1–3 hours

Signing in with your own account

Any user can connect

Same day

A connectable-account (Community) integration shared via https://vercel.com/integrations/<slug>/new, which is what an agent reading projects or deployments needs; a Marketplace listing is optional and takes far longer.

Waiting on
No review needed for Community integrations. Marketplace listing waits on 500 active installs, then a manual review by integrations@vercel.com.
Cost
No fees found in the docs

What you need first

  • A Vercel account or team to own the integration

    Integrations are created from the Integrations Console of a team, and the team's owners manage it.

  • Public EULA URL, privacy policy URL, website, documentation URL and support email

    All are required fields in the Create Integration form; the support email is publicly listed.

  • A square logo (non-transparent PNG, min 256px) and 1–8 gallery images at 1920x1080

    Logo and feature media are required form fields, even for Community integrations.

  • A Redirect URL endpoint that serves a popup UI and exchanges the code

    Vercel opens your Redirect URL in a popup during installation; it must exchange the code, let the user map projects, and then redirect to the 'next' URL.

Who does what

Vercel OAuth setup · OAuth Guide