Add Entries to One User's Whitelist (Deprecated)¶
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
.
- You can't create new Personal API Keys.
- You can't access the API using your existing Personal API Keys starting March 1, 2021.
- You must update any existing scripts or tools to use Programmatic API Keys instead.
Don't confuse this resource with the Project IP Access List resource. That resource controls client access to the project's MongoDB clusters.
Use the following resource to create an entry in your API whitelist.
Atlas whitelists this endpoint. It must originate from an address already on your API whitelist.
The Atlas API authenticates using HTTP Digest Authentication. Provide a programmatic API public key and corresponding private key as the username and password when constructing the HTTP request.
To learn how to configure API access for an Atlas project, see Configure Atlas API Access.
Resource¶
Base URL: https://cloud.mongodb.com/api/atlas/v1.0
POST /users/USER-ID/whitelist
The entity body must be an array of objects, even if it contains only
one object. Each object should specify either the cidrBlock
field
or ipAddress
field, but not both.
If an address is already in the whitelist, it will be ignored.
If you specify a single IP address with the /32
subnet mask,
Atlas does not store the /32
, as the /32
does not change
the address. For example, an address of 12.34.56.78
is the same as
12.34.56.78/32
.
Request Parameters¶
Request Path Parameters¶
Path Parameter | Type | Necessity | Description |
---|---|---|---|
USER-ID | string | Required | Unique 24-hexdecimal-digit string that identifies your Atlas user. To retrieve user IDs, see Get All Users in One Project. Your user ID corresponds to the id field returned in the response from that endpoint. |
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 | Necessity | Description | Default |
---|---|---|---|---|
pageNum | integer | Optional | Page number, starting with one, that Atlas returns of the
total number of objects. | 1 |
itemsPerPage | integer | Optional | Number of items that Atlas returns per page, up to a maximum
of 500. | 100 |
includeCount | boolean | Optional | Flag that indicates whether Atlas returns the totalCount
parameter in the response body. | true |
pretty | boolean | Optional | Flag that indicates whether Atlas returns the JSON
response in the
prettyprint format. | false |
envelope | boolean | Optional | Flag that indicates whether Atlas wraps the response in an envelope. Some API clients cannot access the HTTP response headers or
status code. To remediate this, set Endpoints that return a list of results use the results object as an envelope. Atlas adds the status parameter to the response body. | false |
Request Body Parameters¶
Name | Type | Necessity | Description |
---|---|---|---|
cidrBlock | string | Optional | CIDR |