Skip to main content
POST
Resolve and Pin Project Dependencies

Authorizations

Authorization
string
header
required

Use a JWT bearer token or a Veryfront API key in the Authorization header.

Path Parameters

project_reference
string
required

Project slug, UUID, or domain

Body

application/json
specifiers
string[]
required

npm package specifiers to resolve. Each entry may be a bare name, a name with an inline exact version, or a name with a semver range (e.g. "react", "[email protected]", "zod@^3", "@radix-ui/react-dialog").

Required array length: 1 - 100 elements
Required string length: 1 - 200
Example:
branch
string

Preview branch name or ID whose package.json receives the resolved pins.

Required string length: 1 - 255
Example:

"feature-a"

expected_declarations
object

Package declarations observed by the caller. A null value means the package was absent. When supplied, every requested package must be present and stale declarations are not overwritten.

Example:

Response

Resolved pins (may be a partial set if some specifiers failed)

pins
object
required

Resolved exact version pins keyed by package name. Includes both newly-written pins and pre-existing exact pins for all requested specifiers that were successfully resolved.

Example:
persisted
boolean
required

Whether the resolved pins were successfully written to the project's package.json. A false value means resolution succeeded but the write failed; pins still reflect the intended values and the caller may retry.

skipped
object
required

Requested packages not written because the current declaration no longer matched the caller snapshot.

Example: