Confluence

This documentation for the Confluence integration describes the technical capabilities of this integration, including authorization, scopes/permissions, and utilized endpoints. For more information on how to integrate Confluence, visit our connection instructions.

Version

This integration utilizes the Confluence REST API v1.

Base URL

The base URL used for all Confluence API endpoints:

https://api.atlassian.com

Endpoints Utilized

DataGrail uses the following endpoints to authorize and test the connection:

Method	Endpoint	Purpose	Docs
GET	https://subdomain.atlassian.net/wiki/rest/api/settings/systemInfo	Validate credentials

---

Authentication & Authorization

The DataGrail Confluence integration connects using token authentication which requires an API Token.

Sensitive Credentials

Publicly exposing your API credentials can allow unauthorized access to Confluence API endpoints by a third party. DataGrail stores your API credentials encrypted and protected.

Limits

Limits in Confluence are calculated using the leaky bucket algorithm. All requests that are made after rate limits have been exceeded are throttled and an HTTP 429 Too Many Requests error is returned. Requests succeed again after enough requests have emptied out of the bucket.

• DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
• DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).

---

Capabilities

Access

DataGrail's Confluence integration provides Synchronous Access capabilities for the following supported identifier category: Email.

Data Interactions

For Access requests, DataGrail will take the following actions:

1. Search for occurrences of configured identifiers in title and text fields of Confluence pages using Confluence Query Language (CQL).

Endpoints Utilized

Method	Endpoint	Purpose	Docs
GET	/ex/confluence/cloudid/rest/api/search	Perform text searches

---