Retrieve workflow file representation by blueprintId or VCS parameters (repositoryUrl, organizationId, path, etc.)
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.
blueprintId to fetch by it the workflow file
VCS Revision
If not by blueprintId, this it the repository url
the user organizationId, if not by blueprintId
the path to workflow, if not by blueprintId
the tokenId to clone the repo, if not by blueprintId
the githubInstallationId to clone the repo, if not by blueprintId
the sshKeys to clone the rep, separated by commas, if not by blueprintId
the bitbucketClientKey to clone the repo, if not by blueprintId
if Github Enterprise set to true, if not by blueprintId
if Gitlab Enterprise set to true, if not by blueprintId
if Bitbucket Server set to true, if not by blueprintId