Manually onboarding individual team members through the Anaconda.com graphical user interface (GUI) can be time consuming. For large teams, Anaconda recommends using API calls for a streamlined process. The Anaconda.com public API provides various calls to enable you to add users to an Anaconda.com organization and change their seat and token permissions. You must be an admin of an Anaconda.com organization with an active paid subscription to use these API calls.

​
Interacting with the API

Anaconda maintains a Jupyter notebook that contains Python functions for interfacing with the API, along with instructions for using the notebook itself:

​
Authenticating to the API

The Anaconda.com public API uses OAuth2 standard authentication (with an organization admin’s Anaconda.com username and password) to generate a User_Token. A User_Token is required to create a service account. Once a service account is created, use its credentials (the returned client_id and client_secret) for authentication in order to generate a ServiceAccount_Token to manage users via the other API calls described below.

​
Creating a service account

Creating a service account allows an admin user to specify credentials for a specific machine or machines (like a build server or other machine for pipeline automation) and manage those machines in a similar capacity to a user. The service account can then allow the other API calls to be made directly to the organization the machine user is a part of. You can create as many service accounts per organization as you need. However, Anaconda recommends limiting the number of service accounts to no more than is absolutely necessary. Restricting the number of service accounts enhances your organizations security posture.
Service account names must be created using lower case letters, numbers, hyphens, or underscores, and cannot contain spaces or special characters.

​
API call

# Replace <ORG_ID> with your organization ID, found in your Anaconda.com organization's URL: anaconda.com/app/organizations/<ORG_ID>/
POST /organizations/<ORG_ID>/service-accounts

{
"name":"<SERVICE_ACCOUNT_NAME>"
}

{
"name": "<SERVICE_ACCOUNT_NAME>",
"client_id": "<GUID>",
"org_id": "<GUID>",
"client_secret": "<SECRET_ID>"
}

​
Get service account ID

This call returns the ID of a previously created service account, but it will not reveal its secret.

​
API call

# Replace <ORG_ID> with your organization ID, found in your Anaconda.com organization's URL: anaconda.com/app/organizations/<ORG_ID>/
GET organizations/<ORG_ID>/service-accounts

{
   "name": "<SERVICE_ACCOUNT_NAME>",
   "client_id": "<GUID>",
   "org_id": "<GUID>",
}

​
Deleting a service account

This call deletes the service account associated with the supplied client_id.

​
API call

# Replace <ORG_ID> with your organization ID, found in your Anaconda.com organization's URL: anaconda.com/app/organizations/<ORG_ID>/
# Replace <CLIENT_ID> with your client_id value
DELETE organizations/<ORG_ID>/service-accounts/<CLIENT_ID>
There’s no request or response information for this call. You will receive a 204 status code if the request is successful.

​
Automated Onboarding of new users

If you are adding users to your organization that do not already have an Anaconda.com account, you can use this call to initiate the automated onboarding process, which will add them to your organization, assign them a seat as a member, and issue them a token for access to the repository. Admins will receive an email that the users have been added to the organization. Users will receive two emails, one welcoming them to the organization, and one containing their private access token, which allows them to use packages from repo.anaconda.cloud. 
{
   "user_emails":"[<[[email protected]](/cdn-cgi/l/email-protection)>, <[[email protected]](/cdn-cgi/l/email-protection)>]"
}

{
   "users_in_onboarding_process": [
      "[[email protected]](/cdn-cgi/l/email-protection)" "[[email protected]](/cdn-cgi/l/email-protection)"
   ],
   "users_unavailable_for_onboarding": [],
   "total_organization_seats": "<TOTAL_SEATS>",
   "available_organization_seats": "<REMAINING_SEATS>"
}
  • If a user has an Anaconda.com account associated with their email address, automated onboarding will fail.
  • If users listed under users_in_onboarding_process have started the onboarding process, any issues that occur during onboarding will not be reflected here. You will know there is an issue if a user did not get added to your organization.
  • If the number of available seats are less than the number of members you are attempting to add to your organization, users will be added until seats are no longer available, and the remaining users are shown in the users_unavailable_for_onboarding list.

