canonical: https://jentic.com/apis/tableconvert.com/tableconvert

# TableConvert API

TableConvert provides a table data conversion API supporting over 370 different conversion formats. Convert between Excel, CSV, JSON, HTML, Markdown, and many more table formats. The API exposes 6 endpoints secured with bearer authentication.

## For AI agents

Programmatically convert excel to json, convert csv to json. Covers 6 operations with bearer authentication.

## Scope

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

## Capabilities

- Convert Excel to JSON
- Manage crm data programmatically
- Integrate TableConvert API into automated workflows
- Query and filter TableConvert API records by parameters
- Monitor TableConvert API operational status and events

## Use cases

### CRM Operations

Use the TableConvert API to perform crm operations programmatically. The API provides 6 endpoints covering core functionality including convert excel to json, convert csv to json, convert json to csv.

Example prompt: Call POST `/api/convert/excel-to-json` to convert excel to json

### Automated Convert Management

Automate convert operations by combining multiple TableConvert API endpoints. Agents can convert csv to json and then convert json to csv in a single workflow.

Example prompt: Call POST `/api/convert/csv-to-json` to convert csv to json, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call TableConvert 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 'convert excel to json', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/convert/excel-to-json` | Convert Excel to JSON |
| POST | `/api/convert/csv-to-json` | Convert CSV to JSON |
| POST | `/api/convert/json-to-csv` | Convert JSON to CSV |
| POST | `/api/convert/html-to-markdown` | Convert HTML to Markdown |
| POST | `/api/convert/markdown-to-html` | Convert Markdown to HTML |
| POST | `/api/convert/csv-to-markdown` | Convert CSV to Markdown |

## Key resources

- **Convert** — Operations for convert

## 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:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/tableconvert.com/tableconvert/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 TableConvert API by hand means setting up bearer token auth and posting each conversion payload to the right endpoint yourself. Through Jentic you install once, import the TableConvert API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** TableConvert's conversions carry their data in the request body, so limit the agent to the operations it needs, such as CSV to JSON or Markdown to HTML, rather than to any one resource. Every conversion the agent can run is one you chose to allow.
- **Credential handling:** Your TableConvert token 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 'convert Excel to JSON' or 'turn CSV into a Markdown table', and Jentic returns the matching TableConvert 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 TableConvert API use?

The TableConvert 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 convert excel to json with the TableConvert API?

Yes. Use the POST `/api/convert/excel-to-json` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the TableConvert 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 convert excel to json through Jentic?

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

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

The TableConvert API exposes 6 endpoints covering convert operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which TableConvert operations the agent may call and which credential it uses. Since every conversion carries its data in the request body rather than targeting a stored resource, you scope by operation: allow only the endpoints the agent needs, such as CSV to JSON or Markdown to HTML, and leave the rest, like Excel to JSON or JSON to CSV, unavailable. Every conversion the agent can run is one you explicitly chose to allow.