Operations for retrieving destination type schemas.
List Destination Type Schemas (for Tenant)
Returns a list of JSON-based input schemas for each available destination type. Requires Admin API Key or Tenant JWT.
path Parameters
tenant_id
string · requiredThe ID of the tenant. Required when using AdminApiKey authentication.
Responses
type
stringlabel
stringdescription
stringicon
stringSVG icon string.
instructions
stringMarkdown instructions.
remote_setup_url
string · urlSome destinations may have Oauth flow or other managed-setup flow that can be triggered with a link. If a
remote_setup_url
is set then the user should be prompted to follow the link to configure the destination. See the dashboard design guide for recommended UI patterns and wireframes for implementation in your own app.config_fields
object[]Config fields are non-secret values that can be stored and displayed to the user in plain text.
credential_fields
object[]Credential fields are secret values that will be AES encrypted and obfuscated to the user. Some credentials may not be obfuscated; the destination type dictates the obfuscation logic.
Get Destination Type Schema (for Tenant)
Returns the input schema for a specific destination type. Requires Admin API Key or Tenant JWT.
path Parameters
tenant_id
string · requiredThe ID of the tenant. Required when using AdminApiKey authentication.
type
string · enum · requiredThe type of the destination.
Enum values:webhookaws_sqsrabbitmq
Responses
type
stringlabel
stringdescription
stringicon
stringSVG icon string.
instructions
stringMarkdown instructions.
remote_setup_url
string · urlSome destinations may have Oauth flow or other managed-setup flow that can be triggered with a link. If a
remote_setup_url
is set then the user should be prompted to follow the link to configure the destination. See the dashboard design guide for recommended UI patterns and wireframes for implementation in your own app.config_fields
object[]Config fields are non-secret values that can be stored and displayed to the user in plain text.
credential_fields
object[]Credential fields are secret values that will be AES encrypted and obfuscated to the user. Some credentials may not be obfuscated; the destination type dictates the obfuscation logic.
List Destination Type Schemas (JWT Auth)
Returns a list of JSON-based input schemas for each available destination type (infers tenant from JWT).
Responses
type
stringlabel
stringdescription
stringicon
stringSVG icon string.
instructions
stringMarkdown instructions.
remote_setup_url
string · urlSome destinations may have Oauth flow or other managed-setup flow that can be triggered with a link. If a
remote_setup_url
is set then the user should be prompted to follow the link to configure the destination. See the dashboard design guide for recommended UI patterns and wireframes for implementation in your own app.config_fields
object[]Config fields are non-secret values that can be stored and displayed to the user in plain text.
credential_fields
object[]Credential fields are secret values that will be AES encrypted and obfuscated to the user. Some credentials may not be obfuscated; the destination type dictates the obfuscation logic.
Get Destination Type Schema (JWT Auth)
Returns the input schema for a specific destination type (infers tenant from JWT).
path Parameters
type
string · enum · requiredThe type of the destination.
Enum values:webhookaws_sqsrabbitmq
Responses
type
stringlabel
stringdescription
stringicon
stringSVG icon string.
instructions
stringMarkdown instructions.
remote_setup_url
string · urlSome destinations may have Oauth flow or other managed-setup flow that can be triggered with a link. If a
remote_setup_url
is set then the user should be prompted to follow the link to configure the destination. See the dashboard design guide for recommended UI patterns and wireframes for implementation in your own app.config_fields
object[]Config fields are non-secret values that can be stored and displayed to the user in plain text.
credential_fields
object[]Credential fields are secret values that will be AES encrypted and obfuscated to the user. Some credentials may not be obfuscated; the destination type dictates the obfuscation logic.