​
Adding a user to your organization

This call adds users to the organization. If you do not provide an email address when making this call, the system creates an organization-managed user instead. Organization-managed users are not linked to individual accounts and are intended for programmatic use, allowing tokens to be generated specifically for automated processes or integrations. You can create as many managed users as needed. However, Anaconda recommends limiting the number of managed users to only what is required. Restricting their use enhances the security posture of your organization.
When making requests to create organization-managed users, use the <FIRST_NAME> and <LAST_NAME> fields to provide a descriptive name for the token’s intended purpose. For example, if you are providing a token to a Jupyter Notebooks server, you might enter “Jupyter” and “Server-1” as a first and last name for the organization-managed user.

​
API call

# Replace <ORG_ID> with your organization ID, found in your Anaconda.com organization's URL: anaconda.com/app/organizations/<ORG_ID>/
POST /organizations/<ORG_ID>/users

{
   "email":"<EMAIL_ADDRESS>"
   "first_name": "<FIRST_NAME>",
   "last_name": "<LAST_NAME>"
}

{
   "first_name": "<FIRST_NAME>",
   "last_name": "<LAST_NAME>",
   "email": "<EMAIL_ADDRESS>",
   "id": "<GUID>"
}
If you do not provide a first and last name for your user, the API call will return null. The user can edit this information from their profile later, if necessary.

​
Assign seat to user

This call assigns a seat to a given user for the organization the user is a member of.

​
API call

# Replace <ORG_ID> with your organization ID, found in your Anaconda.com organization's URL: anaconda.com/app/organizations/<ORG_ID>/
# Replace <USER_ID> with the ID of the user you want to assign a seat
POST  /organizations/<ORG_ID>/users/<USER_ID>/seats
There’s no request or response information for this call. You will receive a 201 status code if the request is successful.

​
Assign token to user

This call assigns a token to a given user. Tokens are a unique security key that enable users to access the subscription seat they have been assigned.

​
API call

# Replace <ORG_ID> with your organization ID, found in your Anaconda.com organization's URL: anaconda.com/app/organizations/<ORG_ID>/
# Replace <USER_ID> with the ID of the user you want to assign a token
POST /organizations/<ORG_ID>/users/<USER_ID>/token

{
   "expires_at": "<DATETIME>"
}

{
   "token": "<TOKEN>",
   "expires_at": null
}

​
Syncing user tokens

Renewing your subscription does not extend the lifespan of your token. If you have renewed your subscription and want to retain your current token, run this call to synchronize your token and extend its lifespan to your organization’s new subscription expiration date. 
# Replace <ORG_ID> with your organization ID, found in your Anaconda.com organization's URL: anaconda.com/app/organizations/<ORG_ID>/
# Replace <USER_ID> with the ID of the user whose token needs to be synchronized
PATCH /organizations/<ORG_ID>/users/<USER_ID>/token

​
Revoking a users token

This call revokes a token from a given user ID. It should be used when a user no longer needs access to their software subscription and can be used as the first part in a user removal process.

​
API call

# Replace <ORG_ID> with your organization ID, found in your Anaconda.com organization's URL: anaconda.com/app/organizations/<ORG_ID>/
# Replace <USER_ID> with the ID of the user whose token you want to delete
DELETE /organizations/<ORG_ID>/users/<USER_ID>/token

​
Remove seat from user

This call removes a subscription seat from a given user and can be used as the second part in a user removal process.

​
API call

# Replace <ORG_ID> with your organization ID, found in your Anaconda.com organization's URL: anaconda.com/app/organizations/<ORG_ID>/
# Replace <USER_ID> with the ID of the user whose token you want to delete
DELETE /organizations/<ORG_ID>/users/<USER_ID>/seats

​
Remove user from organization

This call removes a given user from a given organization and can be used as the final part in a user removal process.

​
API call

# Replace <ORG_ID> with your organization ID, found in your Anaconda.com organization's URL: anaconda.com/app/organizations/<ORG_ID>/
# Replace <USER_ID> with the ID of the user whose token you want to delete
DELETE /organizations/<ORG_ID>/users/<USER_ID>