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

# Qntrl API

Qntrl (by Zoho) process orchestration API for managing organizations, forms, custom fields, blueprints, stages, cards/jobs, custom views, reports, users, profiles, roles, webhooks, business rules, and more. The API exposes 36 endpoints.

## For AI agents

Programmatically create organization, list organizations. Covers 36 operations.

## Scope

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

## Capabilities

- Create organization
- List organizations
- Get organization
- Update form
- Access Qntrl API developer tools resources via REST API

## Use cases

### Developer Tools Operations

Use the Qntrl API to perform developer tools operations programmatically. The API provides 36 endpoints covering core functionality including create organization, list organizations, get organization.

Example prompt: Call POST /org to create organization

### Automated Blueprints Management

Automate blueprints operations by combining multiple Qntrl API endpoints. Agents can list organizations and then get organization in a single workflow.

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

### AI Agent Integration via Jentic

AI agents discover and call Qntrl 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 none tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/org` | Create organization |
| GET | `/org` | List organizations |
| GET | `/org/{id}` | Get organization |
| POST | `/layout` | Create form |
| GET | `/layout` | List forms |
| GET | `/layout/{id}` | Get form |
| PUT | `/layout/{id}` | Update form |
| DELETE | `/layout/{id}` | Delete form |

## Key resources

- **Blueprints** — Operations related to Blueprints
- **Cards** — Operations related to Cards
- **Custom Fields** — Operations related to Custom Fields
- **Forms** — Operations related to Forms
- **Organization** — Operations related to Organization

## Why Jentic

- **Setup:** Wiring Qntrl by hand means pointing at the coreapi.qntrl.com/blueprint/api host, shaping each blueprint request, and handling its responses yourself. Through Jentic you install once, import the Qntrl API from the API Directory, and your agent calls it.
- **Permission scoping:** Qntrl puts the layout and org id in the URL path (`/layout/{id}`, `/org/{id}`), so a rule can pin your agent to one layout or organization: it can read and update that record and nothing else. You choose the operations it may call, so destructive ones like deleting a layout are not included unless you add them.
- **Credential handling:** Any Qntrl connection details are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an organization' or 'update a layout', and Jentic returns the matching Qntrl operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Qntrl API use?

The Qntrl API uses no 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 organization with the Qntrl API?

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

### What are the rate limits for the Qntrl 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 organization through Jentic?

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

### How many endpoints does the Qntrl API have?

The Qntrl API exposes 36 endpoints covering blueprints, cards, custom fields operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Qntrl operations and credentials the agent may use. Because Qntrl puts the layout and organization identifiers in the URL path, such as `/layout/{id}` and `/org/{id}`, you can pin the agent to a single layout or organization and allow it only to read and update that record. You choose the operations it may call, so destructive ones like deleting a layout stay out of reach unless you add them.