Overview
DIV3RSA uses a Vercel External / Connectable Integration. A Vercel account owner explicitly chooses the Vercel team and projects that the integration may access. DIV3RSA does not treat a Vercel identity login by itself as project authorization.
Installation
- Sign in to DIV3RSA and open Integrations.
- Select Connect for Vercel.
- You are redirected to Vercel's installation flow.
- Select the Vercel account or team and the projects you want to authorize.
- Review the requested permissions and approve the installation.
- Vercel redirects back to DIV3RSA. DIV3RSA exchanges the authorization code for an installation token and verifies the selected projects.
The production callback used by the integration is https://system.div3rsa.com/api/integrations/vercel/callback.
Requested access
DIV3RSA requests only access required by the Vercel features currently exposed by the platform. The exact labels shown by Vercel may change over time.
| Area | Purpose |
|---|---|
| User · Read | Display the connected Vercel identity when available. |
| Team · Read | Resolve the team selected during installation and scope API requests correctly. |
| Project · Read | Discover the projects explicitly made available to the integration. |
| Deployment · Read | List deployments, inspect deployment state and retrieve deployment-related diagnostics. |
| Deployment · Write | Create or roll back a deployment when an authorized DIV3RSA user explicitly invokes the corresponding action. |
DIV3RSA does not request domain or environment-variable write access as part of the current Vercel integration.
Webhooks and deployment events
Vercel sends signed HTTPS POST requests to https://system.div3rsa.com/api/integrations/vercel/webhook. DIV3RSA verifies the x-vercel-signature header using the integration secret before accepting an event.
The integration can process deployment lifecycle events including created, build requested, error, blocked, canceled, succeeded, promoted, rollback and ready events. It can also process selected project and integration-configuration events so project access stays synchronized when the Vercel installation changes.
Webhook events are de-duplicated by the Vercel event identifier. DIV3RSA stores operational event metadata such as project ID, deployment ID, state, target, branch/commit metadata and event time. It does not use the webhook as a bulk log-ingestion channel.
Deployment and runtime logs
When an authorized user asks DIV3RSA to investigate a deployment, the platform uses the stored Vercel project and deployment identifiers to request current deployment information and logs from Vercel. This enables workflows such as detecting a failed deployment, retrieving the relevant build/runtime output and presenting the failure context to the user.
Log access is performed server-side with the Vercel installation credential associated with that DIV3RSA connection. Credentials are not exposed to the browser or returned to the model as plain text.
Security model
- OAuth state is bound to the authenticated DIV3RSA integration session.
- A Vercel installation configuration and readable project scope are required before the connection becomes active.
- Vercel credentials are stored server-side and protected from normal user access.
- Webhook signatures are verified before payload processing.
- Webhook deliveries are idempotent to protect against duplicate retries.
- Project-scoped authorization is enforced before deployment actions or log access are executed.
- DIV3RSA maintains audit and execution controls around privileged integration actions.
Changing project access
If you add or remove Vercel projects from the installation, Vercel may send integration configuration or project connection events. DIV3RSA uses these events to refresh the projects and capabilities associated with the connection. A project removed from the Vercel installation must no longer be treated as an authorized DIV3RSA resource.
Disconnecting Vercel
You can disconnect the integration from DIV3RSA. Disconnecting revokes the DIV3RSA-side connection, removes discovered project bindings and invalidates outstanding integration execution grants. You may also uninstall or change the integration directly in Vercel. For complete revocation, remove the installation in Vercel as well.
Troubleshooting
No projects appear after authorization
Confirm that at least one project was selected in the Vercel installation and that Project Read access was granted. DIV3RSA intentionally rejects identity-only connections with zero readable projects.
Deployment or log access returns permission denied
Review the Vercel installation scopes and confirm that the affected project is still included. Reconnect the integration if Vercel requires a permission upgrade.
Webhook deliveries fail
Confirm that the configured webhook URL is https://system.div3rsa.com/api/integrations/vercel/webhook, that HTTPS is used and that the integration secret configured in DIV3RSA matches the Vercel integration.
Support
For integration support, visit DIV3RSA Support or email info@div3rsa.com. Include the affected DIV3RSA workspace, Vercel team/project name and deployment ID where relevant. Do not send access tokens or client secrets by email.