Client account access token
An API access token associated with a single Stitch client account. This token must be passed into the header of every request made to the API for the Stitch client account.
A client account access token is prefixed with ac_ so as not to be confused with partner credentials.
Connection check
A test performed by Stitch that checks the configuration of a source’s connection parameters.
Destination
Destination is the Stitch word for ‘data warehouse.’ A data warehouse is a central repository for data accumulated from a variety of sources.
Discovery
The first step in the replication process, this process takes place during the Extraction phase of a replication job. Discovery detects the tables and columns available in the source, along with any changes to the structure of those tables and columns.
Ephemeral token
Note: The Connect JavaScript client has been deprecated. Learn more.
A token that is passed to the Connect JavaScript client to create a session in the Stitch web application. This credential is created by using the Create a session endpoint in the Connect API.
A session is for the user for whom the API access token was created. The session will expire once terminated or after 12 hours.
Partner
An organization that utilizes Stitch Connect to programmatically create and/or manage Stitch client accounts on behalf of their users.
Partner ID
The unique ID for your partner application, obtained after an interest form is submitted to and approved by Stitch.
A partner ID is prefixed with oc_ so as not to be confused with a client account access token.
Partner credentials
A set of credentials specific to a Stitch partner, consisting of a partner ID and partner key, obtained after an interest form is submitted to and approved by Stitch.
Partner credentials are used only to create Stitch client accounts. After the Stitch client account is created, the account’s client access token is used to authenticate API requests.
Partner key
The key associated with your partner application, obtained after an interest form is submitted to and approved by Stitch.
A partner key is prefixed with oc_ so as not to be confused with a client account access token.
Replication job
The three-step process by which Stitch replicates data. A replication job includes three distinct steps: Extraction, preparation, and loading.
Session
A browser session in the Stitch web application.
Source
A database, API, or other data application that Stitch replicates data from. Outside of Connect, known as an ‘integration’.
Stitch client account
An individual account for the Stitch web application.
Stream
A table in a data source.
Structure sync
The first step in the replication process, this process takes place during the Extraction phase of a replication job. A structure sync detects the tables and columns available in the source, along with any changes to the structure of those tables and columns. This is also referred to as discovery.