---
title: "Create a Peering with a VPC"
method: POST
path: "/v2/vpcs/{vpc_id}/peerings"
tags: ["DigitalOcean-public.v2-new_VPCs"]
---

# Create a Peering with a VPC

`POST /v2/vpcs/{vpc_id}/peerings`

To create a new VPC peering for a given VPC, send a POST request to
`/v2/vpcs/$VPC_ID/peerings`.

## Path parameters

- `vpc_id` string, uuid, required

## Request body

- object
  - `name` string, required — The name of the VPC peering. Must be unique and may only contain alphanumeric characters, dashes, and periods.
  - `vpc_id` string, uuid, required — The ID of the VPC to peer with.

## Response `202`

The response will be a JSON object with a key called `peering`, containing  the standard attributes associated with a VPC peering.

- object
  - `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/versions/cb3bf9b21459/schema)