Snowpipe REST API¶

Endpoint: insertFiles¶

Informs Snowflake about the files to be ingested into a table. A successful response from this endpoint means that Snowflake has recorded the list of files to add to the table. It does not necessarily mean the files have been ingested. For more details, see the response codes below.

In most cases, Snowflake inserts fresh data into the target table within a few minutes.

Method: POST

POST URL:

https://{account}.snowflakecomputing.com/v1/data/pipes/{pipeName}/insertFiles?requestId={requestId}

URL Parameters:

• account (Required): Account identifier for your Snowflake account.

• pipeName (Required): Case-sensitive, fully qualified pipe name. For example, myDatabase.mySchema.myPipe.

• requestId (Optional): String used to track requests through the system. We recommend providing a random string with each request, for example, a UUID. This should be appended to the URL like this: ?requestId=<your_uuid>.

Request Headers

• Content-Type::

  • text/plain: For a plain text list of file paths and filenames, one per line. The size parameter is not allowed in this format.

  • application/json: For a JSON object containing a list of files with optional size information.

• Authorization: BEARER <jwt_token>

Request Body (for application/json Content-Type)

The request body must be a JSON object with a single key named “files”. The value associated with this key is an array of JSON objects, where each object represents a file to be ingested.

{
  "files":[
    {
      "path":"filePath/file1.csv",
      "size":100
    },
    {
      "path":"filePath/file2.csv",
      "size":100
    }
   ]
}

Each element in the “files” array is a JSON object with the following attributes:

• path (Required): The path and filename of the staged file. If you follow our recommended best practices by partitioning your data in the stage using logical, granular paths, the path values in the payload include the complete paths to the staged files.

• size (Optional, but recommended for better performance): The size of the file in bytes.

Request Body (for text/plain Content-Type)

The request body should be a plain text list of file paths and filenames, with one entry per line.

filePath/file_a.csv
another/path/file_b.json
yet/another/file_c.txt

Response Body

Response Codes:

• 200 — Success. Files added to the queue of files to ingest.

• 400 — Failure. Invalid request due to an invalid format, or limit exceeded.

• 404 — Failure. pipeName not recognized.

  This error code can also be returned if the role used when calling the endpoint does not have sufficient privileges. For more information, see Granting access privileges.

• 429 — Failure. Request rate limit exceeded.

• 500 — Failure. Internal error occurred.

Response Payload:

With a successful API request (i.e. code 200), the response payload contains the requestId and status elements in JSON format. If an error occurs, the response payload may contain details about the error.

{
  "requestId": "your_request_uuid",
  "status": "success"
}

Copy

If the COPY INTO <table> statement in the pipe definition includes the PATTERN copy option, the unmatchedPatternFiles attribute lists any files submitted in the header that did not match the regular expression and were therefore skipped.

{
  "requestId": "your_request_uuid",
  "status": "success",
  "unmatchedPatternFiles": ["some_file.txt", "another_file.dat"]
}

Copy

Endpoint: insertReport¶

Retrieves a report of files submitted via insertFiles whose contents were recently ingested into a table. Note that for large files, this may only be part of the file.

Note the following limitations for this endpoint:

• The 10,000 most recent events are retained.

• Events are retained for a maximum of 10 minutes.

An event occurs when data from a file submitted via insertFiles has been committed to the table and is available to queries. The insertReport endpoint can be thought of like the UNIX command tail. By calling this command repeatedly, it is possible to see the full history of events on a pipe over time. Note that the command must be called often enough to not miss events. How often depends on the rate files are sent to insertFiles.

Method: GET

GET URL:

https://<account_identifier>.snowflakecomputing.com/v1/data/pipes/<pipeName>/insertReport?requestId=<requestId>&beginMark=<beginMark>

URL Parameters:

• account_identifier (Required): Your unique Snowflake account identifier. The preferred format is organization_name-account_name. For alternative formats (account locator with region and cloud platform), see Format 1 (preferred): Account name in your organization.

• pipeName (Required): The case-sensitive, fully qualified name of the Snowpipe. For example, myDatabase.mySchema.myPipe.

