AWS Redshift Data API Service

Name: Redshift Data API Service API
Brand: Redshift Data API Service
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsBusiness Intelligencehmac10 Endpoints

Install Jentic One Beta

Connect the Redshift Data API Service to your agent

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

Submit a single SQL statement with parameters via ExecuteStatement and receive a statement Id

Run multiple statements in one call with BatchExecuteStatement and track them as a single batch

Check execution status, query duration, and error messages with DescribeStatement

GET STARTED

Start building with Redshift Data API Service API

Explore with Jentic

View OpenAPI Document

For Agents

Run asynchronous SQL queries on Amazon Redshift clusters and Serverless workgroups, fetch results, and inspect schemas through the Data API.

Use for: I need to run an analytical SELECT against a Redshift cluster, Submit a SQL statement to Redshift Serverless and poll for completion, Fetch the result rows for a previously submitted Redshift statement, List all schemas in a Redshift database

Not supported: Does not provision clusters, load data, or modify cluster settings - use for asynchronous SQL execution and catalog inspection on existing Redshift clusters and Serverless workgroups only.

Use Cases

Patterns agents use Redshift Data API Service API for, with concrete tasks.

★ Async Analytical Queries from Lambda

Submit a long-running SELECT to Redshift from a stateless service without holding a JDBC connection. ExecuteStatement returns a statement Id immediately; the caller polls DescribeStatement until Status is FINISHED, then pages results with GetStatementResult. Works against both provisioned ClusterIdentifier with a DbUser, and Redshift Serverless with a WorkgroupName plus Secrets Manager secretArn.

Call POST ExecuteStatement with WorkgroupName 'analytics', Database 'prod', and Sql 'SELECT count(*) FROM events WHERE created_at > current_date - 7'; capture Id and poll DescribeStatement until Status='FINISHED'

Schema Discovery for Agents

Let an agent reason over a warehouse it has not seen before by listing schemas and tables on demand. ListDatabases, ListSchemas, and ListTables produce a navigable tree, and DescribeTable returns column names and types for a specific table. Pair with a query-generation step so the agent grounds SQL on real columns rather than guessing.

Call ListSchemas with WorkgroupName 'analytics' and Database 'prod', then DescribeTable for each candidate table to get its columns

Multi-Statement Batches and Cancellation

Run a batch of related SQL statements (e.g., SET search_path; SELECT ...; SELECT ...) with BatchExecuteStatement so they execute on the same backend session. If a downstream tool times out, CancelStatement aborts the running query by Id, and DescribeStatement surfaces the final state. Useful for orchestrated reports from Step Functions or Airflow.

Call BatchExecuteStatement with Sqls ['SET search_path TO analytics', 'SELECT ...'] and the same WorkgroupName, then CancelStatement if the orchestrator times out

AI Agent Warehouse Tool via Jentic

A data-analyst agent uses Jentic to discover the Redshift Data API, generate SQL grounded in the introspected schema, submit it, and stream the results back to the user. Jentic stores AWS credentials in its vault and signs each call with SigV4; database credentials remain in Secrets Manager (or temporary credentials via DbUser), so neither secret leaks to the agent context.

Use Jentic to search 'run sql on redshift', load ExecuteStatement, and execute it with WorkgroupName, Database, and a generated Sql string

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for the amazon redshift data api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/#X-Amz-Target=RedshiftData.ExecuteStatement

Submit a SQL statement and receive a statement Id

POST

/#X-Amz-Target=RedshiftData.BatchExecuteStatement

Run a batch of SQL statements as one request

POST

/#X-Amz-Target=RedshiftData.DescribeStatement

Get status, duration, and error info for a statement Id

POST

/#X-Amz-Target=RedshiftData.GetStatementResult

Page through result rows for a finished statement

POST

/#X-Amz-Target=RedshiftData.CancelStatement

Cancel a running statement by Id

POST

/#X-Amz-Target=RedshiftData.ListTables

List tables in a database and schema

POST

/#X-Amz-Target=RedshiftData.DescribeTable

Return column metadata for a specific table

POST

/#X-Amz-Target=RedshiftData.ExecuteStatement

Submit a SQL statement and receive a statement Id

POST

/#X-Amz-Target=RedshiftData.BatchExecuteStatement

Run a batch of SQL statements as one request

POST

/#X-Amz-Target=RedshiftData.DescribeStatement

Get status, duration, and error info for a statement Id

POST

/#X-Amz-Target=RedshiftData.GetStatementResult

Page through result rows for a finished statement

POST

/#X-Amz-Target=RedshiftData.CancelStatement

Cancel a running statement by Id

Why Jentic?

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

Credential isolation

Your AWS access keys are stored once, encrypted, by your own Jentic One instance and used to produce a SigV4 signature per request, while Redshift credentials stay in Secrets Manager referenced by SecretArn. Neither secret enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'run SQL on a Redshift cluster', and Jentic returns ExecuteStatement with its parameter schema for WorkgroupName, ClusterIdentifier, Database, Sql, and Parameters so the agent calls the right endpoint directly.

Time to first call

FAQs

Specific to using Redshift Data API Service API through Jentic.

Why is there no official OpenAPI spec for the Amazon Redshift Data API?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Amazon Redshift Data API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Redshift Data API use?

The API uses AWS SigV4 HMAC request signing. The caller authenticates to Redshift either via temporary credentials (DbUser plus IAM auth on the cluster) or via a Secrets Manager secretArn passed in the request. Through Jentic, AWS credentials live in the vault and SigV4 signatures are produced per call.

Does this API support Redshift Serverless?

Yes. Pass WorkgroupName instead of ClusterIdentifier in ExecuteStatement and BatchExecuteStatement. Redshift Serverless requires SecretArn for authentication; it does not accept DbUser-based IAM auth.

Are Data API queries synchronous?

No. ExecuteStatement and BatchExecuteStatement return a statement Id immediately and run asynchronously. Poll DescribeStatement until Status is FINISHED, then call GetStatementResult or GetStatementResultV2 to page through the rows.

What are the limits on result size and statement duration?

Statement results have a 100 MB cap and a maximum row count limit; results are paginated via NextToken. Statements have a 24-hour maximum runtime, and around 500 active statements are allowed per cluster or workgroup. Throttled requests return ThrottlingException.

How do I query Redshift through Jentic?

Search Jentic for 'run sql on redshift', load ExecuteStatement, and execute it with WorkgroupName (or ClusterIdentifier), Database, and Sql. Poll the returned Id with DescribeStatement, then GetStatementResult to fetch rows. Install with pip install jentic.

Can I limit what my agent is allowed to do with the Redshift Data API?

Yes. Because you run Jentic One yourself, your own rules decide which Redshift Data API operations and credentials the agent may use. The workgroup, cluster, database, and SQL all travel in the request body, so you can grant the agent only read-and-run operations like ExecuteStatement, DescribeStatement, and GetStatementResult while withholding others. Operations such as CancelStatement or BatchExecuteStatement are available to the agent only when you explicitly grant them.

AWS Redshift Data API Service

Connect the Redshift Data API Service to your agent

Capabilities

Start building with Redshift Data API Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs