Authorizations
env0 API authentication is done via API keys. An API Key can either be created by an organization administrator, in which case it will not be connected to any specific user, or via Personal API Keys to authenticate as a user.
Creating an API Key with a Specific Role
-
Once you've created your organization, you can set up and manage API Keys.
-
Navigate to the Organization Settings page and click the API Keys tab.
-
Click Add API Key and enter a name for your key in the Name field. This name is for reference purposes only and isn't used directly in authentication.
❗️Save Your API Key ID and secret The secret will not be available after you close this window.
Creating a Personal API Key
-
Click on your avatar (located on the top right of the screen)
-
Click on Personal Settings
-
Select the API Keys tab
-
Click Add API Key, and enter a name for your key in the Name field. This name is for reference purposes and isn't used directly in authentication.
❗️Save your API Key ID & secret The secret will not be available after you close this window.
Using an API Key to Authenticate
Authentication of the env0 API is done using the Basic Authentication method. Each request made should include the API Key ID as the username, and the API Key secret as the password. For example, when using curl, we can include these parameters via flag --user {API Key ID}:{API Key Secret}.
API Key Permissions
When creating an API key through the organization settings, you will need to choose if you’d like to grant it Organization Admin or User permissions. In case of the latter, you can assign fine-grained permissions per project. Personal API Keys can be created through the user’s profile page and will have the same permissions as the user has.
Rate Limits
env0 API allows up to 1K requests per 60 seconds, requests are aggregated by IP, HTTP Method and URI. If you exceed this limit, you will receive a 429 status code.
Body
1opentofu, terraform, terragrunt, pulumi, k8s, cloudformation, helm, ansible, workflow, module, approval-policy, custom-flow, environment-discovery, discovery-config, opentofu, terraform, terragrunt, pulumi, k8s, cloudformation, helm, ansible, workflow, module, approval-policy, custom-flow, environment-discovery, discovery-config, opentofu, terraform, terragrunt, pulumi, k8s, cloudformation, helm, ansible, workflow, module, approval-policy, custom-flow, environment-discovery, discovery-config, opentofu, terraform, terragrunt, pulumi, k8s, cloudformation, helm, ansible, workflow, module, approval-policy, custom-flow, environment-discovery, discovery-config Manage variables in the environment. Either a single variable or an array of variables.
A string representing semantic version of Terraform. If set to "RESOLVE_FROM_TERRAFORM_CODE", the version will be determined by using tfenv's 'min-required'. When set to "latest", the version used will be the most recent one available for Terraform.
terraform, opentofu, terraform, opentofu, terraform, opentofu Response
CREATED, INACTIVE, ACTIVE, FAILED, TIMEOUT, WAITING_FOR_USER, DEPLOY_IN_PROGRESS, DESTROY_IN_PROGRESS, TASK_IN_PROGRESS, ABORTING, ABORTED, NEVER_DEPLOYED, DRIFTED, DRY_RUN_IN_PROGRESS, CREATED, INACTIVE, ACTIVE, FAILED, TIMEOUT, WAITING_FOR_USER, DEPLOY_IN_PROGRESS, DESTROY_IN_PROGRESS, TASK_IN_PROGRESS, ABORTING, ABORTED, NEVER_DEPLOYED, DRIFTED, DRY_RUN_IN_PROGRESS, CREATED, INACTIVE, ACTIVE, FAILED, TIMEOUT, WAITING_FOR_USER, DEPLOY_IN_PROGRESS, DESTROY_IN_PROGRESS, TASK_IN_PROGRESS, ABORTING, ABORTED, NEVER_DEPLOYED, DRIFTED, DRY_RUN_IN_PROGRESS 0, 1, 2, 3, 0, 1, 2, 3 Mark the environment as inactive
ERROR, DRIFTED, OK, NEVER_RUN, DISABLED, ERROR, DRIFTED, OK, NEVER_RUN, DISABLED, ERROR, DRIFTED, OK, NEVER_RUN, DISABLED