• requestId (Optional): A string you can provide to track this specific request through Snowflake’s system. Using a random string like a UUID is highly recommended for easier debugging and monitoring. Append this to the URL like so: ?requestId=<your_uuid>.

• beginMark (Optional): A marker value returned in the nextBeginMark field of a previous insertReport response. Including this marker helps optimize subsequent calls by potentially reducing the number of duplicate events returned. Note: While beginMark is intended as a hint to avoid duplicates, occasional repetition of events might still occur. If beginMark is not specified, the report will show the ingestion history from the last 10 minutes. Append this to the URL like so: ?beginMark=<previous_nextBeginMark>.

Request Headers:

• Accept: Specifies the desired response format. Accepted values are text/plain or application/json.

• Authorization : Your Snowflake authentication token. Use the format BEARER <jwt_token>.

Request Body:

This endpoint does not accept a request body for GET requests. The necessary parameters are provided in the URL and headers.

Response Body:

Response Codes:

• 200 — Success. Report returned.

• 400 — Failure. Invalid request due to an invalid format, or limit exceeded.

• 404 — Failure. pipeName not recognized.

  This error code can also be returned if the role used when calling the endpoint does not have sufficient privileges. For more information, see Granting access privileges.

• 429 — Failure. Request rate limit exceeded.

• 500 — Failure. Internal error occurred.

Response Payload:

A success response (200) contains information about files that have recently been added to the table. Note that this report may only represent a portion of a large file.

For example:

{
  "pipe": "TESTDB.TESTSCHEMA.pipe2",
  "completeResult": true,
  "nextBeginMark": "1_39",
  "files": [
    {
      "path": "data2859002086815673867.csv",
      "stageLocation": "s3://mybucket/",
      "fileSize": 57,
      "timeReceived": "2017-06-21T04:47:41.453Z",
      "lastInsertTime": "2017-06-21T04:48:28.575Z",
      "rowsInserted": 1,
      "rowsParsed": 1,
      "errorsSeen": 0,
      "errorLimit": 1,
      "complete": true,
      "status": "LOADED"
    }
  ]
}

Copy

Response Fields:

Field	Type	Description
pipe	String	The fully-qualified name of the pipe.
completeResult	Boolean	false if an event was missed between the supplied beginMark and the first event in this report history. Otherwise, true.
nextBeginMark	String	beginMark to use on the next request to avoid seeing duplicate records. Note that this value is a hint. Duplicates can still occasionally occur.
files	Array	An array of JSON objects, one object for each file that is part of the history response.
path	String	The file path relative to the stage location.
stageLocation	String	Either the stage ID (internal stage) or the S3 bucket (external stage) defined in the pipe.
fileSize	Long	File size, in bytes.
timeReceived	String	Time that this file was received for processing. Format is ISO-8601 in UTC time zone.
lastInsertTime	String	Time that data from this file was last inserted into the table. Format is ISO-8601 in UTC time zone.
rowsInserted	Long	Number of rows inserted into the target table from the file.
rowsParsed	Long	Number of rows parsed from the file. Rows with errors may be skipped.
errorsSeen	Integer	Number of errors seen in the file
errorLimit	Integer	Number of errors allowed in the file before it is considered failed (based on ON_ERROR copy option).
firstError [1]	String	Error message for the first error encountered in this file.
firstErrorLineNum [1]	Long	Line number of the first error.
firstErrorCharacterPos [1]	Long	Character position of the first error.
firstErrorColumnName [1]	String	Column name where the first error occurred.
systemError [1]	String	General error describing why the file was not processed.
complete	Boolean	Indicates whether the file was completely processed successfully.
status	String	Load status for the file:
		LOAD_IN_PROGRESS: Part of the file has been loaded into the table, but the load process has not completed yet.
		LOADED: The entire file has been loaded into the table.
		LOAD_FAILED: The file load failed.
		PARTIALLY_LOADED: Some rows from this file were loaded successfully, but others were not loaded due to errors. Processing of this file is completed.

_{[1] Values are only supplied for these fields when files include errors.}

