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.
Alert history
- Additive
Add 410 Gone error response code
A new HTTP
410 Goneerror 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
membershipfield has been removed from therequiredarray in two distinct response object schemas (one appears to be a team/project schema around line 167344, another around line 167679). Clients that currently expectmembershipto 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
versionfield has been removed from two response object schemas — the scheduled-expiry object (previously required alongsideexpiresAt) and the locked object (previously required alongsidelockedAtandlockedBy) — across 6 endpoint definitions. Clients that read and depend onversion(e.g. to trackExpireProjectevent 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
__networkPolicyForwardRulesproperty 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 — includingdomainpatterns andforwardURLvalues — 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
delegatedProtectionClientfield (array ofACLActionitems) 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.