Check Status of Cluster Operations

Info With Circle IconCreated with Sketch.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.

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.

GET /groups/{GROUP-ID}/clusters/{CLUSTER-NAME}/status
Path ElementNecessityDescription
GROUP-IDRequiredUnique identifier of the project containing the cluster.
CLUSTER-NAMERequiredName of the cluster.

This endpoint might use any of the HTTP request query parameters available to all Atlas API resources. All of these are optional.

prettybooleanOptionalFlag indicating whether the response body should be in a prettyprint format.false

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:

statusHTTP response code
envelopeExpected response body

This endpoint doesn't use HTTP request body parameters.


Status of the operation on the cluster. Value can be:

  • APPLIED: The operation completed successfully.
  • PENDING: The operation is still running.
curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" \
--digest \
--header "Content-Type: application/json" \
--include \
--request GET "{GROUP-ID}/clusters/{CLUSTER-NAME}/status?pretty=true"
"changeStatus": "APPLIED"
Give Feedback