Endpoint: loadHistoryScan¶

Fetches a report about ingested files whose contents have been added to table. Note that for large files, this may only be part of the file. This endpoint differs from insertReport in that it views the history between two points in time. There is a maximum of 10,000 items returned, but multiple calls can be issued to cover the desired time range.

For a more comprehensive view, without these limits, Snowflake provides an Information Schema table function, COPY_HISTORY, that returns the load history of a pipe or table.

Method: GET

GET URL:

https://{account}.snowflakecomputing.com/v1/data/pipes/{pipeName}/loadHistoryScan?startTimeInclusive=<startTime>&endTimeExclusive=<endTime>&requestId=<requestId>

URL Parameters:

• account (Required): Your unique Snowflake account identifier.

• pipeName (Required): The case-sensitive, fully qualified name of the Snowpipe. Example: myDatabase.mySchema.myPipe.

• startTimeInclusive (Required): The beginning of the time range for retrieving load history data, specified as a timestamp in ISO-8601 format (for example, 2023-10-26T10:00:00Z). This timestamp marks the inclusive lower bound of the query.

• endTimeExclusive (Optional): The end of the time range for retrieving load history data, specified as a timestamp in ISO-8601 format (for example, 2023-10-26T10:15:00Z). This timestamp marks the exclusive upper bound of the query. If this parameter is omitted, the current server timestamp (CURRENT_TIMESTAMP()) will be used as the end of the time range.

• requestId (Optional): A string you can provide to track this specific request through Snowflake’s system. We recommend using a random string like a UUID for easier debugging and monitoring. Append this to the URL like so: ?requestId=<your_uuid>.

Request Headers:

• Accept: Specifies the desired response format. Accepted values are text/plain or application/json.

• Authorization: Your Snowflake authentication token. Use the format BEARER <jwt_token>.

Request Body:

This endpoint does not accept a request body for GET requests. All necessary parameters are provided in the URL and headers.

Response Body:

Response Codes:

• 200 — Success. Load History scan results are returned.

• 400 — Failure. Invalid request due to an invalid format, or limit exceeded.

• 404 — Failure. pipeName not recognized.

• 429 — Failure. Request rate limit exceeded.

• 500 — Failure. Internal error occurred.

Response Payload:

A success response (200) contains information about files that have recently been added to the table. Note that this report may only represent a portion of a large file.

For example:

{
  "pipe": "TESTDB.TESTSCHEMA.pipe2",
  "completeResult": true,
  "startTimeInclusive": "2017-08-25T18:42:31.081Z",
  "endTimeExclusive":"2017-08-25T22:43:45.552Z",
  "rangeStartTime":"2017-08-25T22:43:45.383Z",
  "rangeEndTime":"2017-08-25T22:43:45.383Z",
  "files": [
    {
      "path": "data2859002086815673867.csv",
      "stageLocation": "s3://mystage/",
      "fileSize": 57,
      "timeReceived": "2017-08-25T22:43:45.383Z",
      "lastInsertTime": "2017-08-25T22:43:45.383Z",
      "rowsInserted": 1,
      "rowsParsed": 1,
      "errorsSeen": 0,
      "errorLimit": 1,
      "complete": true,
      "status": "LOADED"
    }
  ]
}

Copy

Response Fields:

Field	Type	Description
pipe	String	Fully-qualified name of the pipe.
completeResult	Boolean	false if the report is incomplete (i.e. the number of entries in the specified time range exceeds the 10,000 entry limit). If false, the user can specify the current rangeEndTime value as the startTimeInclusive value for the next request to proceed to the next set of entries.
startTimeInclusive	String	Starting timestamp (in ISO-8601 format) provided in the request.
endTimeExclusive	String	Ending timestamp (in ISO-8601 format) provided in the request.
rangeStartTime	String	Timestamp (in ISO-8601 format) of the oldest entry in the files included in the response.
rangeEndTime	String	Timestamp (in ISO-8601 format) of the latest entry in the files included in the response.
files	Array	An array of JSON objects, one object for each file that is part of the history response. Within the array, the response fields are the same as those returned in the insertReport response.