Skip to main content
Use the @bijection/connectors/vercel entrypoint to declare Vercel resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Deployments

pull: Deployment observation with signed webhook hints

The following example matches configuration webhooks.

Configuration: standard

Case: vercel/deployments/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: vercel. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: deployments
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Configuration: webhooks

Case: vercel/deployments/pull/webhooks. Connection and resource configuration are declared by this exact case. Credential kind: vercel. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: deployments
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Production pointer

pull: The project’s production deployment

The following example matches configuration standard.

Configuration: standard

Case: vercel/production/pull/standard. Connection and resource configuration are declared by this exact case. Credential kind: vercel. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: production
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. A read-only observation feed. Vercel is not a system of record here: nothing deploys, promotes or rolls back. A 201 promotion is acceptance of a request, and a repeated promote’s 409 means “already true”. The connection holds a vercel bearer credential (vercel.credential) for https://api.vercel.com. Bindings name the teamId and projectId. Identity is the team id. deployments.pull lists the project’s deployments, newest first, by pagination.next sent back as until. State is Vercel’s own readyState. A deployment missing from a listing is not withdrawn. The listing endpoint was not exercised by the probe, which read single deployments; it is declared from Vercel’s published API. With updates: "webhooks", a delivery verified as HMAC-SHA1 in hex over the raw body (x-vercel-signature), identified by its body id, requests a point read of payload.deployment.id. No timestamp is signed, so replay is bounded only by the delivery ring and a delivery proves a refresh hint. production.pull reads the project’s targets.production.id: this read, not a promote’s answer, says which deployment serves production. The analytics points query answered 402 on the probed plan, so no analytics read is declared. Nothing here has run against Vercel or been qualified.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.