Delete One Organization Invitation¶
On this page
Deletes one pending invitation to the specified Atlas organization. You can't delete an invitation that a user has accepted
The Atlas Administration 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 Get Started with the Atlas Administration API.
Required Roles¶
You can successfully call this endpoint with the Organization Owner
role.
Resource¶
https://cloud.mongodb.com/api/atlas/v1.0
DELETE /orgs/{ORG-ID}/invites/{INVITATION-ID}
Request Path Parameters¶
Path Element | Type | Necessity | Description |
---|---|---|---|
ORG-ID | string | Required | Unique 24-hexadecimal digit string that identifies the
organization. |
INVITATION-ID | string | Required | Unique 24-hexadecimal digit string that identifies the
invitation. |
Request Query Parameters¶
This endpoint might use any of the HTTP request query parameters available to all Atlas Administration API resources. All of these are optional.
Name | Type | Necessity | Description | Default | ||||||
---|---|---|---|---|---|---|---|---|---|---|
pretty | boolean | Optional | Flag indicating whether the response body should be in a
prettyprint format. | false | ||||||
envelope | boolean | Optional | Flag indicating if Atlas should wrap the response in a JSON envelope. This option may be needed for some API clients. These 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:
| false |
Request Body Parameters¶
This endpoint does not use HTTP request body parameters.
Response¶
This endpoint returns an empty JSON document.
Example Request¶
curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest --include \ --header "Accept: application/json" \ --request DELETE "https://cloud.mongodb.com/api/atlas/v1.0/orgs/{ORG-ID}/invitations/{INVITATION-ID}"
Example Response¶
Response Header¶
401 Unauthorized Content-Type: application/json;charset=ISO-8859-1 Date: {dateInUnixFormat} WWW-Authenticate: Digest realm="MMS Public API", domain="", nonce="{nonce}", algorithm=MD5, op="auth", stale=false Content-Length: {requestLengthInBytes} Connection: keep-alive
204 No Content Vary: Accept-Encoding Content-Type: application/json Strict-Transport-Security: max-age=300 Date: {dateInUnixFormat} Connection: keep-alive Content-Length: {requestLengthInBytes}
Response Body¶
This endpoint returns an empty JSON object.