Reference
Incident.io
Connect Incident.io to Alter Vault for secure API access
Overview
Section titled “Overview”Use Incident.io credentials to make authenticated API calls through Alter Vault without exposing API keys in code.
| Property | Value |
|---|---|
| Provider ID | incident-io |
| Category | Monitoring & Observability |
| Credential Type | Bearer Token |
Step 1: Get Credentials
Section titled “Step 1: Get Credentials”Log in to incident.io
Log in to incident.io at app.incident.io.
Go to Settings → API Keys
Go to Settings → API Keys at app.incident.io/settings/api-keys.
Create an API Key
Click ‘Create API Key’ and configure permissions.
Copy your API key
Copy the generated API key.
Step 2: Add to Alter Vault
Section titled “Step 2: Add to Alter Vault”Open the Developer Portal
Go to portal.alterauth.com and navigate to the application.
Add Incident.io
Go to Managed Secrets > Add Provider > Incident.io.
Enter credentials
Paste your API Key into the credential field.
Save
Click Save. You’ll receive a grant_id to use with the SDK.
Using in Code
Section titled “Using in Code”response = await alter_app.request( HttpMethod.GET, "https://api.incident.io/v2/incidents", grant_id="YOUR_GRANT_ID",)Policy-cataloged operations
Section titled “Policy-cataloged operations”Alter policy rules can target these attested operations and families for operation-level and parameter-aware controls.
| Operation ID | Families | Method | Provider path |
|---|---|---|---|
Incidents V2#Create | send, write | POST | /v2/incidents |
Incidents V2#List | read | GET | /v2/incidents |
Incidents V2#Show | read | GET | /v2/incidents/{id} |
Incidents V2#Edit | write | POST | /v2/incidents/{id}/actions/edit |
Incidents V1#Create | send, write | POST | /v1/incidents |
Incidents V1#List | read | GET | /v1/incidents |
Incidents V1#Show | read | GET | /v1/incidents/{id} |
Actions V2#List | read | GET | /v2/actions |
Actions V2#Show | read | GET | /v2/actions/{id} |
Follow-ups V2#List | read | GET | /v2/follow_ups |
Follow-ups V2#Show | read | GET | /v2/follow_ups/{id} |
Severities V1#List | read | GET | /v1/severities |
Severities V1#Show | read | GET | /v1/severities/{id} |
Severities V1#Create | admin | POST | /v1/severities |
Severities V1#Update | admin | PUT | /v1/severities/{id} |
Severities V1#Delete | admin, delete | DELETE | /v1/severities/{id} |
Incident Roles V2#List | read | GET | /v2/incident_roles |
Incident Roles V2#Show | read | GET | /v2/incident_roles/{id} |
Incident Roles V2#Create | admin | POST | /v2/incident_roles |
Incident Roles V2#Update | admin | PUT | /v2/incident_roles/{id} |
Incident Roles V2#Delete | admin, delete | DELETE | /v2/incident_roles/{id} |
Schedules V2#List | read | GET | /v2/schedules |
Schedules V2#Show | read | GET | /v2/schedules/{id} |
Schedules V2#Create | admin | POST | /v2/schedules |
Schedules V2#Update | admin | PUT | /v2/schedules/{id} |
Schedules V2#Destroy | admin, delete | DELETE | /v2/schedules/{id} |
Escalations V2#CreatePath | admin | POST | /v2/escalation_paths |
Escalations V2#ShowPath | read | GET | /v2/escalation_paths/{id} |
Escalations V2#UpdatePath | admin | PUT | /v2/escalation_paths/{id} |
Escalations V2#DestroyPath | admin, delete | DELETE | /v2/escalation_paths/{id} |
Users V2#List | read | GET | /v2/users |
Users V2#Show | read | GET | /v2/users/{id} |
Alert Events V2#CreateHTTP | write | POST | /v2/alert_events/http/{alert_source_config_id} |