Confluence | Operate As Docs

Website: atlassian.com/software/confluence
Connects by: Signing in with Atlassian
Category: Files and docs
Part of: Atlassian
Tools: 124

Service	Key	Base URL
Confluence	`confluence`	`https://api.atlassian.com/ex/confluence/{cloud_id}`

Connecting

Your client presses Connect on their link and approves on Atlassian's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "confluence"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "confluence"    ]  }]

Permissions

What the client reads	Permission it asks for
See the names of your spaces	`read:confluence-space.summary`
See pages and blog posts	`read:confluence-content.all`
Create and edit pages and blog posts	`write:confluence-content`

Tools

Install Confluence's typed package for your language:

pip install operate-as-confluence

pip install operate-as-confluence

Run confluence.add_content_watcher

curl -X POST https://api.operate.as/v1/actions/confluence.add_content_watcher \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "content_id": "<content_id>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/confluence.add_content_watcher \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "content_id": "<content_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/confluence.add_content_watcher

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://api.atlassian.com/ex/confluence/{cloud_id}, with the parts in braces filled in from your client's account. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../confluence/..." \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../confluence/..." \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Atlassian refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's Atlassian access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Atlassian access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "atlassian",
    "services": [
      "confluence"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "atlassian",    "services": [      "confluence"    ],    "reconnectUrl": "https://…"  }}