Get Ignored Drift Causes
Returns the drift causes that have been marked as ignored for an organization, in the same grouped-by-cause form as GET /drift-causes. Ignoring is recorded per environment, so a cause appears here only for the environments where it was ignored.
Authorization
env0_API_Key env zero 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 env zero 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
env zero 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.
In: header
Query Parameters
The organization id
Optional comma-separated project ids to narrow the results to
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/drift-causes/ignored?organizationId=string"{ "causes": [ { "causeKind": "unmanagedChange", "causeKeyParts": { "resourceType": "string", "strippedPath": "string", "changeType": "modified" }, "causeId": "string", "firstSeenAt": "string", "environments": [ { "id": "string", "name": "string", "projectId": "string", "projectName": "string", "fixedAt": "string", "fixedBy": "string" } ] } ]}Get Drift Fix Stats GET
Returns how long drift causes have been taking to resolve across an organization: the median fix duration in milliseconds, the number of resolved causes the median was computed from, and the trailing window used. The window defaults to 90 days and is capped at 365. `medianFixDurationInMillis` is null when no causes closed within the window.
Ignore Drift Cause POST
Marks a drift cause as ignored on the given environments, so it stops being reported as outstanding. Ignoring applies per environment and does not expire: it does not silence the cause on environments not listed, and the cause returns if a new environment develops it. The response reports which environment ids were ignored and which were skipped, with a reason for each skip.