Skip to main content
Upcoming release — Zylon 1.58These docs are published ahead of release so you can prepare your API integrations. The release image is not yet available. For installations running 1.57, use the 1.57 documentation.
Confluence integrations are stored as artifacts. The integration identifier used by these endpoints is the integration artifact ID.

Prerequisites

Enable Confluence at the instance level first. See Confluence integration setup. For Confluence Cloud, create or reconnect the integration through the login flow documented in OpenID & OAuth. Use the artifact endpoints below after OAuth creates the integration artifact.

Get a Confluence integration

This endpoint returns public artifact metadata. It never returns access tokens, passwords, or other private properties.

Start a Confluence ingest

The endpoint returns a server-sent event (SSE) stream. space_ids contains the Confluence spaces to ingest and is used for both Confluence Cloud and ConfluenceLocal.

Create a ConfluenceLocal integration

ConfluenceLocal uses basic-auth credentials instead of OAuth. Send credentials only in private_props; artifact responses do not return them.
The response is an artifact object with type: "Integration" and source: "ConfluenceLocalLegacy", like the public artifact response above.

Update ConfluenceLocal credentials

Only the integration creator or an administrator can update private properties.

Errors and edge cases

  • 400: invalid provider fields or ingest parameters.
  • 403: integration not enabled, missing permission, or caller cannot update private properties.
  • 404: integration artifact or project not found, or they do not belong together.