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

# Zenginehq Zengine API

Zengine (now Submittable) provides a RESTful API for grant management and program administration. Access workspaces, forms, submissions, records, users, webhooks, and more. Rate limit: 250 requests per 5-minute window per access token. The API exposes 17 endpoints secured with apiKey, oauth2 authentication.

## For AI agents

Programmatically create workspace, list workspaces. Covers 17 operations with apiKey, oauth2 authentication.

## Scope

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

## Capabilities

- Create Workspace
- List Workspaces
- Get Workspace
- Update Workspace
- Delete Workspace

## Use cases

### Developer Tools Operations

Use the Zengine API to perform developer tools operations programmatically. The API provides 17 endpoints covering core functionality including create workspace, list workspaces, get workspace.

Example prompt: Call POST /workspaces to create workspace

### Automated Forms Management

Automate forms operations by combining multiple Zengine API endpoints. Agents can list workspaces and then get workspace in a single workflow.

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

### AI Agent Integration via Jentic

AI agents discover and call Zengine 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 workspace', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/workspaces` | Create Workspace |
| GET | `/workspaces` | List Workspaces |
| GET | `/workspaces/{workspaceId}` | Get Workspace |
| PUT | `/workspaces/{workspaceId}` | Update Workspace |
| DELETE | `/workspaces/{workspaceId}` | Delete Workspace |
| POST | `/workspaces/{workspaceId}/forms` | Create Form |
| GET | `/workspaces/{workspaceId}/forms` | List Forms in Workspace |
| GET | `/workspaces/{workspaceId}/forms/{formId}` | Get Form |

## Key resources

- **Forms** — Operations related to Forms
- **Members** — Operations related to Members
- **Records** — Operations related to Records
- **Users** — Operations related to Users
- **Webhooks** — Operations related to Webhooks

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 83 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 53 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/zenginehq.com/zenginehq/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Zengine API by hand means choosing between its OAuth flow and an apiKey query parameter, working through workspace and form paths on api.zenginehq.com/v1, and coding request handling yourself. Through Jentic you install once, import Zengine from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The Zengine API puts the workspace and form ids in the URL path (`/workspaces/{workspaceId}/forms/{formId}`), so a rule can pin your agent to one workspace. You choose the operations it may call, so deleting a workspace 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 workspace' or 'list forms in a workspace', and Jentic returns the matching Zengine 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 Zengine API use?

The Zengine 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 workspace with the Zengine API?

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

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

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

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

The Zengine API exposes 17 endpoints covering forms, members, records operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Zengine operations and credentials the agent may use. Since the API carries workspace and form ids in the URL path, such as `/workspaces/{workspaceId}/forms/{formId}`, you can pin the agent to a single workspace and allow only the calls you choose, for example listing and getting forms while excluding delete workspace. Operations you do not grant, and the stored credential itself, stay out of the agent's reach.