---
title: "Create a New VPC Peering"
method: POST
path: "/v2/vpc_peerings"
tags: ["DigitalOcean-public.v2-new_VPC Peerings"]
---

# Create a New VPC Peering

`POST /v2/vpc_peerings`

To create a new VPC Peering, send a POST request to `/v2/vpc_peerings` 
specifying a name and a list of two VPC IDs to peer. The response code, 202 
Accepted, does not indicate the success or failure of the operation, just 
that the request has been accepted for processing.

## Request body

- object
  - `name` string, required — The name of the VPC peering. Must be unique within the team and may only contain alphanumeric characters and dashes.
  - `vpc_ids` string[], required — An array of the two peered VPCs IDs.

## Response `202`

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.
- `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)