About this template
File location: | /_templates/connect |
Used in: | |
Repo link: | Click to view in the Stitch Docs repo |
Instructions: |
This template is used to add new database source form properties to the Connect API documentation. This template is used to add new database source form properties to the Connect API documentation.
Template sections
Each template is grouped into sections to make parameters easier to find. These sections and the parameters they contain are described below.
API content types
These parameters control how the content for the connection property is formatted and how links to the connection property’s section are generated.
Parameter | Description |
product-type STRING |
The developer ‘product’ the property is associated with. For source or destination connection properties, this will always be |
content-type STRING |
The type of Connect content. This will be |
form-type STRING |
The type of connection property this is. Must be one of the following:
|
key STRING |
The unique ID of the connection property, formatted as This is used to create an anchor link for the connection property, which is used throughout the documentation and in the side navigation. Example values:
|
Object property details
Details about the connection property and its source, such as its name, a description, etc.
Parameter | Description |
title STRING |
The display title for the connection property, formatted as Example values:
|
api-type STRING |
The name of the connection property as returned by the Connect API, with For example: Heroku is returned as |
display-name STRING |
The display name of the source or destination. Example values:
|
docs-name STRING |
The source or destination key as it is in the Stitch Docs. In the corresponding documentation, this will be equal to:
|
db-type STRING |
The type of database that backs the source. Must be one of the following:
|
description STRING |
The description of the connection property. By default, copy similar to the following will display for any connection property, depending on its
If there’s any other info you want to include, you can include it in this field using Markdown or HTML. Otherwise, this can be left blank. |
uses-common-fields BOOLEAN |
If This includes attributes like |
Form attributes
The attributes contained in the object’s form
connection step. These are the attributes required to configure the connection in Stitch.
This is an example of Form property documentation.
Nearly every connection property shares some common attributes depending on its form-type
. For example: Almost all source connection properties source have anchor_time
and frequency_in_minutes
attributes. The data for these shared attributes can be found in the following files:
- Common for all sources:
_data/connect/common/all-souces.yml
- Common for databases:
_data/connect/common/database-sources.yml
- Common for destinations:
_data/connect/common/destination-forms.yml
This part of a connection property’s data file only needs to be included if its report card contains attributes specific to it. For example: If a report card only contains anchor_time
and frequency_in_minutes
attributes, this section isn’t required.
Each item in the object-attributes
list must contain the following attributes:
Parameter | Description |
name STRING |
The name of the attribute as it appears in the report card. Note: Case must be retained. This means that if the attribute’s name contains upper- and lower-case characters in the report card, the value of this parameter must match. Example values:
|
type STRING |
The attribute’s data type. |
required BOOLEAN |
If |
description STRING |
A description of the attribute, which can be written in Markdown or HTML.
|
value STRING |
An example value of the attribute. This is used in the example JSON object for the form property. |
OAuth attributes
Note: This is only required if a source or destination supports OAuth via the API, that is, if the connection property object contains an oauth
connection step object.
This is an example of OAuth property documentation.
Each item in the oauth-attributes
list must contain the following attributes:
Parameter | Description |
name STRING |
The name of the attribute as it appears in the report card. Note: Case must be retained. This means that if the attribute’s name contains upper- and lower-case characters in the report card, the value of this parameter must match. Example values:
|
type STRING |
The attribute’s data type. |
required BOOLEAN |
If |
credential BOOLEAN |
If |
description STRING |
A description of the attribute, which can be written in Markdown or HTML.
|
value STRING |
An example value of the attribute. This is used in the example JSON object for the connection property. |
Back to top
Last updated: 28 July 2021