nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Public App Access Settings API not available for our organization – bulk management of Approved Doma

Anja Treis

Hello Atlassian Community,

we are currently setting up Jira Service Management as a customer knowledge portal and would like to manage our Approved Domains / App Access Settings programmatically.

Our goal is to onboard approximately 15–50 customer domains. For each approved domain, we want to configure the same access settings:

Jira Service Management: Customer
Confluence: No access
Other Atlassian apps: No access
Organization admin notification: Notify when users get access

We created an Organization Admin API key without scopes and successfully verified that the key and organization ID are valid.

The following request works successfully:

GET <a href="https://api.atlassian.com/admin/v1/orgs" rel="noopener nofollow noreferrer" target="_blank">https://api.atlassian.com/admin/v1/orgs</a>

However, when calling:

GET <a href="https://api.atlassian.com/admin/v2/orgs/%7BorgId%7D/app-access-settings/domains" rel="noopener nofollow noreferrer" target="_blank">https://api.atlassian.com/admin/v2/orgs/{orgId}/app-access-settings/domains</a>

we receive the following response:

{
  "code": "not-found",
  "message": "Public app access settings API is not available for this org"
}

Could you please clarify:

Is the Public App Access Settings API currently available only for selected organizations or plans?
Can this API be enabled for our organization?
Are there any prerequisites or feature flags that need to be enabled?
Is there another supported API or bulk-import method for creating and managing Approved Domains?
Does the API support configuring the organization admin notification option “When users get access”?
If yes, which API property represents this notification setting?

Our Atlassian Cloud site is:

<a href="https://lunnebachit.atlassian.net" rel="noopener nofollow noreferrer" target="_blank">https://ourcompany.atlassian.net</a>

We would prefer to use the supported Admin API instead of manually creating and configuring up to 50 customer domains individually.

Thank you for your assistance.

Best regards, Anja

Accepted answers

Marc -Devoteam-

Hi @Anja Treis

Welcome to the community.

No, the option for API "App Access Settings" relates to what 3rd party asps can do in JIra or Confluence. This does not relate to the setting "App Access" in Atlassian Administration
No as there is no such public endpoint.
No
No, there is not. This can only be done via the the GUI
No

All comments

Marc -Devoteam-

Hi @Anja Treis

Welcome to the community.

No, the option for API "App Access Settings" relates to what 3rd party asps can do in JIra or Confluence. This does not relate to the setting "App Access" in Atlassian Administration
No as there is no such public endpoint.
No
No, there is not. This can only be done via the the GUI
No

Anja Treis

Thank you for your reply.

However, I believe there may be a misunderstanding regarding the API we are referring to.

According to the official Atlassian Cloud Admin changelog from May 22, 2026, Atlassian introduced APIs specifically for managing approved-domain app access settings programmatically.

The documented endpoints include, among others:

POST /admin/v2/orgs/{orgId}/app-access-settings/domains

and the corresponding GET endpoint under:

/admin/v2/orgs/{orgId}/app-access-settings/domains

This appears to relate directly to the Approved Domains / App access settings section in Atlassian Administration, rather than to third-party app/API access.

In our case, authentication works correctly and we can successfully call:

GET <a href="https://api.atlassian.com/admin/v1/orgs" target="_blank" rel="nofollow noopener noreferrer">https://api.atlassian.com/admin/v1/orgs</a>

However, the App Access Settings endpoint returns:

{
  "code": "not-found",
  "message": "Public app access settings API is not available for this org"
}

So the API itself appears to exist, but it is apparently not available for our organization.

Could you please clarify whether you know what determines the availability of this API for an organization?

For example:

Is it still being rolled out gradually?
Is it limited to specific plans or organization configurations?
Does it require a particular feature to be enabled?
Is there any known prerequisite for an organization to access these endpoints?

The relevant Atlassian changelog entry is dated May 22, 2026 and is titled “Manage approved-domain app access settings with APIs.”

We would mainly like to understand why the API responds with “not available for this org” in our case.

Thank you!

Marc -Devoteam-

Hi @Anja Treis

It seems you are correct, it could be still rolling out or be retracted or this is not available for Free instances.

This 3 are added,:

POST /admin/v2/orgs/{orgId}/app-access-settings/domains — Register a new approved domain for the org, optionally with an initial set of product configurations.
PUT /admin/v2/orgs/{orgId}/app-access-settings/domains/{domain} — Replace the per-product configuration on an existing domain (full replace; products not in the request body are removed).
POST /admin/v2/orgs/{orgId}/app-access-settings/domains/{domain}/products — Add or update a single product configuration on a domain, leaving any other products on that domain untouched.

There is no GET option added, you need to use existing GET options, as mentioned in the changelog bulletin.

Anja Treis

Hi Marc,

Thank you for the clarification.

We are currently using the free version of Atlassian Administration, although the individual Atlassian Cloud instances/products themselves are, of course, paid.

So I assume that either the rollout of these API endpoints has not yet been completed for all organizations, or that the App Access Settings API is not available for organizations using the free administration tier.

For the time being, I have configured the approved domains and the corresponding app access settings manually via the GUI.

Thanks again for checking and for pointing out the distinction regarding the existing GET endpoints.

Best regards,
Anja

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

api

jira-service-management-cloud

jira-service-management

organization-administration