Dovkie
Sign in
Back to monitors

vercel

Vercel API

REST
OpenAPI (JSON)
https://openapi.vercel.sh/
Additive AI classification

Add mounts field to Vercel sandbox configuration

A new optional mounts field has been added to the sandbox API response schema. This field is an object containing key-value pairs of mount paths and volume configurations, with each mount supporting volume (required) and mode (optional, either "read-only" or "read-write"). Existing integrations are unaffected as this is purely additive.

Alert history

  • Additive

    Add mounts field to Vercel sandbox configuration

    A new optional mounts field has been added to the sandbox API response schema. This field is an object containing key-value pairs of mount paths and volume configurations, with each mount supporting volume (required) and mode (optional, either "read-only" or "read-write"). Existing integrations are unaffected as this is purely additive.

  • Additive

    Add vcrRepository ACL action field

    A new optional vcrRepository field has been added to multiple ACL (Access Control List) schemas in the Vercel API, allowing teams to define permissions for VCR repository-related actions. This is purely additive and does not affect existing integrations.

  • Additive

    Add 410 Gone error response code

    A new HTTP 410 Gone error response code has been added to an API endpoint. This is an additive change that documents a new possible error condition clients may encounter, allowing them to handle resource-gone scenarios properly.

  • Breaking

    membership field removed from required fields in two team/project response schemas

    The membership field has been removed from the required array in two distinct response object schemas (one appears to be a team/project schema around line 167344, another around line 167679). Clients that currently expect membership to always be present in these response objects may break if they treat its absence as an error, or if SDK-generated code enforces required-field validation.

  • Breaking

    Remove required `version` field from project expiry/lock response schemas

    The version field has been removed from two response object schemas — the scheduled-expiry object (previously required alongside expiresAt) and the locked object (previously required alongside lockedAt and lockedBy) — across 6 endpoint definitions. Clients that read and depend on version (e.g. to track ExpireProject event versioning or to seed a re-schedule counter) will no longer receive it, which is a breaking change for those integrations.

  • Breaking

    Remove __networkPolicyForwardRules field from VM config schema

    The __networkPolicyForwardRules property has been removed from two locations in the request body schema (both the create and update paths for VM/sandbox configurations). Any client currently sending this field to configure network forwarding rules — including domain patterns and forwardURL values — will no longer have those rules accepted by the API. This is a breaking change for integrations that relied on this field to set up proxy/forward rules for VM network traffic.

  • Additive

    Add delegatedProtectionClient field to ACL schemas

    The OpenAPI specification adds a new optional delegatedProtectionClient field (array of ACLAction items) to multiple ACL-related schema definitions across the Vercel API. This is a purely additive change that expands the ACL action configuration options without breaking existing integrations.