---
title: "Update Resource Secrets"
method: PUT
path: "/v1/installations/{integrationConfigurationId}/resources/{resourceId}/secrets"
tags: ["marketplace"]
---

# Update Resource Secrets

`PUT /v1/installations/{integrationConfigurationId}/resources/{resourceId}/secrets`

## Request

- Base URL: `https://api.vercel.com`
- URL: `https://api.vercel.com/v1/installations/{integrationConfigurationId}/resources/{resourceId}/secrets`
- Auth: HTTP bearer

This endpoint updates the secrets of a resource. If a resource has projects connected, the connected secrets are updated with the new secrets. The old secrets may still be used by existing connected projects because they are not automatically redeployed. Redeployment is a manual action and must be completed by the user. All new project connections will use the new secrets.<br/> <br/> Use cases for this endpoint:<br/> <br/> - Resetting the credentials of a database in the partner. If the user requests the credentials to be updated in the partner’s application, the partner post the new set of secrets to Vercel, the user should redeploy their application and the expire the old credentials.<br/>

## Path parameters

- `integrationConfigurationId` string, required
- `resourceId` string, required

## Request body

- object
  - `secrets` object[], required
    - `name` string, required
    - `value` string, required
    - `prefix` string
    - `environmentOverrides` object: A map of environments to override values for the secret, used for setting different values across deployments in production, preview, and development environments. Note: the same value will be used for all deployments in the given environment.
      - `development` string: Value used for development environment.
      - `preview` string: Value used for preview environment.
      - `production` string: Value used for production environment.
  - `partial` boolean: If true, will only overwrite the provided secrets instead of replacing all secrets.

## Response `201`

## Other responses

- `400`: One of the provided values in the request body is invalid. One of the provided values in the request query is invalid.
- `401`: The request is not authorized.
- `403`: You do not have permission to access this resource.
- `404`
- `409`
- `410`

## Changes

- **2026-10-23** `a24f99b1631b`: 1 info
  - removed the non-success response with the status `422`
- **2026-07-21** `2ae10ee9d21c`: 1 info
  - added the non-success response with the status `410`
- **2025-10-09** `50caddad4ae7`: 5 info
  - added the new optional request property `secrets/items/environmentOverrides/development`
  - added the new optional request property `secrets/items/environmentOverrides/preview`
  - added the new optional request property `secrets/items/environmentOverrides/production`
  - removed 'propertyNames' constraint from the request property `secrets/items/environmentOverrides`
  - …1 more
- **2025-05-17** `67f6a93c3cd8`: 2 info
  - added the new optional request property `secrets/items/environmentOverrides`
  - added the non-success response with the status `422`
- **2025-03-19** `37b482c58c92`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/vercel/apis/vercel-api/changes/v1/installations/:integrationConfigurationId/resources/:resourceId/secrets/put.md)

---

[API](https://skmtc.dev/vercel/apis/vercel-api.md) - [All operations](https://skmtc.dev/vercel/apis/vercel-api/llms.txt) - [OpenAPI document](https://skmtc.dev/vercel/apis/vercel-api/revisions/60686c0e1f6a?raw)