Get All Pending Invoices for One Organization¶
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.
Request Path Parameters¶
Unique identifier of the organization.
Request Query Parameters¶
This endpoint might use any of the HTTP request query parameters available to all Atlas API resources. All of these are optional.
Flag indicating whether the response body should be in a prettyprint format.
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:
Request Body Parameters¶
This endpoint does not use HTTP request body parameters.
If you set the query element
true, the response is wrapped
The HTTP response returns a JSON document that includes the following objects:
Amount billed in this invoice, calculated as subtotalCents + salesTaxCents - startingBalanceCents
Amount paid for this invoice.
Timestamp in ISO 8601 date and time format in UTC when this invoice was created.
Amount credited by MongoDB, in USD cents.
Timestamp in ISO 8601 date and time format in UTC when the billing period for this invoice ended.
Unique identifier of the project with which the invoice is associated. Does not appear on all invoices.
Unique identifier for this invoice.
Line items in the invoice. This information is also found in the Usage Details section of the Invoice page in the Atlas UI.
Each object in the array includes the following fields:
One or more links to sub-resources and/or related resources. The relation-types between URL