[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fNganqV3UHL-04s6xs85BuW8BCXO-JXXymI3OlEpIFFY":3,"$fxD_Q1X-Q1l9FbKbuOpNiSHuuudD2z5Ff2QRLeu71GwQ":21},{"status":4,"source":5,"previous":12,"current":16,"newerSnapshotId":20,"olderSnapshotId":13},"has-previous",{"id":6,"displayName":7,"vendor":8,"kind":9,"apiType":10,"url":11},"mongodb-atlas-admin-openapi","MongoDB Atlas Admin API","mongodb","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fmongodb\u002Fopenapi\u002Fmain\u002Fopenapi\u002Fv2.json",{"id":13,"contentHash":14,"fetchedAt":15},"01KX1RHBAXE4H5704723YE035M","4b0287e8bf5f9602fe2c4693bee2547b4fcc268fb1c387557c1cb81985765feb","2026-07-08T21:00:57.424Z",{"id":17,"contentHash":18,"fetchedAt":19},"01KX441XC36PZFB1XZ59MAYRAM","30e073df2170287154a28e9954e7ce4b8055bf83f922c98f0582f92a07e31c2e","2026-07-09T19:00:43.643Z",null,{"alerts":22},[23,31,39,46,53,60,68,75,82,89,96,103,110,117],{"id":24,"severity":25,"title":26,"summary":27,"contentHash":28,"detectedAt":29,"slug":30},"01KWAJYMBHC8Y288EK9A1824GW","Informational","API documentation clarifications for user management endpoints","Three MongoDB Atlas API endpoint descriptions have been updated to clarify behavior around expired\u002Frejected user invitations: `POST \u002Fapi\u002Fatlas\u002Fv2\u002Fgroups\u002F{groupId}\u002Fusers` (add group users), `POST \u002Fapi\u002Fatlas\u002Fv2\u002Forgs\u002F{orgId}\u002Fteams\u002F{teamId}:addUser` (add team user), and `POST \u002Fapi\u002Fatlas\u002Fv2\u002Forgs\u002F{orgId}\u002Fusers` (create org user). The changes document how the API handles replacing users with expired or rejected invitations, with specifics on conflict detection and re-invitation requirements.","bbdde4df9aaf7d8be28a490d78d91a1f3f15467cb5fc180138230c26db5fe1f9","2026-06-29T21:00:50.417Z","2026-06-29-api-documentation-clarifications-for-user-management",{"id":32,"severity":33,"title":34,"summary":35,"contentHash":36,"detectedAt":37,"slug":38},"01KVY4P881CSZ42T7RVNMJZ41W","Additive","Add OAuth audit event types to event type enums","The MongoDB Atlas Admin API now includes 11 new OAuth-related audit event types in the event type enumerations: `OAUTH_CLIENT_CREATED`, `OAUTH_CLIENT_UPDATED`, `OAUTH_CLIENT_DELETED`, `OAUTH_CLIENT_SECRET_CREATED`, `OAUTH_CLIENT_SECRET_DELETED`, `OAUTH_AUTHORIZATION_GRANTED`, `OAUTH_AUTHORIZATION_DENIED`, `OAUTH_TOKEN_ISSUED`, `OAUTH_TOKEN_REVOKED`, `OAUTH_USER_CONSENT_GRANTED`, and `OAUTH_USER_CONSENT_REVOKED`. These are additive enum values that extend the existing event type definitions without removing or breaking existing event types.","f063cda4de57dde6043728c8e0427b4a8c6e0662023b7d65e6a8ba3559d885b0","2026-06-25T01:00:42.625Z","2026-06-25-add-oauth-audit-event-types-to-event-type-enums",{"id":40,"severity":33,"title":41,"summary":42,"contentHash":43,"detectedAt":44,"slug":45},"01KVR10BWTA237V0H1KPDXKCVB","New stream processor failover configuration and endpoints","MongoDB Atlas added new failover-related fields and endpoints to the Streams API. **New fields**: `failoverEnabled` (request\u002Fresponse), `eligibleForFailover` (response), and `failoverRegions` (response) added to stream processor and workspace schemas; **New region**: `SEOUL_KOR` added as supported region enum; **New endpoints**: `GET` and `PATCH` operations added to manage failover connections at `\u002Fapi\u002Fatlas\u002Fv2\u002Fgroups\u002F{groupId}\u002Fstreams\u002F{tenantName}\u002Fconnections\u002F{connectionName}\u002FfailoverConnections\u002F{failoverConnectionId}`. These are entirely additive and will not break existing clients.","d4542d8a2d26e2a4742b1b1fdd42c03e6d5f3135f0c0aa0e9020076477ab2779","2026-06-22T16:00:53.146Z","2026-06-22-new-stream-processor-failover-configuration-and-endpoints",{"id":47,"severity":33,"title":48,"summary":49,"contentHash":50,"detectedAt":51,"slug":52},"01KVDQDRJJJ3RHH0HFKNMBGTAQ","Add external documentation link to maintenance window defer endpoint","The POST `\u002Fapi\u002Fatlas\u002Fv2\u002Fgroups\u002F{groupId}\u002FmaintenanceWindow\u002Fdefer` endpoint's description was enhanced with clarification about deferral time windows, and a new `externalDocs` field was added linking to MongoDB's official documentation on responding to maintenance. This is purely additive—the API behavior and request\u002Fresponse shapes remain unchanged.","50aaa02a381539248ad624c55bd2d52784f42a42160f4cd012bf180ef1d47dce","2026-06-18T16:01:02.034Z","2026-06-18-add-external-documentation-link-to-maintenance-window-defer",{"id":54,"severity":33,"title":55,"summary":56,"contentHash":57,"detectedAt":58,"slug":59},"01KVBBXG2K8KHZ6049SM4XKW6W","Add Search Deployment and maintenance settings endpoints and schemas","The API adds several new schemas (`AdditionalData`, `ApiSearchDeploymentEffectiveSpecView`) and introduces new optional request\u002Fresponse fields for Search Deployment APIs (`cloudProvider`, `regionName`, `defaultNodeCount`, `effectiveSpecs`). Additionally, two new organization maintenance settings endpoints are added (`GET\u002FPATCH \u002Forgs\u002F{orgId}\u002FmaintenanceSettings`), and the disk warming enum is expanded with a new `ENHANCED_FULLY_WARMED` option. The existing `specs` field in `ApiSearchDeploymentResponseView` is marked deprecated in favor of the new `effectiveSpecs` field.","cef99a7ad70eacd4ea1158ae4f8731ac95fe387430634d711e5844886219e152","2026-06-17T18:01:25.843Z","2026-06-17-add-search-deployment-and-maintenance-settings-endpoints",{"id":61,"severity":62,"title":63,"summary":64,"contentHash":65,"detectedAt":66,"slug":67},"01KV63N942VAPQXB8MXBXB21KY","Breaking","Remove effectiveWaveAssignment and waveAssignment fields from maintenance window","The `effectiveWaveAssignment` (read-only) and `waveAssignment` (writable) fields have been removed from the maintenance window schema. Clients that read `effectiveWaveAssignment` or write `waveAssignment` to control cross-organization maintenance sequencing will break — the writable field removal is especially impactful as there is no longer a documented way to set a manual wave assignment.","3cecfc6e3acc19b93a71d6dd2b350ec62b3f02b47606fce86b94ec6fbeb4d483","2026-06-15T17:00:55.810Z","2026-06-15-remove-effectivewaveassignment-and-waveassignment-fields",{"id":69,"severity":33,"title":70,"summary":71,"contentHash":72,"detectedAt":73,"slug":74},"01KT4H1SZMHEFZQYT2QX4Y34ZV","Add HIGH_PERFORMANCE EBS volume type option","The `volumeType` and `ebsVolumeType` fields now accept a new enum value `HIGH_PERFORMANCE` alongside the existing `STANDARD` and `PROVISIONED` options. The updated documentation clarifies that `HIGH_PERFORMANCE` uses IO2 EBS volumes and that NVMe clusters require either `PROVISIONED` or `HIGH_PERFORMANCE`. This is a purely additive change that allows clients to specify this new storage option while existing integrations continue to work unchanged.","c72fac561ecb4901cfa06d4522b5ce1a2957aa5f480769c7f869a2e13846c7ae","2026-06-02T16:00:47.092Z","2026-06-02-add-high-performance-ebs-volume-type-option",{"id":76,"severity":25,"title":77,"summary":78,"contentHash":79,"detectedAt":80,"slug":81},"01KT2K81DZXB54QY3RHVTCAQKP","Update TLS cipher config field descriptions for clarity","Updated descriptions for `customOpensslCipherConfigTls12` and `customOpensslCipherConfigTls13` fields across multiple schema definitions to clarify that these fields support automatic mode inference when `tlsCipherConfigMode` is omitted. The behavior itself remains unchanged; this is a documentation clarification.","c91345156aa02104ca01be6598009656b73882f00ce722710c5c45ac4a41620d","2026-06-01T22:00:39.615Z","2026-06-01-update-tls-cipher-config-field-descriptions-for-clarity",{"id":83,"severity":62,"title":84,"summary":85,"contentHash":86,"detectedAt":87,"slug":88},"01KT2CCY3DYV10HP0B26NVCC97","Remove CLUSTER_APPLY_CONNECTION_RATE_LIMIT_REQUESTED enum value from audit types","The enum value `CLUSTER_APPLY_CONNECTION_RATE_LIMIT_REQUESTED` has been removed from the **Atlas Audit Types** string enum in two locations in the spec. Any client code that sends or validates this value — e.g. filtering audit events or constructing alert configurations using this event type — will break or fail validation against the updated schema.","391942700dc463f215fb61d64cfc546cb490e35b61fe0ae27f04c4701476576a","2026-06-01T20:01:00.013Z","2026-06-01-remove-cluster-apply-connection-rate-limit-requested-enum",{"id":90,"severity":33,"title":91,"summary":92,"contentHash":93,"detectedAt":94,"slug":95},"01KSQVYKSXMHQY3J87A36B61W4","MongoDB Atlas API: new schemas and audit event types","This update adds three new schemas for cluster configuration validation (`ClusterConfigurationValidation`, `ClusterConfigurationValidationError`, `ClusterConfigurationValidationResult`), enhances existing schemas with descriptions, introduces new audit event types for Charts dashboards and log streaming, and adds a `serviceUnavailable` (503) response component. The changes also replace generic \"This endpoint does not return a response body\" descriptions with clearer \"No Content\" labels on 204 responses, though this is a documentation improvement. All changes are backward-compatible and do not modify existing endpoint signatures or required parameters.","e2cade34f3360fec02ac2fb7adfdfcbb5b798dbc0889b61e4d3f9471e17a9842","2026-05-28T18:01:09.181Z","2026-05-28-mongodb-atlas-api-new-schemas-and-audit-event-types",{"id":97,"severity":62,"title":98,"summary":99,"contentHash":100,"detectedAt":101,"slug":102},"01KSN9HSF033FWGCTAW22SFQVS","Lifecycle Management API endpoints and schemas removed","The entire **Lifecycle Management** tag and all associated endpoints and schemas have been removed from the MongoDB Atlas Admin API spec. This includes the CRUD endpoints under `\u002Fapi\u002Fatlas\u002Fv2\u002Fgroups\u002F{groupId}\u002Fclusters\u002F{clusterName}\u002FlifecycleManagementPolicies` and all related schemas (`ApiCustomCriteria`, `ApiDailySchedule`, `ApiDateCriteria`, `ApiDefaultSchedule`, `ApiLifecycleManagementAction`, `ApiLifecycleManagementCriteria`, `ApiLifecycleManagementPolicyCreateRequest`, `ApiLifecycleManagementPolicyResponse`, `ApiTransitionDataAction`, etc.). Any client integrating with the lifecycle management preview API will break immediately as these endpoints no longer exist in the spec.","b0eb2669acdfaad4986c36633267b85bebfba7b7635d1d0b634fa2e874c8a370","2026-05-27T18:01:05.760Z","2026-05-27-lifecycle-management-api-endpoints-and-schemas-removed",{"id":104,"severity":33,"title":105,"summary":106,"contentHash":107,"detectedAt":108,"slug":109},"01KS65EC8NDAQQSJHPPCMH00JD","New event type enums added to MongoDB Atlas API","Three new event type enum values were added to the MongoDB Atlas Admin API: `PROJECT_COLLECT_DATABASE_STATISTICS_UPDATED`, `SEARCH_HOST_PAUSE_ALL_INITIAL_SYNCS`, and `SEARCH_HOST_DISABLE_FTS`. These are additive changes to response schemas that allow the API to report additional event types without breaking existing integrations that handle unknown values gracefully.","499528d73cdcb3d7247c90a68585b762d4042b21eb8b1583a3196d43ed2cf010","2026-05-21T21:00:43.157Z","2026-05-21-new-event-type-enums-added-to-mongodb-atlas-api",{"id":111,"severity":62,"title":112,"summary":113,"contentHash":114,"detectedAt":115,"slug":116},"01KRY7DEEEA4W8WPFBRK64M49K","DeprecatedStreamProcessorMetricThreshold schema removed, replaced by StreamProcessorMetricThreshold","The `DeprecatedStreamProcessorMetricThreshold` schema has been fully removed from the OpenAPI spec. The `threshold` field in the stream processor alert configuration (previously referencing `DeprecatedStreamProcessorMetricThreshold`) now references `StreamProcessorMetricThreshold` instead. Any clients or generated SDKs that reference the old schema name or depend on its specific shape may break if `StreamProcessorMetricThreshold` has a different structure.","4144b23be46136866209e0811952d59f17156baff10b7c5059c9981757462434","2026-05-18T19:01:14.318Z","2026-05-18-deprecatedstreamprocessormetricthreshold-schema-removed",{"id":118,"severity":33,"title":119,"summary":120,"contentHash":121,"detectedAt":122,"slug":123},"01KREZ0A7KE4EXZHKFKADW3GTY","Add search process throttling event types to Atlas API","Added three new event type enum values to the MongoDB Atlas Admin API: `HOST_SEARCH_PROCESS_THROTTLING`, `HOST_SEARCH_PROCESS_NOT_THROTTLING`, and an additional occurrence of `HOST_SEARCH_PROCESS_THROTTLING`. These new event types expand the set of alert and event states that can be reported by the API without removing or changing existing values, making this a purely additive change that does not affect existing integrations.","0b392e3b042624dab1e747bcb4cd9af10640479808ade11da88f1dddcd4a74aa","2026-05-12T20:45:38.931Z","2026-05-12-01krez0a7ke4exzhkfkadw3gty"]