This page includes release notes and updates for the Customer Service Management REST API. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates.
🛠️ Scheduled maintenance window from September 25 @ 5PM PST to Monday, September 28 @ 10AM, AEST
Our support portal is moving to a new home. New ticket submissions and ticket access including comments via email will be unavailable during this window. Starting September 28, submit all requests at Atlassian Support and update your bookmarks. Learn what's changing.
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.
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.
We’ve added a new API to allow callers to raise an existing issue on a CSM support site.
API callers can now share an existing issue to a support site for customers to see. The Summary and Description of the provided issue are shared with the customer on the support site.
Callers can now have up to 10 unfinished tasks queued up, increasing the limit from the existing 5.
API callers can now have up to 10 unfinished tasks. See https://developer.atlassian.com/cloud/customer-service-management/bulk-apis/#key-concepts to understand key concepts regarding visibility on tasks.
We’ve added new APIs to bulk create detail field definitions for both customers and organizations
Refer to API quick start for information on how to get started with the CSM REST API.
We’ve added a new experimental API to fetch entitlements in a paginated form.
Refer to API quick start for information on how to get started with the CSM REST API.
We’ve added experimental CSM REST APIs for deleting individual customers and organizations:
Refer to API quick start for information on how to get started with the CSM REST API.
We added new experimental APIs for managing customers and organizations are now available. This release includes:
Simple APIs — Create, read, update, and delete individual entities
Bulk APIs — Manage multiple entities in a single request (our first async APIs for CSM)
Task APIs — Track the status of long-running async operations
The new experimental APIs are as the following:
These APIs introduce a new model for configuring customer and organization profiles. This is also the first release of asynchronous bulk APIs for CSM customer context.
For bulk operations, include the Idempotency-Key header in your requests. See the Bulk APIs guide for implementation details.
EDIT 12 Feb, 2026: This RFC is now closed.
A new RFC is ready for review at: https://community.developer.atlassian.com/t/rfc-123-csm-extensibility-on-forge/98412
Jira Administrators can now control which users can edit detail field values. Permission settings that Jira Administrators apply in the Manage Details UI for organizations, customers and entitlements will be enforced in the APIs as well.
The default permissions will allow Agent Users to edit fields. When a Jira Administrator sets a detail field edit capability to Admin Only, then Agent Users will receive a permissions error response when trying to update such a field value via the API.
We're announcing new IP ranges that will soon be available for requests from external clients, such as browsers and API integrations:
13.35.248.0/24
13.227.180.0/24
13.227.213.0/24
These ranges won't be used to make outgoing connections from Atlassian Cloud to remote systems, for example, webhooks.
To prepare for this change, update your firewalls and other security measures to allow connections to the new IP ranges.
For more information, see IP addresses and domains for Atlassian Cloud products, which includes instructions on how to receive notifications of changes, as well as links to machine-readable lists of our IP ranges.
We've released new APIs that allow you to manage (create, read, edit, delete) detail fields for organizations, customers and entitlements. We’ve also added APIs for managing products and entitlements.
Rate this page: