Network Peering
This API reference is deprecated. It will be removed in a future release. For the latest API reference, see the MongoDB Atlas Administration API Specification. This new API specification might take several seconds to load. MongoDB appreciates your patience as it improves this experience.
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
Endpoints
The following lists the endpoints available for Network Peering.
Method | Endpoint | Description |
|---|---|---|
GET | Get details for all network peering containers in an Atlas
project. | |
GET | Get details for all network peering containers in an Atlas
project for a single cloud provider. | |
GET | Get details for one network peering container in an Atlas
project. | |
POST | Create one new network peering container in an Atlas
project. | |
PATCH | Update details for one network peering container in an Atlas
project. | |
DELETE | Remove one network peering container in an Atlas project. | |
GET | Get details for all network peering connections in an Atlas
project. | |
GET | Get details for one network peering connection in an Atlas
project. | |
POST | Create a new network peering connection in an Atlas project. | |
PATCH | Update a new network peering connection in an Atlas project. | |
DELETE | Delete one network peering connection in an Atlas project. | |
GET | Verify if an Atlas project is in Connect via Peering Only mode. NoteAtlas has deprecated Connect via Peering Only. You should use split horizon connection strings. | |
PATCH | Disable Connect via Peering Only mode for one Atlas project. NoteAtlas has deprecated Connect via Peering Only. You should use split horizon connection strings. |