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.
❗️Save Your API Key ID and secret The secret will not be available after you close this window.
❗️Save your API Key ID & secret The secret will not be available after you close this window.
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}.
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.
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.
Number of deployments per page. The maximum is 100, with the default value is set to maximum
The offset of the first deployment returned. Defaults to 0
The start date of the first deployment log in the response. Must be provided with toDate and in the following format YYYY-MM-DDTHH:mm:ss.sssZ
The start date of the last deployment log in the response. Must be provided with fromDate and in the following format YYYY-MM-DDTHH:mm:ss.sssZ
The types of the deployment logs in the response. The types should be in Camel case and separated by commas. For example: deploymentTypes=deploy,prPlan,driftDetection
The statuses of the deployment logs in the response. The statuses should be separated by commas.
The ids of the users who started the deployments. The ids should be separated by commas.
deploy, destroy, prPlan, driftDetection, task, remotePlan, dryRun, moduleTest, deploy, destroy, prPlan, driftDetection, task, remotePlan, dryRun, moduleTest IN_PROGRESS, WAITING_FOR_USER, TIMEOUT, FAILURE, SUCCESS, CANCELLED, INTERNAL_FAILURE, ABORTING, ABORTED, QUEUED, SKIPPED, NEVER_DEPLOYED, IN_PROGRESS, WAITING_FOR_USER, TIMEOUT, FAILURE, SUCCESS, CANCELLED, INTERNAL_FAILURE, ABORTING, ABORTED, QUEUED, SKIPPED, NEVER_DEPLOYED, IN_PROGRESS, WAITING_FOR_USER, TIMEOUT, FAILURE, SUCCESS, CANCELLED, INTERNAL_FAILURE, ABORTING, ABORTED, QUEUED, SKIPPED, NEVER_DEPLOYED opentofu, terraform, terragrunt, pulumi, k8s, cloudformation, helm, ansible, opentofu, terraform, terragrunt, pulumi, k8s, cloudformation, helm, ansible, opentofu, terraform, terragrunt, pulumi, k8s, cloudformation, helm, ansible, opentofu, terraform, terragrunt, pulumi, k8s, cloudformation, helm, ansible, opentofu, terraform, terragrunt, pulumi, k8s, cloudformation, helm, ansible user, terraform-cli, workflow, user, terraform-cli, workflow, user, terraform-cli, workflow