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

# Version 2 of the GoFormz Rest API.

Version 2 of the GoFormz Rest API. - OpenAPI Specification. The API exposes 36 endpoints secured with basic authentication.

## For AI agents

Programmatically datasources_post, datasources_get. Covers 36 operations with basic authentication.

## Scope

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

## Capabilities

- DataSources_Post
- DataSources_Get
- DataSources_Patch
- DataSources_Delete
- Monitor Version 2 of the GoFormz Rest API. operational status and events

## Use cases

### Developer Tools Operations

Use the Version 2 of the GoFormz Rest API. to perform developer tools operations programmatically. The API provides 36 endpoints covering core functionality including datasources_post, datasources_get, datasources_get.

Example prompt: Call POST `/v2/datasources` to datasources_post

### Automated DataSources Management

Automate datasources operations by combining multiple Version 2 of the GoFormz Rest API. endpoints. Agents can datasources_get and then datasources_get in a single workflow.

Example prompt: Call GET `/v2/datasources` to datasources_get, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Version 2 of the GoFormz 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 basic tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v2/datasources` | DataSources_Post |
| GET | `/v2/datasources` | DataSources_Get |
| GET | `/v2/datasources/{id}` | DataSources_Get |
| PATCH | `/v2/datasources/{id}` | DataSources_Patch |
| DELETE | `/v2/datasources/{id}` | DataSources_Delete |
| POST | `/v2/datasources/{dataSourceId}/rows` | DataSources_PostRow |
| GET | `/v2/datasources/{dataSourceId}/rows` | DataSources_GetRows |
| POST | `/v2/datasources/{dataSourceId}/rows/batch` | DataSources_PostRows |

## Key resources

- **DataSources** — Operations related to DataSources
- **Exports** — Operations related to Exports
- **Files** — Operations related to Files
- **Formz** — Operations related to Formz
- **Groups** — Operations related to Groups

## 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:** 12 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 65 / 100
  - Developer Experience & Jentic Compatibility: 55 / 100
  - AI-Readiness & Agent Experience: 4 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/version2ofthegoformz/version2ofthegoformz/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 GoFormz REST API by hand means setting up basic HTTP auth against api.goformz.com and coding each data source and row operation yourself. Through Jentic you install once, import the GoFormz REST API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** GoFormz puts the data source id in the URL path (`/v2/datasources/{id}`, `/v2/datasources/{dataSourceId}/rows`), so a rule can pin your agent to one data source. You choose the operations it may call, so destructive ones like deleting a data source are not included unless you add them.
- **Credential handling:** Your GoFormz basic auth credentials 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 a data source' or 'add rows to a data source', and Jentic returns the matching GoFormz 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 Version 2 of the GoFormz Rest API. use?

The Version 2 of the GoFormz Rest API. uses HTTP Basic authentication with username and password. 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 datasources_post with the Version 2 of the GoFormz Rest API.?

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

### What are the rate limits for the Version 2 of the GoFormz 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 datasources_post through Jentic?

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

### How many endpoints does the Version 2 of the GoFormz Rest API. have?

The Version 2 of the GoFormz Rest API. exposes 36 endpoints covering datasources, exports, files operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which GoFormz operations and credentials your agent may use. GoFormz puts the data source id in the URL path (`/v2/datasources/{id}` and `/v2/datasources/{dataSourceId}/rows`), so a rule can pin your agent to a single data source. You pick the operations it may call, so a destructive endpoint like DELETE `/v2/datasources/{id}` is off limits unless you explicitly add it.