Count Public API

Name: Count Public API API
Brand: Count Public API
Availability: InStock

✓ Official Vendor SpecAnalyticsBusiness Intelligencebearer17 EndpointsREST

For Agents

Run SQL queries, list canvases and catalogs, refresh data connections, and export results from a Count workspace. Suitable for automated reporting and exploratory analytics workflows.

Quickstart

Get started with Count Public API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"run a SQL query in Count"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Count Public API API.

Run a SQL query against a connected warehouse and retrieve the resulting job key

List canvases in a workspace and fetch a specific canvas by key

Browse catalogs of curated tables and connections

Refresh schema and metadata for a connected data source

Export query results as a downloadable CSV file

GET STARTED

Start building with Count Public API API

Explore with Jentic

View OpenAPI Document

The Count Public API lets developers and AI agents interact with a Count workspace programmatically, exposing canvases, catalogs, connections, projects, queries, and workspace members across 17 endpoints. Agents can run SQL queries against connected data sources, list and inspect canvases, refresh connection metadata or schemas, and export query results to CSV. The API is designed around the data canvas model rather than dashboards, so it suits exploratory analytics, automated reporting, and pipelines that need to read or trigger query jobs in Count.

Use Cases

Patterns agents use Count Public API API for, with concrete tasks.

★ Automated SQL Reporting

Trigger SQL queries in Count programmatically and pull the results into downstream pipelines or scheduled reports. The API accepts a query, returns a job key, and exposes a CSV export endpoint so the same query can feed a BI dashboard, an email digest, or a data warehouse load. Suitable for teams that already model data in Count and want to reuse those queries outside the canvas UI.

Submit a SQL query to POST /v1/queries, poll GET /v1/queries/{job_key} until complete, then call POST /v1/queries/{job_key}/create_csv to obtain the CSV file

Canvas and Catalog Inventory

Build an inventory of every canvas, catalog, and connection in a Count workspace for governance or documentation purposes. The API exposes paginated list endpoints for canvases, catalogs, projects, and connections, and a workspace search endpoint for cross-resource lookup. Useful when migrating between BI tools or producing a catalogue of analytical assets.

Call GET /v1/canvases, GET /v1/catalogs, GET /v1/projects, and GET /v1/connections and produce a JSON manifest of every asset keyed by resource type

Connection Health Monitoring

Keep Count connections in sync with upstream warehouses by refreshing metadata and schemas on a schedule. The API exposes refresh_metadata and refresh_schema endpoints per connection, so an agent can detect when a connected source has changed and trigger a refresh before users open the canvas. Reduces stale-schema errors during analyst sessions.

List all connections via GET /v1/connections then call POST /v1/connections/{connection_key}/refresh_schema for each connection that has not been refreshed in the last 24 hours

AI Agent Analytics Workflow

Let an AI agent answer business questions by running SQL against a Count workspace through Jentic. The agent searches for the right operation in plain English, loads the schema, runs a query, and returns either the job key or the CSV. Because credentials live in the Jentic vault, the agent never sees the raw bearer token. End-to-end integration takes under an hour rather than several days.

Use Jentic to search for 'run a query in Count', load the operation schema for POST /v1/queries, execute it with a user-supplied SQL string, and return the job_key

Key Endpoints

17 endpoints — the count public api lets developers and ai agents interact with a count workspace programmatically, exposing canvases, catalogs, connections, projects, queries, and workspace members across 17 endpoints.

METHOD

PATH

DESCRIPTION

POST

/v1/queries

Run a SQL query and obtain a job key

GET

/v1/queries/:job_key

Get the status and result of a query job

POST

/v1/queries/:job_key/create_csv

Create a CSV file from a completed query

GET

/v1/canvases

List canvases in the workspace

GET

/v1/connections

List data connections

POST

/v1/connections/:connection_key/refresh_schema

Refresh the schema for a connection

GET

/v1/workspaces/search

Search across workspace content

POST

/v1/queries

Run a SQL query and obtain a job key

GET

/v1/queries/:job_key

Get the status and result of a query job

POST

/v1/queries/:job_key/create_csv

Create a CSV file from a completed query

GET

/v1/canvases

List canvases in the workspace

GET

/v1/connections

List data connections

Why though Jentic?

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

Credential isolation

Count workspace bearer tokens are stored encrypted in the Jentic MAXsystem vault. Agents receive scoped session tokens for each call, so the raw API key never enters the agent's prompt or logs.

Intent-based discovery

Agents search Jentic with intents like 'run a SQL query in Count' or 'export a Count query as CSV' and Jentic returns the matching operation along with its parameter schema, so the agent calls the right endpoint without reading the spec.

Time to first call

Direct integration with Count: 1-3 days for auth handling, query polling, and CSV download wiring. Through Jentic: under 1 hour to search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Metabase API

Open-source BI platform with similar SQL-question and dashboard primitives

Choose Metabase when the team self-hosts BI and needs question, dashboard, and pulse endpoints rather than Count's canvas model

Alternative

Tableau API

Enterprise BI with workbooks, data sources, and embedded analytics

Choose Tableau for large-enterprise dashboards, governance, and embedded reporting workflows

Complementary

Snowflake API

Cloud data warehouse that often sits behind a Count connection

Use Snowflake when you need to manage warehouses, roles, or table metadata directly rather than going through a Count canvas

Complementary

dbt Cloud API

Transformation layer that produces the modelled tables Count queries against

Use dbt to trigger or inspect upstream model runs before refreshing Count schemas

FAQs

Specific to using Count Public API API through Jentic.

What authentication does the Count Public API use?

The Count Public API uses HTTP bearer authentication. You generate a workspace API key in Count and pass it as `Authorization: Bearer <key>` on every request. When called through Jentic, the key is stored in the encrypted MAXsystem vault and the agent receives a scoped session token rather than the raw key.

Can I run arbitrary SQL with the Count Public API?

Yes. POST /v1/queries accepts a SQL string and runs it against the workspace's connected warehouse, returning a job key you can poll with GET /v1/queries/{job_key} until the job finishes. The result can then be exported as CSV via POST /v1/queries/{job_key}/create_csv.

What are the rate limits for the Count Public API?

Count does not publish hard rate limits in the OpenAPI spec, but workspace plans determine concurrent query and connection refresh quotas. Treat it as best practice to keep query polling intervals at 2-5 seconds and avoid more than a handful of concurrent refresh_schema calls.

How do I export a Count query as CSV through Jentic?

Search Jentic for 'export count query as csv', load the schema for POST /v1/queries/{job_key}/create_csv, then execute it with the job_key returned by your earlier query. Jentic handles the bearer credential and returns the CSV download URL.

Does the Count Public API support webhooks or events?

No. The current spec only exposes synchronous REST operations across canvases, catalogs, connections, projects, queries, and workspaces. To detect query completion you poll GET /v1/queries/{job_key}.

Can agents create new canvases via the Count Public API?

The spec does not include a create-canvas endpoint, but it does expose POST /v1/canvases/agent which creates an agent on a canvas. For full canvas authoring, use the Count UI.