Fields removed in POST /v13/deployments response 200: [nodeVersion env meta checksState createdIn gitRepo integrations connectBuildsEnabled aliasFinal builds in…

What changed

Fields removed in POST /v13/deployments response 200: [nodeVersion env meta checksState createdIn gitRepo integrations connectBuildsEnabled aliasFinal builds initReadyAt automaticAliases name defaultRoute microfrontends images passiveRegions gitSource config errorLink checks createdAt crons oidcTokenClaims alwaysRefuseToBuild public buildErrorAt routes inspectorUrl readyState isInConcurrentBuildsQueue buildArtifactUrls aliasAssignedAt isInSystemBuildsQueue version buildSkipped project isFirstBranchDeployment services customEnvironment plan readySubstate seatBlock userAliases ready softDeletedByRetention url platform ownerId undeletedAt bootedAt errorStep alias errorCode canceledAt prebuilt target build lambdas deletedAt buildingAt attribution ttyBuildLogs status team projectId originCacheRegion userConfiguredDeploymentId oomReport flags type aliasWarning readyStateReason autoAssignCustomDomains projectSettings passiveConnectConfigurationId regions buildContainerFinishedAt checksConclusion aliasError connectConfigurationId errorMessage functions id manualProvisioning monorepoManager creator previewCommentsEnabled aliasAssigned source] Affected surface: POST /v13/deployments. Root cause: endpoint `POST /v13/deployments`. Detected at Thu, 23 Jul 2026 20:21:40 UTC UTC.

Diff

{
  "path": "POST /v13/deployments",
  "removed_fields": [
    "nodeVersion",
    "env",
    "meta",
    "checksState",
    "createdIn",
    "gitRepo",
    "integrations",
    "connectBuildsEnabled",
    "aliasFinal",
    "builds",
    "initReadyAt",
    "automaticAliases",
    "name",
    "defaultRoute",
    "microfrontends",
    "images",
    "passiveRegions",
    "gitSource",
    "config",
    "errorLink",
    "checks",
    "createdAt",
    "crons",
    "oidcTokenClaims",
    "alwaysRefuseToBuild",
    "public",
    "buildErrorAt",
    "routes",
    "inspectorUrl",
    "readyState",
    "isInConcurrentBuildsQueue",
    "buildArtifactUrls",
    "aliasAssignedAt",
    "isInSystemBuildsQueue",
    "version",
    "buildSkipped",
    "project",
    "isFirstBranchDeployment",
    "services",
    "customEnvironment",
    "plan",
    "readySubstate",
    "seatBlock",
    "userAliases",
    "ready",
    "softDeletedByRetention",
    "url",
    "platform",
    "ownerId",
    "undeletedAt",
    "bootedAt",
    "errorStep",
    "alias",
    "errorCode",
    "canceledAt",
    "prebuilt",
    "target",
    "build",
    "lambdas",
    "deletedAt",
    "buildingAt",
    "attribution",
    "ttyBuildLogs",
    "status",
    "team",
    "projectId",
    "originCacheRegion",
    "userConfiguredDeploymentId",
    "oomReport",
    "flags",
    "type",
    "aliasWarning",
    "readyStateReason",
    "autoAssignCustomDomains",
    "projectSettings",
    "passiveConnectConfigurationId",
    "regions",
    "buildContainerFinishedAt",
    "checksConclusion",
    "aliasError",
    "connectConfigurationId",
    "errorMessage",
    "functions",
    "id",
    "manualProvisioning",
    "monorepoManager",
    "creator",
    "previewCommentsEnabled",
    "aliasAssigned",
    "source"
  ],
  "schema_path": "POST /v13/deployments response 200"
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Recommended action

Diff your serializers against the new schema. The diff above shows what moved.