canonical: https://jentic.com/apis/zenduty.com/zenduty

# Zenduty

Introduction Zenduty is a cutting edge platform for incident management. With high level automation, Zenduty enables faster and better incident resolution keeping developers first. Javascript Libraries: https://github.com/Zenduty/zenduty-js Ruby Libraries: https://github.com/Zenduty/zenduty-ruby Python Libraries: https://github.com/Zenduty/zenduty-python-sdk Postman Collection for Zenduty API: htt. The API exposes 140 endpoints secured with bearer authentication.

## For AI agents

Programmatically invite user, list all account member objects. Covers 140 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for security only.

## Capabilities

- Invite User
- List all Account Member objects
- Retrieve the Account Member object
- Update the Account Member object
- Delete User
- Create the Account Custom Role object

## Use cases

### Security Operations

Use the Zenduty to perform security operations programmatically. The API provides 140 endpoints covering core functionality including invite user, list all account member objects, retrieve the account member object.

Example prompt: Call POST `/api/account/api_invite`/ to invite user

### Automated Account Member Management

Automate account member operations by combining multiple Zenduty endpoints. Agents can list all account member objects and then retrieve the account member object in a single workflow.

Example prompt: Call GET `/api/account/members`/ to list all account member objects, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Zenduty endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'invite user', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/account/api_invite/` | Invite User |
| GET | `/api/account/members/` | List all Account Member objects |
| GET | `/api/account/members/{username}/` | Retrieve the Account Member object |
| PUT | `/api/account/members/{username}/` | Update the Account Member object |
| POST | `/api/account/deleteuser/` | Delete User |
| POST | `/api/account/customroles/` | Create the Account Custom Role object |
| GET | `/api/account/customroles/` | List all Account Custom Role objects |
| GET | `/api/account/customroles/{custom_role_id}/` | Retrieve the Account Custom Role object |

## Key resources

- **Account Member** — This object represents a user of the account. Each account member object has a role, which can be ow
- **Account Custom Role** — This object represents a custom role of the account. Each custom role object has custom permissions,
- **User Custom Role** — This object represents a user's custom role. Each user can be assigned to only one custom role.
- **Notification Rules** — This object represents a user's notification rules. A user can have notification rules for high urge
- **Forwarding Rules** — This object represents a user's forwarding rules. A user can forward his notifications to the other

## Why Jentic

- **Setup:** Wiring Zenduty by hand means carrying its bearer token on every request, working through account, member, and role paths on www.zenduty.com, and coding the request handling yourself. Through Jentic you install once, import Zenduty from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Zenduty puts the member and role ids in the URL path (`/account/members/{username}`/ and `/account/customroles/{custom_role_id}`/), so a rule can pin your agent to one member or custom role. You choose the operations it may call, so member invites and user deletion are not included unless you add them.
- **Credential handling:** Your Zenduty token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list account members' or 'read a custom role', and Jentic returns the matching Zenduty operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Snyk** — Alternative security API
- **Crowdstrike** — Alternative security API

## FAQ

### What authentication does the Zenduty use?

The Zenduty uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I invite user with the Zenduty?

Yes. Use the POST `/api/account/api_invite`/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Zenduty?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I invite user through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'invite user'. Jentic returns the matching Zenduty operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Zenduty have?

The Zenduty exposes 140 endpoints covering account member, account custom role, user custom role operations.

### Can I limit what my agent is allowed to do with the Zenduty API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Zenduty operations and credentials the agent may use. Because Zenduty puts member and role ids in the URL path, such as `/account/members/{username}`/ and `/account/customroles/{custom_role_id}`/, you can pin the agent to a single member or custom role. You also choose which operations it may call, so sensitive actions like inviting members or deleting users are excluded unless you explicitly allow them.