> For the complete documentation index, see [llms.txt](https://docs.apono.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apono.io/docs/additional-integrations/incident-response-integrations/zenduty.md).

# Zenduty

Zenduty provides end-to-end incident alerting and resolution for site reliability engineering (SRE), DevOps, and ITOps teams.

With this integration, you can manage access to Zenduty for creating incident alerts and response workflows based on Zenduty shifts:

* Create access policies that are synced with ZenDuty on-call rotations
* Set grantees to be requesters who are currently on call
* Allocate the minimum amount of resource permissions needed for resolving incidents with automatic approval
* Require on-call approvers for developers assisting with incident response

***

### Prerequisite

| Item                | Description                                                                                            |
| ------------------- | ------------------------------------------------------------------------------------------------------ |
| **Zenduty API key** | [Key](https://www.zenduty.com/docs/zenduty-api/#generating-the-api-key) for accessing Zenduty REST API |

***

### Integrate with Zenduty

{% hint style="warning" %}
Zenduty limits the `On-call Get` API to **40 calls per minute**. In case Apono exceeds that limit, consider reaching out to Zenduty to raise this [rate limit](https://www.zenduty.com/docs/rate-limits/).
{% endhint %}

Follow these steps to complete the integration:

1. On the [**Catalog**](https://app.apono.io/catalog?search=zenduty) tab, click **Zenduty**. The **Add Integration** page appears.
2. Enter a unique, alphanumeric, user-friendly **Integration Name** for identifying this integration when constructing an Access Flow.
3. Under **Secret Store**, enter your Zenduty **Api Key**.
4. Click **Connect**.

{% hint style="success" %}
Go to the [**Identities**](https://app.apono.io/identities) page to see the most currently synced on-call schedules and members. This integration syncs every few minutes to keep shifts and members current.
{% endhint %}

Now that you have completed this integration, you can [create access flows](/docs/access-flows/access-flows.md) for Zenduty.


---

# 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://docs.apono.io/docs/additional-integrations/incident-response-integrations/zenduty.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.