For the complete documentation index, see llms.txt. This page is also available as Markdown.

Publish an integration

post
Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
integrationNamestring · max: 100Required

Name of the integration.

Pattern: ^[a-zA-Z0-9-_.]+$
Body
runtimestring · enumOptional

The runtime version to use for the integration. If not specified, the integration will use the default runtime.

Default: v1Possible values:
iconstring · byteOptional

Base64 content of the icon

titlestring · min: 2 · max: 30Required

Title of the integration

descriptionstring · max: 100Required

Description of the integration

summarystring · max: 2048Optional

Long form markdown summary of the integration

previewImagesstring · byte[] · max: 3Optional

Base64 content of the image

visibilitystring · enumOptionalPossible values:
targetstring · enumOptional

Allowed installation target for the integration. If not specified, the integration can be installed at all targets (org, spaces etc)

Possible values:
scriptstringRequired

Content of the script to use

organizationstringRequired

The ID or subdomain of the organization under which the integration should be published

contentSecurityPolicyone ofOptional

Security policy to validate the content of the integrations scripts and Contentkit. Will be sent as headers when processing the script fetch event and the blocks fetch events.

stringOptional
or
Responses
200

OK

application/json
objectstring · enumRequiredPossible values:
namestringRequired

Unique named identifier for the integration

versionnumberRequired

Version of the integration

titlestring · min: 2 · max: 30Required

Title of the integration

descriptionstring · max: 100Optional

Description of the integration

summarystring · max: 2048Optional

Long form markdown summary of the integration

previewImagesstring[] · max: 3Required

URLs of images to showcase the integration

targetstring · enumRequired

The target on which the integration can operate and needs to be configured for

Possible values:
verifiedbooleanRequired

If true, the integration has been verified by the GitBook team

visibilitystring · enumRequiredPossible values:
contentSecurityPolicyone ofOptional

Security policy to validate the content of the integrations scripts and Contentkit. Will be sent as headers when processing the script fetch event and the blocks fetch events.

stringOptional
or
post/integrations/{integrationName}

Last updated

Was this helpful?

Powered by GitBook