Zenduty

Name: Zenduty API
Brand: Zenduty
Availability: InStock

✓ Official Vendor SpecSecuritySecrets Managementbearer140 EndpointsREST

For Agents

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

Use for: I need to invite user, I want to all account member objects, Search for the account member object, Find all the account member object

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

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.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the Zenduty to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Zenduty, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzenduty.com%2Fzenduty" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzenduty.com%2Fzenduty" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Zenduty API.

Invite User

List all Account Member objects

Retrieve the Account Member object

Update the Account Member object

Delete User

GET STARTED

Start building with Zenduty API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Zenduty API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

140 endpoints — introduction zenduty is a cutting edge platform for incident management.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Zenduty API through Jentic.

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.

Zenduty

Connect the Zenduty to your agent

Capabilities

Start building with Zenduty API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs