---
title: "Update a VPC peering"
method: PATCH
path: "/v2/vpc_peerings/{vpc_peering_id}"
tags: ["DigitalOcean-public.v2-new_VPC Peerings"]
---

# Update a VPC peering

`PATCH /v2/vpc_peerings/{vpc_peering_id}`

To update the name of a VPC peering, send a PATCH request to `/v2/vpc_peerings/$VPC_PEERING_ID` with the new `name` in the request body.

## Path parameters

- `vpc_peering_id` string, uuid, required

## Request body

- VpcPeeringUpdatable
  - `name` string — The name of the VPC peering. Must be unique within the team and may only contain alphanumeric characters and dashes.

## Response `200`

The response will be a JSON object with a key called `vpc_peering`. The value of this will be an object that contains the standard attributes associated with a VPC peering.

- object
  - `vpc_peering` VpcPeering
    - `id` string, uuid — A unique ID that can be used to identify and reference the VPC peering.
    - `created_at` string, date-time — A time value given in ISO8601 combined date and time format.
    - `status` 'PROVISIONING' | 'ACTIVE' | 'DELETING' — The current status of the VPC peering.
    - `vpc_ids` string[] — An array of the two peered VPCs IDs.
    - `name` string — The name of the VPC peering. Must be unique within the team and may only contain alphanumeric characters and dashes.

## Other responses

- `401` — Authentication failed due to invalid credentials.
- `404` — The resource was not found.
- `429` — The API rate limit has been exceeded.
- `500` — There was a server error.
- `default` — There was an unexpected error.

---

[API](https://skmtc.net/digitalocean/apis/digitalocean-api.md) · [All operations](https://skmtc.net/digitalocean/apis/digitalocean-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/digitalocean/digitalocean-api/revisions/cb3bf9b21459/schema)