
<section>
    <h1>Cortex Search Service</h1>
</section>


A search query and additional parameters for search.

Opaque container for experimental features. You probably do not want to use this.

Configure External Oauth with Snowflake (see <a href=https://docs.snowflake.com/en/user-guide/oauth-ext-overview>External OAuth overview</a>.) Set `X-Snowflake-Authorization-Token-Type` to `OAUTH` and set the Token to the auth token received from the external Auth server.

Set `X-Snowflake-Authorization-Token-Type` to `KEYPAIR_JWT` if the token is a key-pair authentication JWT.

Set `X-Snowflake-Authorization-Token-Type` to `OAUTH` if the token is snowflakeOAuth

Snowflake, Inc.

OpenAPI 3.0 specification for the Cortex Search REST API

Cortex Search REST API

Query a Cortex Search Service to get search results.

Identifier (i.e. name) for the database to which the resource belongs. You can use the `/api/v2/databases` GET request to get a list of available databases.

database

Identifier (i.e. name) for the schema to which the resource belongs. You can use the `/api/v2/databases/{database}/schemas` GET request to get a list of available schemas for the specified database.

schema

service_name

Bad Request. The request payload is invalid or malformed. This happens if the application didn't send the correct request payload. The response body may include the error code and message indicating the actual cause. The application must reconstruct the request body for retry.

Unauthorized. The request is not authorized. This happens if the attached access token is invalid or missing. The response body may include the error code and message indicating the actual cause, e.g., expired, invalid token. The application must obtain a new access token for retry.

Forbidden. The request is forbidden. This can also happen if the request is made even if the API is not enabled.

Not Found. The request endpoint is not valid. This happens if the API endpoint does not exist, or if the API is not enabled.

Method Not Allowed. The request method doesn't match the supported API. This happens, for example, if the application calls the API with GET method but the endpoint accepts only POST.

Request Timeout. This indicates that the request from the client timed out and was not completed by the server.

Conflict. The requested operation could not be performed due to a conflicting state that could not be resolved. This usually happens when a CREATE request was performed when there is a pre-existing resource with the same name, and also without one of the options orReplace/ifNotExists.

Internal Server Error. The server hit an unrecoverable system error. The response body may include the error code and message for further guidance. The application owner may need to reach out the customer support.

Service Unavailable. The request was not processed due to server side timeouts. The application may retry with backoff. The jittered backoff is recommended.

Gateway Timeout. The request was not processed due to server side timeouts. The application may retry with backoff. The jittered backoff is recommended.

Parameter	Description
database string	Identifier (i.e. name) for the database to which the resource belongs. You can use the `/api/v2/databases` GET request to get a list of available databases.
schema	Identifier (i.e. name) for the schema to which the resource belongs. You can use the `/api/v2/databases/{database}/schemas` GET request to get a list of available schemas for the specified database.
service_name string	The name of the Cortex Search Service.

Cortex Search Service

Query a Cortex Search Service¶

Path Parameters¶

Response¶

Response Body Schema¶