Confluence
Collaborationsystem_type: "confluence"Proxy Confluence REST API v2 calls for pages, spaces, and attachment encryption.
Overview#
The Confluence connector proxies Atlassian Confluence Cloud REST API v2 calls. API tokens sealed in QuantaVault are used for HTTP Basic authentication. Supports page CRUD, space management, and content search.
https://api.quantaseal.io/api/v2/proxy/outboundAuth header:
X-API-Key: qs_live_…Prerequisites#
- 1A Confluence Cloud account
- 2An Atlassian API token
- 3Your Confluence base URL (e.g. https://your-org.atlassian.net)
Configuration#
Follow these steps to connect Confluence to QuantaSeal. You can configure integrations via the Admin Console or directly via the API.
- 1
Create an Atlassian API token at id.atlassian.com → Security → API Tokens.
- 2
Seal: POST /api/v2/vault/seal with credential_type: basic_auth.
- 3
Create integration with system_type: confluence, config: {base_url: 'https://your-org.atlassian.net'}.
Authentication Types#
Same as Jira — HTTP Basic Auth with email + API token. Seal as basic_auth credential.
All credential types are sealed in QuantaVault with ML-KEM-768 + AES-256-GCM and wrapped by your tenant AWS KMS CMK before storage. See the Vault API reference for the full list of credential types and seal/unseal endpoints.
Available Operations#
QuantaSeal enforces a default-deny operation policy. Only operations listed in your integration's allowed_operations array will be permitted. Add operations when creating or updating the integration.
| Operation | Description |
|---|---|
get_page | Retrieve a Confluence page by ID. |
create_page | Create a new page in a space. |
update_page | Update page content and title. |
search_content | Search pages using CQL (Confluence Query Language). |
list_spaces | List all accessible spaces. |
Code Example#
Every proxy call returns a HybridCryptoEnvelope - the response is ML-KEM-768 key-encapsulated, AES-256-GCM encrypted, and signed with ML-DSA-65 + HMAC-SHA-512. Verify both signatures before trusting the decrypted payload.
curl -X POST https://api.quantaseal.io/api/v2/proxy/outbound \
-H "X-API-Key: qs_live_your_key_here" \
-H "Content-Type: application/json" \
-d '{"integration_id":"int_CONF001","operation":"search_content","payload":{"cql":"space = ENG AND type = page AND text ~ \"security policy\"","limit":10}}'client.encryption.decrypt(envelope). Both the ML-DSA-65 signature and the HMAC-SHA-512 signature must pass - QuantaSeal uses a bitwise & check, not short-circuit and.Troubleshooting#
401 Unauthorized
API tokens are scoped to the user's permissions. Ensure the user account has read access to the spaces you are querying.