Customer Experience access APIs and Atlassian Accounts in customer profiles

New experimental APIs let you list, grant, and remove organizations’ access to an organization-restricted Customer Experience.

Customer profile and bulk APIs now accept eligible Atlassian Accounts as customers. You can retrieve their profiles and update their detail fields, organization associations, and product associations using their Atlassian account ID as customerId. The account must be active, have the CSM Customer role, and be neither a CSM agent nor a Jira site admin. Customer Account creation and lifecycle APIs continue to manage Customer Accounts only.

More details

Use the new Customer Experience access APIs to list organizations with access, grant access to up to five existing organizations per request, or remove an organization’s access. These experimental APIs require X-ExperimentalApi: opt-in and apply to Customer Experiences already configured for organization-restricted access. The caller must be able to administer the Customer Experience.

The customer profile and customer bulk APIs accept eligible Atlassian Accounts using their Atlassian account ID as customerId. This covers profile reads and bulk updates to detail fields, organization associations, and product associations. The account must be active, have the CSM Customer role, and be neither a CSM agent nor a Jira site admin. Profile creation and Customer Account lifecycle operations still create or manage Customer Accounts; the bulk profile API cannot change an Atlassian Account’s display name. See Supported customer IDs.