Skip to main content

Atlassian Admin

Atlassian Administration is where organization admins manage users, product access, and security across Atlassian Cloud products such as Jira and Confluence. Nexla connects to the Atlassian Organizations REST API to ingest your organizations, managed accounts with their billable status and last active date per product, product workspaces, and the organization audit log. Together these show which Atlassian products your organization runs, who holds a billable seat in each, and who has stopped using them.

Atlassian Admin icon

Power end-to-end data operations for your Atlassian Admin API with Nexla. Our bi-directional Atlassian Admin connector is purpose-built for Atlassian Admin, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Atlassian Admin or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Atlassian Admin workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Nexla authenticates to the Atlassian Organizations REST API with an organization API key. Every request is sent to https://api.atlassian.com/admin with the header Authorization: Bearer <key>. To create the credential, you need two values:

  • An organization API key, created by an organization admin in Atlassian Administration.

  • Your organization ID, which Atlassian Administration shows when you create the API key. The List Organizations endpoint template also returns it.

To create an API key, follow these steps from the Atlassian documentation:

  1. Sign in to Atlassian Administration as an organization admin, and select your organization.

  2. Go to Organization settings > API keys.

  3. Click Create API key, and choose between an API key with scopes and an API key without scopes. A key without scopes can call every Admin API, which Atlassian notes is a security risk; scopes are available for some APIs only.

  4. Enter a descriptive name, such as "Nexla", and select an expiration date. Keys can last no longer than one year.

  5. If you chose a scoped key, select the scopes you need.

  6. Review the details, and click Create.

  7. Copy the API key and the organization ID, and store them in a secure location such as a password manager. The key is shown only once.

warning

Organization API keys expire on the date you select, and a key can last no longer than one year. When the key expires, Nexla flows that use it stop working. Create a new key before the expiration date and update the credential in Nexla.

A few plan and data limits apply to the endpoints:

  • List Managed Accounts returns managed accounts only: accounts whose email address belongs to a domain your organization has verified. Accounts from other domains are not included.

  • List Audit Log Events requires Atlassian Guard Premium or Atlassian Cloud Enterprise.

  • Last active dates can be delayed by up to 24 hours.

Authenticate​

Credentials required​

API key created by an organization admin in admin.atlassian.com (Settings > API keys).

FieldRequiredSecretDescription
Organization IDYesNoYour organization ID, shown in admin.atlassian.com when you create the API key (List Organizations also returns it).
API KeyYesYesThe organization API key (sent as Authorization: Bearer <key>).

Create a credential in Nexla​

  1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Enter your organization ID in the Organization ID field. Nexla uses it to build the request URLs for every endpoint except List Organizations.

  4. Paste the API key you created in Atlassian Administration into the API Key field. Enter only the key value; Nexla adds the Bearer prefix to the Authorization header automatically.

    The API key is a secret and should be treated like a password. A key without scopes can call every Admin API for your organization. If the key is exposed, revoke it in Atlassian Administration under Organization settings > API keys and create a new one.

  5. Click the Save button at the bottom of the overlay. Nexla validates the credential by calling the Atlassian endpoint that lists the organizations the key can manage (/admin/v1/orgs). The newly added credential will now appear in a tile on the Authenticate screen during data source creation.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Atlassian Admin connector tile, then select the credential that will be used to connect to your Atlassian organization, and click Next; or, create a new Atlassian Admin credential for use in this flow.

The Atlassian Admin connector is a data source only. It reads from Atlassian Administration and does not write to it.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Atlassian Admin endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

For a SaaS license usage view, the endpoints fit together as follows: List Workspaces gives the inventory of Atlassian products in the organization; List Managed Accounts shows each person's account status, whether they hold a billable seat, and their last active date per product; Get User Last Active Dates returns the per-product detail for one account; and List Audit Log Events shows who was added, removed, or granted access over a time window.

List Organizations

Returns the organizations the API key can manage, with their IDs.

  • This endpoint has no configurable parameters.
  • Use it to look up the organization ID for your credential.

Sends GET /admin/v1/orgs and reads each organization from data. Additional pages are fetched by following the links.next URL in the response. See the Atlassian Get organizations reference.

List Managed Accounts

Returns the managed accounts in the organization with their email, account status, billable status (access_billable), last active date, and per-product access (product_access).

  • This endpoint has no configurable parameters.
  • Only managed accounts are returned: accounts whose email domain your organization has verified.

Sends GET /admin/v1/orgs/{orgId}/users and reads each account from data. Additional pages are fetched by following the links.next URL in the response. Last active dates can be delayed by up to 24 hours. See the Atlassian Get managed accounts in an organization reference.

Get User Last Active Dates

Returns the last active date in each product for one account.

  • Account ID (required): The account_id of the user, as returned by List Managed Accounts.
  • Each source fetches one account. To cover every user, use List Managed Accounts, which already includes the last active date per product.

Sends GET /admin/v1/orgs/{orgId}/directory/users/{accountId}/last-active-dates and reads the result from data. Last active dates can be delayed by up to 24 hours. See the Atlassian Directory API reference.

List Audit Log Events

Returns organization audit log events, such as users added or removed, product access changes, and admin actions.

  • This endpoint has no configurable parameters.
  • Requires Atlassian Guard Premium or Atlassian Cloud Enterprise.

Sends GET /admin/v1/orgs/{orgId}/events-stream?limit=500 and reads each event from data. Additional pages are fetched by following the links.next URL in the response. See the Atlassian Events API reference.

List Workspaces

Returns the product instances (sites) in the organization with their product type and status.

  • This endpoint has no configurable parameters.

Sends POST /admin/v2/orgs/{orgId}/workspaces with the body {"limit": 1000} and reads each workspace from data. This template makes a single request and does not follow further pages. See the Atlassian Workspaces API reference.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration​

Atlassian Admin data sources can also be manually configured to ingest data from any valid Atlassian Organizations REST API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Atlassian Organizations REST API endpoints follow the pattern https://api.atlassian.com/admin/v1/orgs/&lt;organization ID>/<resource>, and most list endpoints return their records under data (path to data $.data[*]) with the next page URL in links.next. The Authorization: Bearer header is added automatically by your credential. For more information, see the Atlassian Organizations REST API introduction.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Atlassian Admin data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.