# Custom HTTPS Endpoints (EOL) > Source-anchored research for Custom HTTPS Endpoints (EOL). Run status: COMPLETED. Parent: [MongoDB Atlas App Services](https://llms-explorer.com/tree/mongodb-atlas-app-services/) · 4 facets · 14 facts · page: https://llms-explorer.com/tree/custom-https-endpoints-eol/ ## Structure and components - RESTHeart's maintainer presents it as an alternative HTTP service over MongoDB, with authentication, authorization and plugins for custom logic. This supplies an alternative execution layer, but the article does not establish automatic compatibility with arbitrary App Services function code. (low confidence) — [source](https://softinstigate.com/en/blog/posts/mongodb-deprecates-data-api/) - A migration can keep MongoDB Atlas as the database while replacing the retired HTTP layer: AWS demonstrates this architecture, and RESTHeart's maintainer describes an API service over MongoDB. Endpoint EOL therefore does not itself require moving the stored database to another engine. (high confidence) — [source](https://aws.amazon.com/blogs/big-data/integrating-the-mongodb-cloud-with-amazon-kinesis-data-firehose/) - Migration should explicitly inventory route/method bindings, validation secrets and response serialization before implementing a replacement. This is an engineering inference from the historical endpoint schema and AWS's example, which implements authorization and ingestion as separate components. (medium confidence) — [source](https://www.mongodb.com/docs/api/doc/atlas-app-services-admin-api-v3/operation/operation-admingetendpoint) ## Problems, failure modes and limitations - MongoDB deprecated HTTPS Endpoints in September 2024 and scheduled their removal for September 30, 2025; its retained Admin API notice states that HTTPS Endpoints reached EOL on that date. (high confidence) — [source](https://www.mongodb.com/docs/api/doc/atlas-app-services-admin-api-v3) ## Comparisons and alternatives - The historical endpoint configuration accepted GET, POST, PUT, PATCH, DELETE or the wildcard *. A migration inventory should preserve each route's configured method rather than assume every endpoint was POST-only. (low confidence) — [source](https://www.mongodb.com/docs/api/doc/atlas-app-services-admin-api-v3/operation/operation-admingetendpoint) - A retained Get an endpoint reference is marked Deprecated. Its presence should be treated as migration documentation rather than evidence that custom HTTPS endpoint execution remains supported after EOL. (high confidence) — [source](https://www.mongodb.com/docs/api/doc/atlas-app-services-admin-api-v3) ## Facts and statements - Historically, a custom endpoint configuration bound a route and HTTP method to a function_id. The documented method choices were GET, POST, PUT, PATCH, DELETE, or the wildcard *. (high confidence) — [source](https://www.mongodb.com/docs/api/doc/atlas-app-services-admin-api-v3/operation/operation-admingetendpoint) - MongoDB's current Admin API notice states that HTTPS Endpoints reached end of life on September 30, 2025. SoftInstigate's earlier announcement identified the same removal date. The retained endpoint reference should not be interpreted as proof of continued service availability. (high confidence) (verified as of 2026-10-23) — [source](https://www.mongodb.com/docs/api/doc/atlas-app-services-admin-api-v3) - Historical endpoint validation modes were NO_VALIDATION, SECRET_AS_QUERY_PARAM and VERIFY_PAYLOAD. The latter two referred to a secret_id; return_type selected JSON or EJSON. These fields identify request-validation and serialization behavior to reproduce in a replacement. (low confidence) — [source](https://www.mongodb.com/docs/api/doc/atlas-app-services-admin-api-v3/operation/operation-admingetendpoint) - AWS's September 2025 revision describes replacing MongoDB HTTPS endpoints with Amazon API Gateway and AWS Lambda while continuing to write to MongoDB Atlas. In that Firehose-specific example, a custom Lambda authorizer validates incoming requests before an ingestion Lambda decodes and writes their data. (low confidence) — [source](https://aws.amazon.com/blogs/big-data/integrating-the-mongodb-cloud-with-amazon-kinesis-data-firehose/) - MetaDesign's January 15, 2025 guide recommends recreating HTTPS endpoints with Atlas Functions as a direct replacement. This conflicts with MongoDB's later notice that HTTPS Endpoints themselves reached EOL; treat that recommendation as unsuitable evidence of a supported post-EOL HTTP deployment path. (medium confidence) — [source](https://metadesignsolutions.com/migrating-from-atlas-data-api-and-custom-https-endpoints-previously-realm-what-are-your-options/) - The historical endpoint schema supported NO_VALIDATION, SECRET_AS_QUERY_PARAM and VERIFY_PAYLOAD. In either secret-based mode, secret_id identified the secret authorizing requests. (low confidence) — [source](https://www.mongodb.com/docs/api/doc/atlas-app-services-admin-api-v3/operation/operation-admingetendpoint) - The historical return_type field selected JSON or EJSON; configuration also exposed respond_result, disabled, fetch_custom_user_data and create_user_on_auth. (low confidence) — [source](https://www.mongodb.com/docs/api/doc/atlas-app-services-admin-api-v3/operation/operation-admingetendpoint) - Supabase's March 20, 2025 migration guide acknowledges HTTPS Endpoints EOL, but its worked migration exports MongoDB data into PostgreSQL and changes calls to generated PostgREST APIs. Inference: its near-drop-in marketing claim for a generated CRUD interface does not demonstrate compatibility with arbitrary custom endpoint functions. (medium confidence) — [source](https://supabase.com/blog/migrating-mongodb-data-api-with-supabase)