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

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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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

GET STARTED

Start building with Zenduty API

Explore with Jentic

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Zenduty bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'invite user') and Jentic returns the matching Zenduty operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Zenduty integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Snyk

Alternative security API

Choose Snyk when you need a different approach to security operations

Alternative

Crowdstrike

Alternative security API

Choose Crowdstrike when you need a different approach to security operations

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.