canonical: https://jentic.com/apis/apptivegrid.de/apptivegrid

# Apptivegrid De ApptiveGrid REST API

The ApptiveGrid REST API stores structured records in spaces, grids, and entities, so an application can treat a grid like a flexible table of typed fields and rows. You create spaces and grids, add and update entities, change field types and read a grid's schema, query and export grid views, and build forms that write submissions straight into a grid. It is a HAL-style hypermedia API, so each response lists the operations the caller is allowed on that resource, and it also carries flows and webhooks that react when grid data changes.

## For AI agents

Create grids, read and write their entities and fields, query and export views, and build forms that feed a grid. Authenticates with an HTTP Basic access key or a bearer JWT.

## Scope

Does not run a general SQL database, host arbitrary files, or send email campaigns. Use for managing ApptiveGrid spaces, grids, and their records only.

## Capabilities

- Create spaces and grids to hold structured records
- Add, update, and read entities in a grid
- Add, rename, and retype fields and read a grid's schema
- Query a grid and export a view as CSV
- Build forms on a grid and collect their submissions
- Define flows and webhooks that react to grid changes

## Use cases

### Agent-Managed Structured Data

An AI agent connected through Jentic reads a grid's schema, adds and updates entities, and queries for matching rows, so it can keep a structured table in sync without a human editing it by hand. Because each ApptiveGrid response advertises the operations allowed on that resource, the agent can discover what it may do next rather than guessing.

Example prompt: Read the schema of this grid, then add a row with the given field values and confirm it was written

### Form-to-Grid Intake

A team builds a form on a grid and collects submissions straight into it, so responses land as typed entities ready to query or export. The form and its grid share a schema, which keeps incoming data clean enough to act on without a cleanup step.

Example prompt: Create a form on this grid and return the submitted entries as rows

### Grid Automation and Webhooks

A workflow defines flows and webhooks on a space so that changes to a grid trigger downstream actions, giving an agent an event-driven view of the data instead of polling. The hooks can be tested before they go live, so a setup can be verified end to end.

Example prompt: Register a webhook on this grid that fires when an entity is added, then send a test payload through it

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/users/{userId}/spaces` | List spaces |
| GET | `/api/users/{userId}/spaces/{spaceId}/grids` | List grids in a space |
| POST | `/api/users/{userId}/spaces/{spaceId}/grids/{gridId}/entities` | Add an entity to a grid |
| PUT | `/api/users/{userId}/spaces/{spaceId}/grids/{gridId}/entities/{entityId}` | Update an entity |
| GET | `/api/users/{userId}/spaces/{spaceId}/grids/{gridId}/query` | Query a grid |
| GET | `/api/users/{userId}/spaces/{spaceId}/grids/{gridId}/csv` | Export a grid view as CSV |

## Key resources

- **Spaces** — Top-level containers that hold grids, blocks, forms, and flows
- **Grids** — Tables of typed fields and entities, with views, schema, and CSV export
- **Entities** — The rows of a grid, with add, update, partial-update, and read operations
- **Forms and hooks** — Forms that write submissions into a grid and webhooks that react to changes

## 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:** 54 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 47 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 62 / 100
  - Security: 43 / 100
  - AI Discoverability: 44 / 100
- **View full report:** https://jentic.com/apis/apptivegrid.de/apptivegrid/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 ApptiveGrid REST API by hand means reading its HAL hypermedia responses, choosing between HTTP Basic access keys and bearer JWTs, and threading user, space, and grid ids through deeply nested paths. Through Jentic you install once, import ApptiveGrid from the API Directory, store the access key once, and your agent calls it.
- **Permission scoping:** ApptiveGrid puts the space, grid, and entity ids in the URL path, so a rule can pin your agent to one grid and let it read and add entities while leaving space deletion and schema changes out. You choose the operations it may call, so destructive ones like removing a grid or field are not included unless you add them.
- **Credential handling:** Your ApptiveGrid access key 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 'add a row to a grid' or 'query a grid', and Jentic returns the matching ApptiveGrid operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Airtable API** — Spreadsheet-database hybrid with bases, tables, records, and automations
- **Trello API** — Kanban boards with cards, lists, and power-up automations
- **Asana API** — Work management with tasks, projects, and portfolios

## FAQ

### Is there an ApptiveGrid MCP server?

You don't need an MCP server to give your agent the ApptiveGrid REST API. Jentic connects it directly from the API Directory: import it, store your access key once, and your agent can read and write grid records straight away, with no extra server to run and no tool definitions to load into the agent's context.

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

Yes. Write a rule that allows reading and adding entities in one grid but not removing grids, fields, or spaces, so the agent can maintain records without restructuring your workspace, and every call it makes is logged. Because the grid id is in the URL path, you can bound the agent to a single grid.

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

The ApptiveGrid REST API authenticates with HTTP Basic, using an access key as the username and its secret as the password, or a bearer JWT obtained by signing in, per its OpenAPI spec. Through Jentic the access key is stored encrypted by your own instance and added at call time, so it never appears in the agent's prompt or logs.

### Can I add and update records in a grid with the ApptiveGrid REST API?

Yes. The API adds an entity to a grid, updates or partially updates it, reads it back, and queries a grid for matching records, so an agent can keep a table in sync. Reading the grid's schema first lets the agent build a record whose field values are valid.

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

The OpenAPI spec does not specify rate limits for the ApptiveGrid REST API. For current limits and fair-use guidance, see the ApptiveGrid documentation at https://docs.apptivegrid.de.

### How do I write records into an ApptiveGrid grid through Jentic?

Import the ApptiveGrid REST API from the Jentic API Directory, then have your agent issue a request such as 'add a row to this grid with these values'. Jentic matches the intent to the add-entity operation and returns its input schema so the agent builds the correct request, with your stored access key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.