Atlas Data API (EOL)
Parent: MongoDB Atlas App Services · Published reference · snapshot 2026-10-23 · viability 3.40 / 5 (research)
↓ Facts as markdownall context files
Source-anchored research for Atlas Data API (EOL). 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.
How it works
- MongoDB's App Services Admin API notice states that database triggers remain available despite Data API EOL. The notice also says the retirement affects authentication, user management, functions, Wire Protocol, and data access permissions; it does not support treating every App Services capability as unaffected. (low confidence) (verified as of 2025-09-23) [source]
- The Data API EOL should not be generalized to every App Services capability: MongoDB's EOL notice explicitly says database triggers remain available. (low confidence) (verified as of 2026-10-23) [source]
Problems, failure modes and limitations
- Retained Data API configuration endpoints in the App Services Admin API are explicitly marked deprecated. Their continued appearance in an API reference does not establish that an application can enable or use Data API after EOL. (medium confidence) [source]
- The surviving Data API v1 reference still describes setup and authentication, but labels the API deprecated and gives June 12, 2025 as its last update. Read alongside MongoDB's explicit EOL notice, these instructions do not establish present service availability. (high confidence) (verified as of 2026-10-23) [source]
Comparisons and alternatives
- Atlas Data API reached end of life on September 30, 2025; it is a retired dependency rather than a service with a future deprecation deadline. MongoDB states the EOL date, and RESTHeart independently markets migration from the removed service. (high confidence) [source]
- FerretDB's documented Data API is integrated into FerretDB, a PostgreSQL-backed MongoDB-compatible database. It is a route to a different database architecture, rather than merely adding an HTTP proxy in front of an existing Atlas cluster. (high confidence) [source]
- FerretDB v2.7 documents its Data API as an integrated FerretDB feature rather than a standalone service. It exposes HTTP MongoDB-compatible operations and is enabled with FERRETDB_LISTEN_DATA_API_ADDR or --listen-data-api-addr. Its examples use /action/findOne and HTTP Basic credentials. (low confidence) (verified as of 2026-02-07) [source]
Facts and statements
- The former Data API exposed application-data reads, writes, and aggregations through HTTP. Its retained v1 specification lists find, insert, update, delete, and aggregate actions; it was powered by Atlas Functions and used application authentication and role-based permissions. (high confidence) [source]
- The former global v1 base URL was https://data.mongodb-api.com/app/{ClientAppID}/endpoint/data/v1. The administrative reference also documents regional base URLs for locally deployed apps. These are historical identification patterns for dependency inventories. (high confidence) [source]
- MongoDB distinguishes the App Services Admin API, which configures and deploys applications, from the app-specific HTTPS APIs used by client applications. Treating the old Data API base URL as an administrative API confuses these two roles. (medium confidence) [source]
- In its February 28, 2025 walkthrough, FerretDB demonstrates insert, find, update, and delete over action endpoints. Its documentation also shows those actions using HTTP Basic credentials and an explicitly enabled Data API listener, so migration includes endpoint and authentication configuration. (medium confidence) [source]
- Modelence's August 13, 2026 migration guide describes configuring a MongoDB URI and a Data API key, exchanging the key at /auth/providers/api-key/login, and sending the returned bearer token to /data/v1/action/insertOne. This is the provider's documented workflow, not a tested assertion of complete Atlas compatibility. (low confidence) (verified as of 2026-08-13) [source]
- RESTHeart markets an Atlas Data API-compatible migration service. Its landing page establishes that the provider offers this route, but does not document an exhaustive compatibility matrix or prove that changing only the hostname preserves all application behavior. (low confidence) (verified as of 2026-05-14) [source]
- Historically, Atlas Data API exposed document reads, writes, and aggregation through app-specific HTTPS endpoints. The App Services Admin API instead configured applications and their API surfaces; it was not the client application's document-operation interface. (high confidence) [source]
- Migration review should cover authentication and data-access permissions as well as endpoint URLs. The historical Data API depended on App Services authentication and role-based permissions, and MongoDB's EOL notice explicitly lists authentication, user management, and data-access permissions among impacted capabilities. (high confidence) [source]
- Do not assume that an HTTP replacement preserves the original authentication contract: MongoDB's historical reference describes App Services login credentials or session access tokens, whereas FerretDB's v2.7 request examples use Basic authentication. Validate credentials and authorization during migration. (medium confidence) [source]
Children
- No children recorded.