Validate Integration Creation

Header Parameters

x-workspace-id*string

Workspace ID

x-multiple-integrations?string

Whether the client supports bots with multiple instances of the same integration. Set to "true" to receive integration instances keyed by their alias instead of their id. This header will be removed in the future, and the API will always return multiple instances keyed by alias.

Request Body

application/json

Integration

TypeScript Definitions

Use the request body type in TypeScript.

name*string

Name of the Integration

Lengthlength <= 200

version*string

Version of the Integration

Lengthlength <= 200

configuration?

Default configuration definition of the integration

configurations?

Additional configuration definitions of the integration

states?

events?

actions?

entities?

identifier?

channels?

user?

interfaces?

extraOperations?

EXPERIMENTAL Extra integration operations that should be sent or not to the integration instances. The key is the operation name.

sdkVersion?string

Lengthlength <= 200

secrets?

Secrets are integration-wide values available in the code via environment variables formatted with a SECRET_ prefix followed by your secret name. A secret name must respect SCREAMING_SNAKE casing.

code?string

JavaScript code of the integration

url?string

URL of the integration

dev?boolean

Indicates if the integration is a development integration; Dev integrations run locally

icon?string

Base64 encoded svg of the integration icon. This icon is global to the integration each versions will be updated when this changes.

readme?string

Base64 encoded markdown of the integration readme. The readme is specific to each integration versions.

title?string

Title of the integration. This is the name that will be displayed in the UI

Length1 <= length <= 64

description?string

Description of the integration. This is the description that will be displayed in the UI

Lengthlength <= 256

public?boolean

Deprecated

[DEPRECATED] Indicates whether the integration is public. Please use the "visibility" parameter instead.

visibility?string

The integration's visibility. Public integrations are available to all and cannot be updated without creating a new version. Unlisted integrations behave identically to public integrations, but they are not listed in the integration hub. By default, integrations are private and only accessible to the workspace that created them.

Value in

"public"
"private"
"unlisted"

layers?array<string>

attributes?

Optional key-value attributes from the integration definition

Response Body

`application/json`

curl -X POST "https://example.com/v1/admin/integrations/validate" \  -H "x-workspace-id: string" \  -H "Content-Type: application/json" \  -d '{    "name": "string",    "version": "string"  }'

{}

{}

Validate Integration Creation

Header Parameters

Request Body

Response Body

200application/json

defaultapplication/json

`application/json`

`application/json`