canonical: https://jentic.com/apis/redash.io/redash

# Redash API

Redash is a data visualization and dashboarding platform. The API allows you to programmatically create queries, refresh data, manage dashboards, and access query results. The API exposes 10 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create a new query, list all queries. Covers 10 operations with apiKey authentication.

## Scope

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

## Capabilities

- Create a new query
- List all queries
- Update query
- Get query by ID
- Delete query
- Refresh query results

## Use cases

### Analytics Operations

Use the Redash API to perform analytics operations programmatically. The API provides 10 endpoints covering core functionality including create a new query, list all queries, update query.

Example prompt: Call POST /queries to create a new query

### Automated Queries Management

Automate queries operations by combining multiple Redash API endpoints. Agents can list all queries and then update query in a single workflow.

Example prompt: Call GET /queries to list all queries, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Redash 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 apiKey tokens manually.

Example prompt: Search Jentic for 'create a new query', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/queries` | Create a new query |
| GET | `/queries` | List all queries |
| POST | `/queries/{query_id}` | Update query |
| GET | `/queries/{query_id}` | Get query by ID |
| DELETE | `/queries/{query_id}` | Delete query |
| POST | `/queries/{query_id}/results` | Refresh query results |
| GET | `/dashboards` | List all dashboards |
| GET | `/dashboards/{dashboard_slug}` | Get dashboard by slug |

## Key resources

- **Queries** — Query management operations
- **Dashboards** — Dashboard management operations
- **Data Sources** — Data source operations
- **Users** — User management operations

## Why Jentic

- **Setup:** Wiring the Redash API by hand means learning its apiKey auth and pointing every request at your own instance host (/{instance}.redash.io/api). Through Jentic you install once, import the Redash API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Redash puts the query id in the URL path (`/queries/{query_id}`), so a rule can pin your agent to specific queries. You choose the operations it may call, so writes like deleting a query or running its results are only included if you add them.
- **Credential handling:** Your Redash API key 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 'create a query' or 'fetch query results', and Jentic returns the matching Redash 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 Redash API use?

The Redash API uses an API key passed in the `api_key` query. 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 create a new query with the Redash API?

Yes. Use the POST /queries endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Redash 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 create a new query through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new query'. Jentic returns the matching Redash API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The Redash API exposes 10 endpoints covering queries, dashboards, data sources operations.

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

Yes. Because you self-host Jentic One, your own rules decide which Redash operations and credentials the agent may use. Since Redash puts the query id in the URL path (`/queries/{query_id}`), you can pin the agent to specific queries and choose exactly which operations it calls, such as allowing GET /queries to list and read while withholding write actions. Destructive calls like DELETE `/queries/{query_id}` or POST `/queries/{query_id}/results` to refresh results are only available to the agent if you add them.