Ninox API

Name: Ninox API
Brand: Ninox API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDatabasebearer9 EndpointsREST

For Agents

Read and write records across Ninox teams, databases, and tables through 9 endpoints under api.ninox.com/v1.

Install Jentic One Beta

Connect the Ninox API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ninox API, 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.

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 | sh

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 instance

Jentic 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 Ninox API.

List the teams accessible to the API key through GET /teams

List databases inside a team through /teams/{teamId}/databases

List tables in a database through /teams/{teamId}/databases/{databaseId}/tables

Page through records in a table through /records

GET STARTED

Start building with Ninox API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Ninox API, keeping it validated and agent-ready. Ninox is a low-code database platform used by small teams to build internal tools, CRMs, and project trackers. The REST API exposes the team-database-table-record hierarchy: list teams, list databases inside a team, list tables in a database, then list, create, read, update, and delete records inside a table. Authentication is a bearer token issued from the Ninox account settings; every call is scoped to the team and database identifiers in the URL path.

Use Cases

Patterns agents use Ninox API for, with concrete tasks.

★ Internal tool back-end CRUD

Teams using Ninox as the back end for an internal tool can read and write records from a custom UI or script. GET /records pages through entries, POST /records inserts a new row with arbitrary fields, PUT /records/{recordId} edits one, and DELETE /records/{recordId} removes one. The team and database IDs in the URL keep operations scoped to the right tenant.

POST /teams/{teamId}/databases/{databaseId}/tables/{tableId}/records with fields {Name: 'Acme', Status: 'Active'} and confirm a 200 response with the new record ID.

Data sync into Ninox

An ETL job can mirror rows from another system into Ninox by creating or updating records on a schedule. The agent lists tables once via GET /tables to confirm the schema, then for each source row issues a POST or PUT against /records depending on whether the target row already exists.

For each source CSV row, PUT /records/{recordId} if the matching ID exists in Ninox, otherwise POST /records to create a new record.

AI agent operating a Ninox-backed app

An AI agent can read and modify Ninox records as part of a workflow — for example, marking a task as done, adding a contact, or attaching a note. Through Jentic, the agent searches for the right Ninox endpoint by intent and Jentic returns the schema. The bearer token is held in the vault and never enters the agent's chat context.

Search Jentic for 'update a ninox record', load PUT /teams/{teamId}/databases/{databaseId}/tables/{tableId}/records/{recordId}, and execute it with fields {Status: 'Done'}.

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for ninox api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/teams

List teams accessible to the token

GET

/teams/{teamId}/databases

List databases inside a team

GET

/teams/{teamId}/databases/{databaseId}/tables

List tables in a database

GET

/teams/{teamId}/databases/{databaseId}/tables/{tableId}/records

List records in a table

POST

/teams/{teamId}/databases/{databaseId}/tables/{tableId}/records

Create a new record

PUT

/teams/{teamId}/databases/{databaseId}/tables/{tableId}/records/{recordId}

Update fields on a record

DELETE

/teams/{teamId}/databases/{databaseId}/tables/{tableId}/records/{recordId}

Delete a record

GET

/teams

List teams accessible to the token

GET

/teams/{teamId}/databases

List databases inside a team

GET

/teams/{teamId}/databases/{databaseId}/tables

List tables in a database

GET

/teams/{teamId}/databases/{databaseId}/tables/{tableId}/records

List records in a table

POST

/teams/{teamId}/databases/{databaseId}/tables/{tableId}/records

Create a new record

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Ninox bearer tokens are stored encrypted in the Jentic vault. Agents call records, tables, and databases via Jentic, which attaches Authorization: Bearer server-side; raw tokens never enter the agent's chat context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'create a record in a Ninox table') and Jentic returns the matching path-parameterised endpoint with its input schema.

Time to first call

Direct Ninox integration: half a day to wire team/database/table/record routes. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Ninox API through Jentic.

Why is there no official OpenAPI spec for Ninox API?

Ninox publishes documentation but does not maintain an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Ninox API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Ninox API use?

Ninox uses HTTP bearer tokens. Issue a token from the Ninox account settings and send it as Authorization: Bearer <token>. Through Jentic, the token is stored encrypted in the vault and never enters the agent's context.

Can I create records in any field schema with the Ninox API?

Yes. POST /teams/{teamId}/databases/{databaseId}/tables/{tableId}/records accepts a fields object whose keys match the Ninox table's field names. The response returns the new record ID and stored values.

What are the rate limits for the Ninox API?

Ninox enforces per-account rate limits but does not publish exact numbers in this OpenAPI spec. Bulk imports should batch writes and back off on HTTP 429 responses.

How do I create a Ninox record through Jentic?

Run pip install jentic, search Jentic for 'create a record in a Ninox table', and load POST /teams/{teamId}/databases/{databaseId}/tables/{tableId}/records. Provide the team, database, and table IDs along with a fields object.

Is the Ninox API free?

API access is bundled with Ninox paid plans. The API itself does not have separate per-call pricing; usage is included in the team's seat plan.

Ninox API

Connect the Ninox API to your agent

Capabilities

Start building with Ninox API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs