Vercel integration

In short

List projects and deployments and check their status. Connect it on the Integrations page; your app then calls Vercel through Sapilon without ever holding a Vercel credential.

Lets your app list the projects, deployments and teams a Vercel access token can see, and read a deployment’s state. It cannot deploy, change settings or read environment variables.

Connecting

On the Integrations page choose Connect on Vercel and fill in:

Access token — vercel.com/account/settings/tokens → Create. Scope it to the team the app should see.

Sapilon checks the key with the provider before it saves it, and stores it encrypted; it is never shown again.

What your app can do

Only these requests are available; anything else is refused.

GET /v2/user
GET /v2/teams
GET /v9/projects
GET /v9/projects/*
GET /v6/deployments
GET /v13/deployments/*

How the agent uses it

Use integrations.request('vercel', …); paths are relative to https://api.vercel.com and carry their own version.

GET /v2/user, GET /v2/teams — the account and its teams. For a team’s data add query: { teamId } to the calls below.
GET /v9/projects, GET /v9/projects/{idOrName} — Example: { method: 'GET', path: '/v9/projects', query: { teamId: 'team_abc' } }.
GET /v6/deployments — recent deployments. Example: { method: 'GET', path: '/v6/deployments', query: { projectId: 'prj_abc', limit: '10' } }.
GET /v13/deployments/{idOrUrl} — one deployment; body.readyState is READY, BUILDING or ERROR.

Read-only.

More from Vercel: https://vercel.com/docs/rest-api