Skip to main content
CredentialsBefore using this method, retrieve your API key and the appropriate Sift URL for your environment. See Authentication.
Schemaless ingestion lets you send a JSON payload to the /api/v2/ingest endpoint without pre-registering an ingestion config. Sift creates the asset and channels automatically if they do not already exist.

Example request

You can also let Sift resolve the run for you by providing run_config instead of run_id:

Request fields

The name of the asset. If the asset does not exist, it will be created. Required.
The run_id returned from a previous CreateRun call. Optional. Cannot be used together with run_config.
Resolves a run by client key instead of requiring a run_id, so the client does not need to look up or track run IDs itself. Optional. Cannot be used together with run_id.If no run with the given client_key exists, Sift creates one and uses it. If a run with that client_key already exists, Sift resolves its run_id and uses it as-is. run_config only creates a run when one does not already exist; it never modifies an existing run’s name or any other field.
An arbitrary user-chosen key that uniquely identifies the run. Must be 3-128 characters, start and end with an alphanumeric character, and contain only letters, numbers, and _~.-. Required when run_config is provided.
The name to give the run if it needs to be created. Only used at creation time and has no effect on an existing run. Defaults to client_key if omitted. Optional.
The organization ID of the organization that owns the asset. Only required if you are a member of multiple organizations. Optional otherwise.
The array of data objects to ingest.
The timestamp used for every value in the sibling values array. Must be in RFC3339 format. Required.
The array of channel values. Every value is assigned the timestamp from the sibling timestamp field.
The name of the channel. Required.
The channel value. Supported types are string, boolean, and number. Required.