> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/integrations/overview/opsgenie-integration.md).
# OpsGenie Integration
The OpsGenie integration allows Sprinto to automatically fetch and monitor incidents from your OpsGenie account. This helps track incident response processes, validate compliance controls, and maintain audit-ready evidence without manual effort.
***
### Prerequisites
Before you begin, ensure the following:
* You have an active OpsGenie account.
* You have **admin access** to OpsGenie.
* You have access to generate an **OpsGenie API key**.
* The API key has **read access to incidents**.
* You know your OpsGenie **region**:
* US (Default).
* EU.
***
### Permissions and access
#### Minimum requirements
* API key with **read access to incidents**.
* No specific role is required, but access must allow:
* Viewing incidents.
* Viewing incident details.
#### Data accessed by Sprinto
* Message.
* Status.
* Priority.
* Description.
* Impact start date.
* Impact end date.
***
### Data sync behaviour
Sprinto follows a structured sync process:
1. **Fetch** – Retrieves incidents from OpsGenie API.
2. **Transform** – Maps data to Sprinto’s schema.
3. **Store** – Updates the database using bulk operations.
4. **Evaluate** – Triggers monitors and compliance checks.
This ensures consistent and reliable incident tracking.
***
### How it works
Sprinto connects to OpsGenie using API key-based authentication and periodically syncs incident data.
* Sprinto authenticates using **Basic Authentication (Base64 encoded API key)**.
* It fetches incident data using OpsGenie APIs.
* Retrieved data is transformed and mapped to Sprinto’s internal compliance model.
* Incidents are continuously synced and updated.
#### APIs used by Sprinto
* `GET /v1/incidents` – Fetch all incidents.
#### Priority mapping
* P1, P2 → High.
* P3 → Medium.
* P4 → Low.
***
### Connect OpsGenie to Sprinto
1. Log in to the Sprinto dashboard.
2. Navigate to **Settings → Integrations**.
3. In the **All** tab, search for **OpsGenie**.
4. Click **Connect**.
#### Step 1: Review permissions
* Review:
* Required permissions.
* Data accessed by Sprinto.
* Click **Next**.
#### Step 2: Add connection details
1. Enter the following details:
* **API Key**.
* **Region** (US or EU).
2. Click **Connect**.
Once completed, Sprinto validates the connection and establishes the integration.
***
### How to get your API key
1. Log in to your OpsGenie console.
2. Go to the **Admin** section.
3. Navigate to **Settings → API Key Management**.
4. Generate a new API key.
5. Copy and securely store the API key.
Ensure the API key has **read access to incidents**.
***
### Regional configuration
OpsGenie requires selecting the correct region during setup.
Selecting the wrong region will result in connection failure.
***
### Post-connection flow
After a successful connection:
* The integration status is shown as **Connected**.
* Sprinto starts syncing incidents automatically.
* Relevant controls and checks are activated.
* Incident data is continuously updated and mapped to compliance requirements.
***
### Error handling
Sprinto validates the connection during setup and monitors it continuously.
#### Common error scenarios
**Invalid API key (401).**\
Occurs when the API key is incorrect.\
**Action:** Re-enter the correct API key.
**Insufficient permissions (403).**\
Occurs when the API key lacks required access.\
**Action:** Ensure read access to incidents is enabled.
**Incorrect region.**\
Occurs when the selected region does not match your OpsGenie account.\
**Action:** Select the correct region (US or EU).
**Rate limiting (429) or server errors (5xx).**\
Handled automatically with retries.
***
### Troubleshooting
#### Connection fails
* Ensure the API key is copied correctly without extra spaces.
* Verify the API key is active.
* Confirm the correct region is selected.
#### No incidents are syncing
* Check if incidents exist in OpsGenie.
* Ensure the API key has read permissions.
* Allow time for the initial sync.
#### Integration shows errors
* Reconnect the integration.
* Regenerate the API key if required.
Refer to internal troubleshooting steps for OpsGenie integration:
***
### Additional notes
* Credentials are securely stored (API key is encrypted).
* Sprinto uses a structured sync pipeline to ensure data accuracy.
* Transient errors are automatically retried.
* Authentication and permission errors require manual intervention.
***
### Support
Please contact [Sprinto Support](mailto:www.support@sprinto.com) If you have any queries related to the integration or need any assistance.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.sprinto.com/integrations/overview/opsgenie-integration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.