> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/human-access/connections-and-integrations/integration-guides/incident.io.md).

# incident.io

Sync incident.io users and non-human identities into Cakewalk with an API key, including the read permissions the key needs.

### :arrows\_counterclockwise: Access Sync

Access Sync for incident.io allows you to automatically synchronize user data with Cakewalk, including permission levels and seat assignments.

| **Authentication method**  | API key                                                                            |
| -------------------------- | ---------------------------------------------------------------------------------- |
| **Synced user attributes** | Email, Name and Permissions                                                        |
| **Non-human identities**   | Supported. API keys and alert sources                                              |
| **Required permissions**   | Read access to users. For non-human identities, also to API keys and alert sources |

<details>

<summary><strong>How can I create an incident.io API key?</strong></summary>

Cakewalk reads your incident.io users with an API key. You choose what the key can do when you create it.

1. Sign in to incident.io.
2. Go to **Settings** > **API keys**, or open [app.incident.io/\~/settings/api-keys](https://app.incident.io/~/settings/api-keys) directly.
3. Create a new key and give it a recognizable name.
4. Grant read access to your users. To sync non-human identities as well, also grant read access to API keys and alert sources.
5. Copy the key value. incident.io shows it exactly once.
6. Navigate back to Cakewalk and paste the key into the `API Key` field.

The key keeps working if the person who created it is later deactivated, so the sync does not break when someone leaves.

</details>

#### Learn more

* [incident.io: API reference](https://docs.incident.io/api-reference)

#### Quick Setup

1. Navigate to **App Governance** → **incident.io** → **Users table** → **Sync Users**
2. Enter your incident.io API key
3. Users will sync automatically


---

# 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, and the optional `goal` query parameter:

```
GET https://www.cakewalk.security/docs/human-access/connections-and-integrations/integration-guides/incident.io.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
