Admin API alert configurations for billing events
Parent: Atlas Billing Mechanics and Cost Visibility · Published reference · snapshot 2026-10-21 · skill ranked-2d47adf8
↓ Facts as markdownall context files
Source-anchored research for Admin API alert configurations for billing events. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Structure and components
- Atlas's billing event catalogue marks `DAILY_BILLING_CHANGE_OVER_THRESHOLD` alertable and `DAILY_BILLING_CHANGE_NORMAL` not alertable; the catalogue therefore contains events that are not triggers, and its full set should not be substituted for the project endpoint's five-value enum. (medium confidence) (verified as of 2026-10-14) [source]
Comparisons and alternatives
- The event catalog is broader than the billing alert configuration enum: BILLING_EMAIL_ADDRESS_ADDED is marked not alertable, while threshold names such as ORG_INVOICE_OVER_THRESHOLD and DAILY_BILL_OVER_THRESHOLD are marked alertable. Use the billing configuration's allowed eventTypeName values instead of assuming every billing-related event is a configurable alert trigger. (high confidence) (verified as of 2026-10-21) [source]
- Atlas's access guidance says Project Owner or Project Alerts Manager access is needed to manage project alerts, while Organization Billing Admin has limited billing-alert authorization; because the `groups/{groupId}` API is project-scoped, callers should verify project access rather than assume an organization billing role covers that project configuration. (medium confidence) (verified as of 2026-10-14) [source]
Facts and statements
- The published Atlas Admin API v2 create and list operations for alert configurations are project scoped: POST /api/atlas/v2/groups/{groupId}/alertConfigs and GET /api/atlas/v2/groups/{groupId}/alertConfigs. The API docs equate groupId with the project ID, and Pulumi's third-party resource likewise requires projectId and identifies it as the official API's groupId. (high confidence) (verified as of 2026-10-21) [source]
- The v2 create schema's Billing Threshold Alert Configuration accepts PENDING_INVOICE_OVER_THRESHOLD, DAILY_BILL_OVER_THRESHOLD, DAILY_BILLING_CHANGE_OVER_THRESHOLD, WEEKLY_BILLING_CHANGE_OVER_THRESHOLD, and MONTHLY_BILLING_CHANGE_OVER_THRESHOLD as eventTypeName values. The event catalog describes these as alertable project billing thresholds. (high confidence) (verified as of 2026-10-21) [source]
- Atlas UI documentation separates organization and project billing alerts. Organization rules include the current bill for the organization, the current bill for any one project, and daily, weekly, or monthly gross-spend changes. Yesterday's billed amount and credit-card expiry conditions apply to both organizations and projects; amount thresholds are in USD. (high confidence) (verified as of 2026-10-21) [source]
- The v2 create schema defaults enabled to false. Pulumi's independent resource documentation also says an omitted enabled value leaves the configuration disabled, so clients that expect notifications should explicitly set enabled to true. (high confidence) (verified as of 2026-10-21) [source]
- The third-party atlasapi 0.11.0 documentation lists both organization billing event names such as ORG_INVOICE_OVER_THRESHOLD and pending-invoice names such as PENDING_INVOICE_OVER_THRESHOLD. This is historical corroboration that the vocabulary distinguished billing scopes; it does not establish current Atlas Admin API v2 support. (low confidence) [source]
- The API describes Billing Threshold configurations as selecting bill or invoice thresholds, sets `enabled` to false by default, and requires a `notifications` list with 1 to 25 targets. (medium confidence) (verified as of 2026-10-21) [source]
- Pulumi's independent `AlertConfiguration` resource exposes project, event, enabled, notification, and threshold inputs; its docs require `metricThresholdConfig` only for `OUTSIDE_METRIC_THRESHOLD` and `OUTSIDE_SERVERLESS_METRIC_THRESHOLD`, separating metric alerts from billing threshold alerts. (medium confidence) (verified as of 2026-10-13) [source]
- The independent AtlasUI 0.3.4 documentation says its UI is built from Atlas OpenAPI specifications and lists alert-configuration management among its Atlas Admin API coverage; it does not enumerate billing event names, so it only corroborates general API support. (low confidence) [source]
Children
- Organization-scoped alert configuration API (frontier)
- Atlas billing alert notification delivery (frontier)
Frontier under this node: Atlas billing alert notification delivery, Organization-scoped alert configuration API