API >
API Resources >
Network Peering >
Delete One Existing Network Peering Connection

Delete One Existing Network Peering Connection¶

On this page

Base URL: https://cloud.mongodb.com/api/atlas/v1.0
Resource
Response Elements
Example Request
Example Response

Note

Groups and projects are synonymous terms. Your {GROUP-ID} is the same as your project ID. For existing groups, your group/project ID remains the same. The resource and corresponding endpoints use the term groups.

Base URL: `https://cloud.mongodb.com/api/atlas/v1.0`¶

Delete one network peering connection associated with one Atlas project. You must have the Project Owner role or the Organization Owner role to successfully call this endpoint.

AWS Only

If you delete the last network peering connection associated with a project, Atlas also removes any AWS security groups from the project whitelist.

Resource¶

copy

DELETE /groups/{GROUP-ID}/peers/{PEER-ID}

Request Path Parameters¶

Parameter	Type	Necessity	Description
`GROUP-ID`	string	Required	Unique identifier for the project.
`PEER-ID`	string	Required	Atlas assigned `unique ID` for the peering connection. Note This is separate from the peering container ID. Use the Get All Peering Connections API to retrieve a list of peering connection ids for an Atlas project.

Request Query Parameters¶

This endpoint may use any of the HTTP request query parameters available to all Atlas API resources. These are all optional.

Name Type Description Default

pretty boolean Indicates whether the response body should be in a prettyprint format. false

envelope

boolean

Indicates whether or not to wrap the response in an envelope.

Some API clients cannot access the HTTP response headers or status code. To remediate this, set envelope=true in the query.

For endpoints that return one result, the response body includes:

status	HTTP response code
envelope	The expected response body

false

Request Body Parameters¶

This endpoint does not use HTTP request body parameters.

Response Elements¶

This endpoint does not have response elements.

Example Request¶

copy

curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest \
  --header "Accept: application/json" \
  --request DELETE "https://cloud.mongodb.com/api/atlas/v1.0/groups/5356823b3794dee37132bb7b/peers/1112222b3bf99403840e8934?pretty=true"

Example Response¶

This endpoint returns an empty JSON Object.

← Update One New Network Peering Connection Verify Connect via Peering Only Mode for a Project →