canonical: https://jentic.com/apis/tadabase.io/tadabase

# Tadabase API

Tadabase REST API for viewing tables, fields and manipulating records. Industry standard REST API for no-code database applications. The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically check API status, list all tables. Covers 8 operations with apiKey authentication.

## Scope

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

## Capabilities

- Check API Status
- List All Tables
- Create Record
- Get Record
- Update Record

## Use cases

### Developer Tools Operations

Use the Tadabase API to perform developer tools operations programmatically. The API provides 8 endpoints covering core functionality including check API status, list all tables, list table fields.

Example prompt: Call GET /status to check API status

### Automated Records Management

Automate records operations by combining multiple Tadabase API endpoints. Agents can list all tables and then list table fields in a single workflow.

Example prompt: Call GET /data-tables to list all tables, then verify the result

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/status` | Check API Status |
| GET | `/data-tables` | List All Tables |
| GET | `/data-tables/{tableId}/fields` | List Table Fields |
| POST | `/data-tables/{tableId}/records` | Create Record |
| GET | `/data-tables/{tableId}/records` | List Records |
| GET | `/data-tables/{tableId}/records/{recordId}` | Get Record |
| PUT | `/data-tables/{tableId}/records/{recordId}` | Update Record |
| DELETE | `/data-tables/{tableId}/records/{recordId}` | Delete Record |

## Key resources

- **Records** — Operations related to Records
- **Status** — Operations related to Status
- **Tables** — Operations related to Tables

## 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:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 57 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 67 / 100
- **View full report:** https://jentic.com/apis/tadabase.io/tadabase/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 Tadabase API by hand means sending its TadabaseAuth header on every call and threading table and record ids through nested data-table routes yourself. Through Jentic you install once, import the Tadabase API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Tadabase puts the table id and record id in the URL path (`/data-tables/{tableId}/records/{recordId}`), so a rule can pin your agent to one table's records: it can read them and nothing else. You choose the operations it may call, so updating or deleting a record is not included unless you add it.
- **Credential handling:** Your Tadabase 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 'list records in a table' or 'check API status', and Jentic returns the matching Tadabase 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 Tadabase API use?

The Tadabase API uses an API key passed in the `TadabaseAuth` header. 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 check API status with the Tadabase API?

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

### What are the rate limits for the Tadabase 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 check API status through Jentic?

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

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

The Tadabase API exposes 8 endpoints covering records, status, tables operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Tadabase operations and credentials the agent may use. Since Tadabase puts the table id and record id in the URL path (`/data-tables/{tableId}/records/{recordId}`), a rule can pin the agent to one table's records so it only reads them. You pick the operations it may call, so creating, updating, or deleting a record stays off limits unless you add it.