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

# Zengine REST API

Zengine is a platform for managing data through workspaces, forms, records, tasks, events, notes, files, and more. The REST API enables integration with other apps such as email systems, marketing automation systems, or EMRs. All API communications require HTTPS. Each access token is allowed 250 queries per 5 minute window. The API exposes 156 endpoints secured with apiKey, oauth2 authentication.

## For AI agents

Programmatically create a user, list users. Covers 156 operations with apiKey, oauth2 authentication.

## Scope

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

## Capabilities

- Create a user
- List users
- Get a user
- Update a user
- Delete a user

## Use cases

### Productivity Operations

Use the Zengine REST API to perform productivity operations programmatically. The API provides 156 endpoints covering core functionality including create a user, list users, get a user.

Example prompt: Call POST /users to create a user

### Automated Users Management

Automate users operations by combining multiple Zengine REST API endpoints. Agents can list users and then get a user in a single workflow.

Example prompt: Call GET /users to list users, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Zengine REST API 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 apiKey, oauth2 tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/users` | Create a user |
| GET | `/users` | List users |
| GET | `/users/{userId}` | Get a user |
| PUT | `/users/{userId}` | Update a user |
| DELETE | `/users/{userId}` | Delete a user |
| GET | `/users/{userId}/authorizations` | List authorized clients |
| GET | `/users/{userId}/authorizations/{authorizationId}` | Get an authorized client |
| DELETE | `/users/{userId}/authorizations/{authorizationId}` | Revoke an authorized client |

## Key resources

- **Users** — Manage user accounts and profiles
- **User Authorizations** — View and revoke authorized clients for a user
- **User Clients** — Manage API clients for a user
- **User Avatar** — Upload and manage user avatar images
- **Workspaces** — Create, update, delete, and list workspaces

## Why Jentic

- **Setup:** Wiring the Zengine REST API by hand means choosing between its OAuth flow and an access_token query key, working through user and authorization paths on api.zenginehq.com/v1, and coding request handling yourself. Through Jentic you install once, import Zengine REST from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The Zengine REST API puts the user and authorization ids in the URL path (`/users/{userId}/authorizations/{authorizationId}`), so a rule can pin your agent to one user. You choose the operations it may call, so deleting a user or revoking an authorization is not included unless you add it.
- **Credential handling:** Your Zengine credential 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 'create a user' or 'list a user's authorizations', and Jentic returns the matching Zengine REST operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Asana** — Alternative productivity API
- **Monday** — Alternative productivity API
- **Clickup** — Complementary productivity API

## FAQ

### What authentication does the Zengine REST API use?

The Zengine REST API uses apiKey, oauth2 authentication. 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 create a user with the Zengine REST API?

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

### What are the rate limits for the Zengine REST API?

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 create a user through Jentic?

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

### How many endpoints does the Zengine REST API have?

The Zengine REST API exposes 156 endpoints covering users, user authorizations, user clients operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Zengine REST operations and credentials the agent can use, so you can grant read calls like GET /users and GET `/users/{userId}/authorizations` while withholding destructive ones such as DELETE `/users/{userId}` or revoking an authorization. Since Zengine puts the user and authorization ids in the URL path (`/users/{userId}/authorizations/{authorizationId}`), a rule can also pin the agent to a single user. Nothing outside the operations you explicitly allow is callable, and the stored credential is injected only for those calls.