Skip to main content

Note

You can find below the full description of Parameters for each POST/PATCH/GET/DELETE methods and also what parameters you can expect from the API responses.
If you want to play with the API, please see the Contexts API playground.

Parameters:

name String

Displayed name of the context

description String

Description of the context

externalId String

Unique Identifier of the context you can optionally provide

isSynced Boolean

When a context is synced, files ingestion are synced with automatic mechanism (external process). Hence, the files ingested in the context cannot be managed manually via the Mindset App admin portal.

Parameters:

name String

Displayed name of the context

description String

Description of the context

Parameters:

startAfter - Querying for “the next page” String

Use the startAfter parameter and provide the createdAt string of the last context in the current results set When there are no more results you will receive an empty array in the response and a 404 status code.
Note: You cannot delete a context containing files. You will receive a 422 response code if you try.
You will get the same response data when calling POST, PATCH or GETNote: When retrieving a collection of contexts, the response will be an array of objects.

uid String

Mindset internal context uid

externalId String

Unique Identifier of the context you can optionally provide

name String

Displayed name of the context

description String

Description of the context

createdAt ISO timestamp

Context creation date

isSynced Boolean

Set to True when you need to syncronize the context files with an ingestion integrated process (Via Cyclr)
I