MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Add new feedback Subscribe
Status Will Not Implement
Categories Atlas Backups
Created by Mdrayhan Rayhan
Created on Feb 9, 2026

RELATED FEEDBACK

HTTP/1.1 400 Bad Request Content-Type: application/json Content-Length: 71 { "error": "Bad request", "message": "Request body could not be read properly.", }

What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.


What would you like to see happen?

Describe the desired outcome or enhancement.


Why is this important to you or your team?

Explain how the request adds value or solves a business need.


What steps, if any, are you taking today to manage this problem?



  • Admin
    Kaylee Won
    Feb 23, 2026

    @Guest Thank you for sharing this.

    The 400 Bad Request error indicates that Atlas was unable to parse the request body before processing the operation. This typically occurs when the request payload is malformed, missing required fields, incorrectly encoded, or sent with an incorrect Content-Type header.

    Because this relates to a specific API request and may require reviewing request headers and payload details, this is best handled through our Support team so they can investigate directly with you.

    Could you please open a case via the Atlas Support Portal or start a conversation in the Atlas Support chat? When you do, please include:

    • The full request (headers and body, with sensitive information redacted)

    • The exact endpoint being called

    • The tool being used (e.g., curl, Postman, SDK, Terraform)

    This will allow the team to diagnose the issue more quickly. Thank you!

    Reply