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

# Snowflake SQL API

The Snowflake SQL API is a REST API that you can use to access and update data in a Snowflake database. The API exposes 3 endpoints secured with bearer, oauth2 authentication.

## For AI agents

Programmatically submits a sql statement for execution., checks the status of the execution of a statement. Covers 3 operations with bearer, oauth2 authentication.

## Scope

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

## Capabilities

- Submits a SQL statement for execution.
- Checks the status of the execution of a statement
- Cancels the execution of a statement.
- Query and filter Snowflake SQL API records by parameters
- Monitor Snowflake SQL API operational status and events

## Use cases

### Developer Tools Operations

Use the Snowflake SQL API to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including submits a sql statement for execution., checks the status of the execution of a statement, cancels the execution of a statement..

Example prompt: Call POST /api/v2/statements to submits a sql statement for execution.

### Automated Statements Management

Automate statements operations by combining multiple Snowflake SQL API endpoints. Agents can checks the status of the execution of a statement and then cancels the execution of a statement. in a single workflow.

Example prompt: Call GET /api/v2/statements/{statementHandle} to checks the status of the execution of a statement, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Snowflake SQL 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, oauth2 tokens manually.

Example prompt: Search Jentic for 'submits a sql statement for execution.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/v2/statements | Submits a SQL statement for execution. |
| GET | /api/v2/statements/{statementHandle} | Checks the status of the execution of a statement |
| POST | /api/v2/statements/{statementHandle}/cancel | Cancels the execution of a statement. |

## Key resources

- **Statements** — Operations for statements

## Why Jentic

- **Setup:** Wiring the Snowflake SQL API by hand means setting up key-pair or OAuth bearer auth, pointing at your org-account.snowflakecomputing.com host, and polling statement handles for results yourself. Through Jentic you install once, import the Snowflake SQL API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The Snowflake SQL API submits work in the request body and references a statement handle rather than a durable resource id in the path, so limit the agent to the operations it needs, such as submitting a statement and reading its status. You choose that set, so cancelling a running statement is only included if you add it.
- **Credential handling:** Your Snowflake SQL API credential 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 'run a SQL statement' or 'check a query result', and Jentic returns the matching Snowflake SQL API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Snowflake SQL API use?

The Snowflake SQL API uses bearer, oauth2 authentication. 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 submits a sql statement for execution. with the Snowflake SQL API?

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

### What are the rate limits for the Snowflake SQL 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 submits a sql statement for execution. through Jentic?

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

### How many endpoints does the Snowflake SQL API have?

The Snowflake SQL API exposes 3 endpoints covering statements operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Snowflake SQL API operations and credentials the agent can use. You can allow only submitting a statement (POST /api/v2/statements) and reading its status (GET /api/v2/statements/{statementHandle}), and leave out cancelling a running statement (POST /api/v2/statements/{statementHandle}/cancel) unless you explicitly add it. The stored credential is injected only for the operations you permit, so the agent cannot call anything outside that set.