Check if a manifest exists | Vercel REST API

APIs & SDKs

Check if a manifest exists

HEADhttps://api.vercel.com/v2/{teamSlug}/{projectSlug}/{repositoryName}/manifests/{reference}

HEAD /v2/:teamSlug/:projectSlug/:repositoryName/manifests/:reference Check whether a manifest exists. Used by Docker client during push to determine if a manifest (or config blob referenced by digest) is already present.

https://api.vercel.com/v2/{teamSlug}/{projectSlug}/{repositoryName}/manifests/{reference}

const response = await fetch('https://api.vercel.com/v2/teamSlug/projectSlug/repositoryName/manifests/reference', {
  method: 'HEAD',
  headers: {
    'Authorization': 'Bearer YOUR_ACCESS_TOKEN',
    'Content-Type': 'application/json',
  },
});

const data = await response.json();
console.log(data);

Response

"value"

Path parameters

teamSlugstringRequired

Single Docker repository team slug component.

projectSlugstringRequired

Single Docker repository project slug component.

repositoryNamestringRequired

Single Docker repository name component.

referencestringRequired

Manifest reference: a tag or digest.

Response

200Success

Errors

400One of the provided values in the request query is invalid.

401The request is not authorized.

402The account is missing a payment so payment method must be updated

403You do not have permission to access this resource.

404Error

410Error

Cross-link map: Check if a manifest exists (/docs/rest-api/vcr/check-if-a-manifest-exists)

From the Vercel docs graph (built 2026-10-10T05:32:43.016Z), spanning vercel.com docs + KB, nextjs.org, ai-sdk.dev, and other Vercel documentation sites. Full graph as JSON: https://vercel.com/docs/graph.json

Semantically closest pages

Pull an image manifest — GET /v2/{teamSlug}/{projectSlug}/{repositoryName}/manifests/{reference} — GET /v2/:teamSlug/:projectSlug/:repositoryName
Push an image manifest — PUT /v2/{teamSlug}/{projectSlug}/{repositoryName}/manifests/{reference} — PUT /v2/:teamSlug/:projectSlug/:repositoryName
Delete an image manifest — DELETE /v2/{teamSlug}/{projectSlug}/{repositoryName}/manifests/{reference} — DELETE /v2/:teamSlug/:projectSlug/:reposito
Check if a blob exists — HEAD /v2/{teamSlug}/{projectSlug}/{repositoryName}/blobs/{digest} — HEAD /v2/:teamSlug/:projectSlug/:repositoryName/blob
Create a check — POST /v2/projects/{projectIdOrName}/checks — Creates a new check for a project.

This page links to (1)

Vercel REST API Reference — Interact programmatically with your Vercel account using the SDK or direct HTTP requests.

Pages that link here (1)

By site: vercel-docs (1)

Vercel REST API Reference — Interact programmatically with your Vercel account using the SDK or direct HTTP requests.

https://api.vercel.com/v2/{teamSlug}/{projectSlug}/{repositoryName}/manifests/{reference}

const response = await fetch('https://api.vercel.com/v2/teamSlug/projectSlug/repositoryName/manifests/reference', {
  method: 'HEAD',
  headers: {
    'Authorization': 'Bearer YOUR_ACCESS_TOKEN',
    'Content-Type': 'application/json',
  },
});

const data = await response.json();
console.log(data);

Response

"value"

OpenAPI Specification