Skip to main content

Atlassian Organization Audit connector setup

Polls audit log events from the Atlassian Organizations REST API (GET /orgs/{orgId}/events-stream).

What you need first​

RequirementDetails
Atlassian accessOrganization administrator
Organization IDUUID for your Atlassian organization
API keyCloud Admin API key with access to audit events

1. Create an API key and copy your organization ID​

  1. Sign in to Atlassian Administration.
  2. Go to Settings → API keys (or API access depending on your admin UI).
  3. Click Create API key.
  4. Name the key (e.g. Perpetual Atlassian Audit).
  5. Assign the read:events:admin scope (required for the events stream endpoint).
  6. Complete two-factor authentication if prompted.
  7. Copy the API key and Organization ID. Atlassian shows the secret only once — store both securely.

To find your organization ID later: Settings → Organization settings (or the API key creation flow displays it).


2. Perpetual credential​

  1. Log in to Perpetual. Open Settings from the user/org control at the bottom left of the sidebar (click your name → Settings), then go to Credentials → New Credential.
  2. Choose Text.
  3. Fill in:
FieldValue
NameUnique identifier using letters, digits, and underscores only (e.g. atlassian_org_audit).
Allowed URL patterns*.atlassian.com
ValueAPI key from step 1 (used as a Bearer token)
  1. Save the credential.

3. Create the Atlassian Organization Audit connector​

  1. Go to Datasets → Connectors → Create Connector.

  2. Select Atlassian Organization Audit.

  3. Connector name: unique identifier (letters, numbers, underscores).

  4. Configure:

    • Atlassian API access: select the credential from step 2.
    • Poll interval (minutes): default 5.
    • Organization ID: the org UUID from step 1.
  5. Optionally check Deploy, then save.

First run backfills roughly the last 24 hours of audit events, then advances the stream cursor on subsequent polls.


Operational notes​

  • Key rotation: Create a new API key, update the Perpetual credential, verify runs succeed, then revoke the old key.
  • Rate limits: The connector retries 429 and 5xx responses with backoff; very large backfills may span multiple runs.

Reference​