NocoDB v2
★ Only Publicly Available OpenAPI DocumentStorageDatabaseapiKey143 EndpointsREST
For Agents
Build and operate NocoDB bases — define tables, views, columns, hooks, and filters, run audits, and manage shared apps across 143 endpoints.
Use for: I need to create a new base in NocoDB, List all tables in a NocoDB base, Configure a kanban view on an existing table, Set up a hook that fires when a row is updated
Not supported: Does not handle row-level CRUD on user data tables (covered by NocoDB's data API) or hosting infrastructure — use for NocoDB metadata, view, hook, and audit operations only.
NocoDB v2 is the API surface of the open-source no-code database that turns relational data sources into spreadsheet-style bases, tables, views, and shared apps. The 143-endpoint catalog covers base and source management, table and column definition, grid/form/gallery/kanban/map view configuration, hooks, filters, comments, audits, plugins, and shared base/ERD lifecycle. Authentication is by JWT-based xc-auth header for authenticated calls and shared base/ERD ids for read-only public access. The base URL points at a self-hosted NocoDB instance, so deployments substitute their own host (NocoDB Cloud or self-hosted).
Install Jentic One Beta
Connect the NocoDB v2 to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NocoDB v2, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with NocoDB v2 API.
Manage NocoDB bases and connected sources via /api/v2/meta/bases and /api/v2/meta/bases/{baseId}/sources
Define and configure tables, columns, and primary keys through the meta column endpoints
Configure grid, form, gallery, kanban, and map views with their per-column settings
Set up hooks and hook filters to trigger external systems when records change
Manage filters, comments, and row-level audits across bases via /api/v2/meta/audits and related endpoints
Provision base-level API tokens and run plugin tests through /api/v2/meta/plugins
Use Cases
Patterns agents use NocoDB v2 API for, with concrete tasks.
★ Spreadsheet-to-API Workflow
Operations and ops-engineering teams use NocoDB to expose a relational database as a spreadsheet UI plus REST API. The meta endpoints let an automation define new bases, add tables and columns, and configure grid or kanban views without manual clicking. Combined with the row-level CRUD endpoints (handled separately by NocoDB's data API), this turns a NocoDB instance into a programmatic backoffice in minutes.
POST /api/v2/meta/bases to create a base, then add tables via /api/v2/meta/bases/{baseId}/{sourceId}/tables and configure a grid view
Hooks-Driven Integration
Teams wiring NocoDB into downstream systems need event hooks that fire on row create, update, or delete. The /api/v2/meta/hooks/{hookId} and /api/v2/meta/hooks/{hookId}/filters endpoints let an automation register a hook with conditional filters, then inspect /api/v2/meta/hooks/{hookId}/logs to debug delivery. This keeps NocoDB as the system of record while pushing changes to webhooks, queues, or downstream services.
Register a hook on a table via /api/v2/meta/hooks/{hookId}, attach filter rules through /api/v2/meta/hooks/{hookId}/filters, and tail /api/v2/meta/hooks/{hookId}/logs
Compliance and Audit Trail
Compliance teams running NocoDB as a lightweight operational database need a structured audit trail of who changed which row and when. The /api/v2/meta/audits/comments and /api/v2/meta/bases/{baseId}/audits endpoints expose audit entries and per-row comments so a daily export can flow into a SIEM or compliance dashboard. Filters narrow the export to specific bases or time windows.
Call /api/v2/meta/bases/{baseId}/audits with a date range and stream the result into a SIEM ingest endpoint
AI Agent Workspace Builder
An agent provisioning workspaces for new teams can use Jentic to create a NocoDB base, add tables and views, and set up hooks without juggling dozens of meta endpoints by hand. Jentic search routes 'create a nocodb base' to the right operation, loads the schema, and executes with the JWT injected. The same agent can then iterate on column definitions and views.
Use Jentic to call /api/v2/meta/bases to create a base, then /api/v2/meta/bases/{baseId}/{sourceId}/tables to scaffold tables for the new workspace
Key Endpoints
143 endpoints — nocodb v2 is the api surface of the open-source no-code database that turns relational data sources into spreadsheet-style bases, tables, views, and shared apps.
METHOD
PATH
DESCRIPTION
GET
/api/v2/meta/bases
List NocoDB bases
POST
/api/v2/meta/bases
Create a new base
GET
/api/v2/meta/bases/{baseId}/tables
List tables in a base
PATCH
/api/v2/meta/columns/{columnId}
Update a column definition
GET
/api/v2/meta/bases/{baseId}/audits
Retrieve audit entries for a base
PATCH
/api/v2/meta/hooks/{hookId}
Update a hook configuration
GET
/api/v2/meta/hooks/{hookId}/logs
Inspect hook delivery logs
GET
/api/v2/meta/bases/{baseId}/api-tokens
List API tokens scoped to a base
GET
/api/v2/meta/bases
List NocoDB bases
POST
/api/v2/meta/bases
Create a new base
GET
/api/v2/meta/bases/{baseId}/tables
List tables in a base
PATCH
/api/v2/meta/columns/{columnId}
Update a column definition
GET
/api/v2/meta/bases/{baseId}/audits
Retrieve audit entries for a base
PATCH
/api/v2/meta/hooks/{hookId}
Update a hook configuration
GET
/api/v2/meta/hooks/{hookId}/logs
Inspect hook delivery logs
GET
/api/v2/meta/bases/{baseId}/api-tokens
List API tokens scoped to a base
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
NocoDB JWT tokens (xc-auth) and shared base/ERD ids are stored encrypted in the Jentic vault. Agents receive scoped access — the raw JWT never enters the agent context, and rotation is handled at the vault layer.
Intent-based discovery
Agents search by intent (e.g. 'create a nocodb base' or 'register a hook on a table') and Jentic returns the matching operation across the 143-endpoint meta surface with its input schema.
Time to first call
Direct integration: 3-7 days to navigate the meta surface, wire JWT auth, and configure base/source/table/view scaffolding. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using NocoDB v2 API through Jentic.
What authentication does the NocoDB API use?
NocoDB uses an apiKey via the xc-auth header carrying a JWT issued for the logged-in user, with a default 10-hour lifetime governed by NC_JWT_EXPIRES_IN. Shared base and ERD endpoints accept xc-shared-base-id and xc-shared-erd-id for unauthenticated read access. Through Jentic the JWT lives in the vault.
Can I create a new base programmatically with the NocoDB API?
Yes. POST /api/v2/meta/bases creates a base, then /api/v2/meta/bases/{baseId}/sources connects a data source. /api/v2/meta/bases/{baseId}/{sourceId}/tables creates tables under the source.
What are the rate limits for the NocoDB API?
NocoDB is typically self-hosted, so rate limits depend on the deployment (NocoDB Cloud or self-hosted). The OpenAPI spec does not declare hard limits. Jentic handles 429 responses if the deployment enforces them.
How do I configure a hook on a NocoDB table through Jentic?
Run pip install jentic, search Jentic for 'create a nocodb hook', load the /api/v2/meta/hooks/{hookId} operation, configure the hook body and attach filters via /api/v2/meta/hooks/{hookId}/filters, then execute. Jentic injects the xc-auth JWT.
Is NocoDB free to use?
NocoDB is open-source and free to self-host. NocoDB Cloud offers managed pricing tiers — check nocodb.com for current plans. The API surface is identical between self-hosted and Cloud deployments.
Can I export audit logs from NocoDB?
Yes. /api/v2/meta/bases/{baseId}/audits returns base-scoped audit entries and /api/v2/meta/audits/comments exposes row-level comments. Combine with date filters to export a compliance trail.
GET STARTED