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

# SeekTable API

SeekTable provides a secure web API for accessing reports saved in your SeekTable account. Use it to automate report generation in various formats including HTML, PDF, CSV, Excel, JSON, and PNG. The API exposes 3 endpoints secured with bearer authentication.

## For AI agents

Programmatically generate and export a report (post), generate and export a report. Covers 3 operations with bearer authentication.

## Scope

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

## Capabilities

- Generate and export a report (POST)
- Share a report by email
- Integrate SeekTable API into automated workflows
- Query and filter SeekTable API records by parameters
- Monitor SeekTable API operational status and events

## Use cases

### Analytics Operations

Use the SeekTable API to perform analytics operations programmatically. The API provides 3 endpoints covering core functionality including generate and export a report (post), generate and export a report, share a report by email.

Example prompt: Call POST `/api/report/{report_id}/export` to generate and export a report (post)

### Automated Report Management

Automate report operations by combining multiple SeekTable API endpoints. Agents can generate and export a report and then share a report by email in a single workflow.

Example prompt: Call GET `/api/report/{report_id}/export` to generate and export a report, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SeekTable 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 'generate and export a report (post)', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/report/{report_id}/export` | Generate and export a report (POST) |
| GET | `/api/report/{report_id}/export` | Generate and export a report |
| POST | `/api/report/{report_id}/share/email` | Share a report by email |

## Key resources

- **Report** — Operations for report

## 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:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 58 / 100
- **View full report:** https://jentic.com/apis/seektable.com/seektable/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 SeekTable API by hand means obtaining its JWT bearer token, threading it onto each export call, and handling the report generation and email-share request shapes yourself. Through Jentic you install once, import SeekTable from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** SeekTable puts the report id in the URL path (`/api/report/{report_id}/...`), so a rule can pin your agent to one report: it can export that report and nothing else. You choose the operations it may call, so the email-share operation is not included unless you add it.
- **Credential handling:** Your SeekTable 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 'export a report' or 'email a report', and Jentic returns the matching SeekTable operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the SeekTable API use?

The SeekTable 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 generate and export a report (post) with the SeekTable API?

Yes. Use the POST `/api/report/{report_id}/export` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SeekTable 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 generate and export a report (post) through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'generate and export a report (post)'. Jentic returns the matching SeekTable API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The SeekTable API exposes 3 endpoints covering report operations.

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

Yes. Because you self-host Jentic One, your own rules decide which SeekTable operations and credentials the agent may use. Since the report id lives in the URL path (`/api/report/{report_id}/export`), you can pin the agent to a single report so it exports only that one and nothing else. You also choose the allowed operations, so the email-share endpoint stays off unless you explicitly add it.