PUT
/
stashes
/
{stashID}
/
{serial}

When using large datasets with the Glide API, it may be necessary to break them into smaller chunks for performance and reliability. We call this process “stashing.”

Tabular data may be stashed in JSON, CSV, or TSV format.

To learn more about stashing and how to use it to work with large datasets, please see our introduction to stashing.

Authorizations

Authorization
string
headerrequired

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

stashID
string
required

ID of the stash. The stash will be created if it doesn't already exist.

serial
string
required

Serial identifier of the chunk of data to set in the stash. If a chunk has already been sent with the same serial, its data will be overwritten. Chunks will be assembled in the sort order of their serials, so utilize ordered identifiers for each chunk if a specific ordering of data in the stash is desired, e.g., 1, 2, etc... If the order of data is not important, random, but unique, values can be used, e.g., c2a4567.

Body

{key}
any

Response

200 - application/json

A 200 HTTP response code indicates that the data was successfully stashed into the stash with the given stash ID.

Was this page helpful?

IntroductionDelete Stash