Changelog

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:

• Organization Simple APIs

• Organization Bulk APIs

• Customer Simple APIs

• Customer Bulk APIs

• Task APIs

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.

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.

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.