Get Started with the Atlas Administration API
On this page
- Required for All Resources: Generate an Organization API Key
- Required for Select Resources: API Resource Request Access Lists
- Use API Resources that Require an Access List
- Organization API Access List Entries
- Cloud Backup Restores
- Cloud Backup Snapshots
- Legacy Backups
- Require an API Access List for All Requests
- Procedure
- Grant Programmatic Access to Atlas
- Manage Programmatic Access to an Organization
- Create an API Key in an Organization
- View the Details of an API Key in an Organization
- Change an API Key in an Organization
- Delete an API Key from an Organization
- Manage Programmatic Access to a Project
- Invite an Organization API Key to a Project
- Create an API Key for a Project
- View the Details of an API Key in a Project
- Change an API Key's Roles in a Project
- Edit an API Key's Access List
- Delete an API Key from a Project
Each {atlas-admin-api+} has its own resources and requires initial setup. The Atlas Administration API and the Realm Admin API also use different access keys from the Data API.
To learn more, see APIs.
Required for All Resources: Generate an Organization API Key
To access the Atlas Administration API, Create an API Key in an Organization.
All API keys belong to the organization. You can give an API key access to a project. To add the new API key to a project, Invite an Organization API Key to a Project.
To learn more about managing API keys for your organization or project, see Grant Programmatic Access to Atlas.
Required for Select Resources: API Resource Request Access Lists
Atlas allows your API key to make requests from any address on the internet. Atlas has some exceptions to this rule. These exceptions limit which resources an API key can use without location-based limits defined in an API access list.
To add these location-based limits to your API key, create an API access list. This list limits the internet addresses from which a specific API key can make API requests.
Any API keys with an API access list require all API requests to come from an IP address on that list. Your API access list must include entries for all clients that use the API.
Use API Resources that Require an Access List
The following API resources require an API access list:
Organization API Access List Entries
Create or remove access list entries for an organization API key.
Cloud Backup Restores
- Return a dedicated or serverless cloud backup restore job.
- Return all dedicated or serverless cloud backup restore jobs.
- Restore a dedicated or serverless cloud backup snapshot.
- Cancel the restore of a dedicated or serverless cloud backup snapshot.
Cloud Backup Snapshots
Legacy Backups
- Restore, remove, or change the expiration date of a legacy backup snapshot.
- Clear or update a legacy backup snapshot schedule.
Require an API Access List for All Requests
You can require all API requests from an API key to come from an entry on its API access list. If you require API access lists, API keys can't make any API requests until you define at least one API access list entry.
Procedure
To set your organization to require API access lists for every API key:
Grant Programmatic Access to Atlas
To grant programmatic access to an organization or project using only the API, create an API key.
- API keys have two parts: a Public Key and a Private Key. These two parts serve the same function as a username and a personal API key when you make API requests to Atlas.
- You can't use an API key to log into Atlas through the user interface.
- You must grant roles to API keys as you would for users to ensure the API keys can call API endpoints without errors.
- Each API key belongs to only one organization, but you can grant an API key access to any number of projects in that organization.
Manage Programmatic Access to an Organization
To perform any of the following actions, you must have the
Organization Owner
role.
Create an API Key in an Organization
Enter the API Key Information.
- Enter a Description.
- In the Organization Permissions menu, select the new role or roles for the API key.
View the Details of an API Key in an Organization
View the Access List.
- Click to the right of the API Key.
- Click View Details.
The <Public Key> API Key Details modal displays:
- The obfuscated Private Key
- The date the Key was last used
- The date the Key was created
- The IP addresses from which the Key can access the API
- The projects to which the Key has been granted access
Change an API Key in an Organization
You can change the roles, description, or access list of an API Key in an Organization.
Edit the API Key Information.
On the Add API Key page:
- Modify the Description.
- In the Organization Permissions menu, select the new role or roles for the API key.
Edit the API Access List.
To add an IP address or CIDR block from which you want Atlas to accept API requests for this API Key, click Add Access list Entry and type an IP address.
You can also click Use Current IP Address if the host you are using to access Atlas also will make API requests using this API Key.
- To remove an IP address from the access list, click to the right of the IP address.
- Click Save.
Delete an API Key from an Organization
Manage Programmatic Access to a Project
To perform any of the following actions, you must have the
Project Owner
role.
To make this API request:
- Configure an IP access list.
- Add the IP addresses or CIDR blocks of your client applications to the access list using the console or API. If you host your application on AWS, you can use an AWS security group ID as well.
Changing an API key's access list might impact multiple organizations, projects, or both.
Invite an Organization API Key to a Project
Navigate to the Access Manager page for your project.
- If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
- Select your desired project from the list of projects in the Projects page.
- Click the vertical ellipsis () next to your project name in the upper left corner and select Project Settings.
- Click Access Manager in the navigation bar, then click your project.
Add the API Key to the project.
- Click Invite to Project.
- Type the public key into the field.
- In the Project Permissions menu, select the new role or roles for the API key.
Create an API Key for a Project
Navigate to the Access Manager page for your project.
- If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
- Select your desired project from the list of projects in the Projects page.
- Click the vertical ellipsis () next to your project name in the upper left corner and select Project Settings.
- Click Access Manager in the navigation bar, then click your project.
Enter the API Key Information.
On the Create API Key page:
- Enter a Description.
- In the Project Permissions menu, select the new role or roles for the API key.
View the Details of an API Key in a Project
Navigate to the Access Manager page for your project.
- If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
- Select your desired project from the list of projects in the Projects page.
- Click the vertical ellipsis () next to your project name in the upper left corner and select Project Settings.
- Click Access Manager in the navigation bar, then click your project.
View the Access List.
- Click to the right of the API Key.
- Click View Details.
The <Public Key> API Key Details modal displays the following information:
- The obfuscated Private Key
- The date the key was last used
- The date the key was created
- The IP address or addresses from which the API key can access the API
Change an API Key's Roles in a Project
Navigate to the Access Manager page for your project.
- If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
- Select your desired project from the list of projects in the Projects page.
- Click the vertical ellipsis () next to your project name in the upper left corner and select Project Settings.
- Click Access Manager in the navigation bar, then click your project.
Select the new role or roles for the API Key from the Project Permissions menu.
Edit an API Key's Access List
Navigate to the Access Manager page for your project.
- If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
- Select your desired project from the list of projects in the Projects page.
- Click the vertical ellipsis () next to your project name in the upper left corner and select Project Settings.
- Click Access Manager in the navigation bar, then click your project.
Edit the API Access List.
You cannot modify an existing API Key access list entry. You must delete and re-create it.
- Click to the right of the IP address to remove it.
Add the new IP address from which you want Atlas to accept API requests for this API Key. Use one of the two options:
- Click Add access list Entry and type an IP address, or
- Click Use Current IP Address if the host you are using to access Atlas will also make API requests using this API Key.
- Click Save.
Delete an API Key from a Project
Navigate to the Access Manager page for your project.
- If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
- Select your desired project from the list of projects in the Projects page.
- Click the vertical ellipsis () next to your project name in the upper left corner and select Project Settings.
- Click Access Manager in the navigation bar, then click your project.