
<section>
    <h1>Result</h1>
</section>


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.

The Snowflake Result API is a REST API that you can use to check request status and fetch request response.

Snowflake Result API

Get result status or the result when it is ready.

result_handler

Number of the page of results to return. The number can range from 0 to the total number of pages minus 1.

page

Successfully accepted the request, but it is not completed yet.

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.

Code	Beschreibung
200	successful
202	Successfully accepted the request, but it is not completed yet.

Result

Check result status or fetch request¶

Pfadparameter¶

Abfrageparameter¶

Antwort¶

Antwort-Bodyschema¶