Compose Database-as-a-Service Help and Documentation

Everything you need to know about Compose, Hosted or Enterprise, is here in our help system. Whether you run one database for your businesses' sole application or six different databases to support an entire corporation, we've got the information you need.



This is the older REST API and is now deprecated.

Go to the dedicated for details of the current API which works with all Compose databases with the exception of the MongoDB Classic deployments.

In order to authenticate and use the API, you must first have a Personal Access Token. Personal Access Tokens are static tokens created by you to access Compose via the API. Once tokens are created, they will last forever. When access is no longer required, the token should be deleted.

Create a Personal Access Token

  1. Ensure you are on a paid account plan. API tokens are not available on sandbox accounts.
  2. Log in to your account, and click the "Account" icon on the left menu.
  3. Click the Manage OAuth Tokens link on the right side of the page.

Test your Personal Access Token

curl -H "Authorization: Bearer <Personal Access Token>" -H "Accept-Version: 2014-06" -H "Content-Type: application/json"

Still Need Help?

If this article didn't solve things, summon a human and get some help!

Updated about a year ago


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.