canonical: https://jentic.com/apis/tabidoo.cloud/tabidoo-cloud

# Tabidoo API

Tabidoo API v2 provides programmatic access to applications, tables, and records in the Tabidoo cloud database platform. Supports CRUD operations, bulk operations, filtering, sorting, pagination, file management, and user management. The API exposes 23 endpoints secured with bearer authentication.

## For AI agents

Programmatically ping the API, list applications. Covers 23 operations with bearer authentication.

## Scope

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

## Capabilities

- Ping the API
- List applications
- Get application
- Create a record
- Monitor Tabidoo API operational status and events

## Use cases

### CRM Operations

Use the Tabidoo API to perform crm operations programmatically. The API provides 23 endpoints covering core functionality including ping the API, list applications, get application.

Example prompt: Call GET /ping to ping the API

### Automated System Management

Automate system operations by combining multiple Tabidoo API endpoints. Agents can list applications and then get application in a single workflow.

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

### AI Agent Integration via Jentic

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

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/ping` | Ping the API |
| GET | `/apps` | List applications |
| GET | `/apps/{app_id}` | Get application |
| GET | `/apps/{app_id}/tables` | List tables |
| GET | `/apps/{app_id}/tables/{table_id}` | Get table definition |
| POST | `/apps/{app_id}/tables/{table_id}/data` | Create a record |
| GET | `/apps/{app_id}/tables/{table_id}/data` | List records |
| POST | `/apps/{app_id}/tables/{table_id}/data/filter` | Filter records |

## Key resources

- **System** — System health checks
- **Applications** — Application management
- **Tables** — Table schema and metadata
- **Records** — Record CRUD operations
- **Bulk Operations** — Bulk record operations

## 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:** 70 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/tabidoo.cloud/tabidoo-cloud/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 Tabidoo by hand means generating a JWT bearer token in the app settings, sending it on every call, and threading app and table ids through nested data routes yourself. Through Jentic you install once, import Tabidoo from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Tabidoo puts the app id and table id in the URL path (`/apps/{app_id}/tables/{table_id}/...`), so a rule can pin your agent to one table: it can read or add data there and nothing else. You choose the operations it may call, so writes are not included unless you add them.
- **Credential handling:** Your Tabidoo JWT 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 tables in an app' or 'filter table data', and Jentic returns the matching Tabidoo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Tabidoo API use?

The Tabidoo API uses a Bearer token in the Authorization 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 ping the API with the Tabidoo API?

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

### What are the rate limits for the Tabidoo 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 ping the API through Jentic?

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

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

The Tabidoo API exposes 23 endpoints covering system, applications, tables operations.