Changelog

Simplified security scopes for the Event Subscription API, by consolidating multiple scopes into a single, streamlined scope.

• New scope:

  • intelligence.knowledge-models:read

• Replaces:

  • triggers:read
  • triggers:manage
  • knowledge-models:query

You can find the required scopes defined in the updated documentation: Getting Started

Version 2.0 of the Celonis Audit Log and Celonis Platform Adoption APIs has been released. With this new version, both APIs now offer token-based/cursor-based pagination. The request parameters in Version 2.0 include pageToken and limit, with limit having a default value of "200", a minimum of "1", and a maximum of "500". The response models for both new versions return cursor-based data that includes a nextPageToken.

The new versions of these APIs provide:

• Better performance for large datasets.
• More stable pagination when new events are ingested.
• Higher per-request limit support (up to 500 records).

For more information, see Celonis Audit Log API (v2.0) and Celonis Platform Adoption API (v2.0).

We’ve updated the AI API to support Structured Outputs! You can now configure Process Copilot to return specific JSON data alongside standard text responses. This makes it easier to trigger Action Flows or update UI components directly from an Agent's response.

Check the updated endpoint: Conversation Endpoint.

We're enhancing the security of your integration with the Event Subscription API. Previously it used a singular intelligence.subscriptions:manage scope. To ensure that integrations have access only to the resources they truly need this is the list of scopes required currently:

• intelligence.subscriptions:manage
• triggers:read & triggers:manage
• knowledge-models:query

You can find the required scopes defined in the updated documentation: Getting Started

• The Agent Tools (MCP) Asset has been released in General Availability (GA).
• This asset was formerly named the Model Context Protocol (MCP) Server Asset and was released into Private Preview in November of 2025.
• This feature enables AI agents to securely access and interact with Celonis data and insights through the Model Context Protocol.
• Provides ready-to-use tools that AI agents can use to search for relevant information, get real-time process context, trigger actions in external systems, and write decisions back to Celonis.

For more information, see the Agent Tools (MCP) Asset Overview.

• We have refined how the Chat API is enabled to improve security and visibility.
• You must now enable the External Use in the Process Copilot asset in Studio to connect the Process Copilot to third-party applications via this API.
• Check the updated Getting Started page for the full enablement checklist.

• The Tools API has been removed from the AI API portfolio. To expose Celonis data retrieval and actions to third-party platforms like Microsoft Copilot Studio or Agentforce, please use the new MCP Server Asset in Studio. This provides a more secure, standardized way to integrate Process Intelligence into your AI ecosystem via the Model Context Protocol.
• For more information, see the MCP Server Asset Overview.

• The Permissions API has been released in General Availability (GA).
• This API enables you to query permissions for a Celonis Platform team and then extract this data to provide insights into access management for your team.
• The extracted permissions data can be imported into the Celonis Platform as a data model and then used to create custom views in Studio.

For more information, see Permissions API.

• The Agent Tools (MCP) Asset has been released in Private Preview.
• This feature enables AI agents to securely access and interact with Celonis data and insights through the Model Context Protocol.
• Provides ready-to-use tools that AI agents can use to search for relevant information, get real-time process context, trigger actions in external systems, and write decisions back to Celonis.

For more information, see the MCP Server Asset Overview.

• The Intelligence API has been renamed to the Knowledge Model API! This is a name-only change, you can continue using the API as usual - all functionality remains the same.

• The Standard Data Ingestion API has been released in General Availability (GA).

• The Reporting API for Celonis Process Management has been released in General Availability (GA).
• The Reporting API enables you to retrieve elements from your reporting database based on Process Designer data.
• This API also allows you to build reports and dashboards based on the CPM data in your 3rd party analytics tools.

Great news! We've just released two new endpoints in private preview: POST for KM Data Query and POST for KM Record Data Query within the Intelligence API.

This will directly address the challenges you've faced with URL length limitations when sending query parameters like filterExpr. Now, instead of breaking down large queries into many smaller requests, you can send all your query parameters (including lengthy filter expressions, pagination, and other components) within the request body.

This means you can:

• Make single, comprehensive requests for large datasets.

• Simplify your integration logic by removing the need for complex manual batching and result aggregation.

  Please note that this solution only supports the new OData semantics; legacy filtering methods are no longer supported. Filter expressions are limited only by PQL and payload length.

Please contact your account team to get early access.

We're enhancing the security of your integrations with the Process Intelligence APIs by introducing new, granular OAuth 2.0 scopes, providing more precise control over integration authorizations.

Previously, the Process Intelligence APIs used a singular studio scope, which granted broad permissions. With this update, we are moving to a more refined system of granular scopes. These new scopes allow you to define specific permissions for different actions within the Process Intelligence APIs, ensuring that integrations only have access to the resources they truly need.

You can find the required scopes defined in the updated documentation for all our APIs:

• New scopes for Intelligence API
• New scopes for Event Subscriptions API
• New scopes for AI APIs

Please, if you are using OAuth, ensure you set the required scope permissions in your OAuth Client.

API Keys will be deprecated in the coming months (as previously communicated to our customers), and we will provide ample time for you to migrate existing solutions. Find here a guide about How to migrate applications calling Celonis APIs to OAuth 2.0 from API/Application keys

• The 5,000 row limit per data set has been removed from the data retrieval endpoints Get a list of KM data and Get a list of KM Record data. Please read our updated Terms and Conditions.

• Fixed incorrect handling of dots in filter expression parameter literals

• A new value of subscription status rejected was introduced to indicate that the events, although transmitted, were rejected by the recipient due to logical or configurational problems. Action is required from the consumer side to recover the subscription. Please read more here.

• OAuth2.0 client with grant_type=authorization_code has now been released in private preview. Please contact your account team to get early access.

• The Subscription API subdomain has now been released in General Availability (GA).

• The Chat API AI subdomain has now been released in public preview.

• A new AI subdomain has been added to the Process Intelligence APIs family in private preview. Please contact your account team to get early access.
• The AI Subdomain contains:
  • The Chat API to interact with a Process Copilot built in Celonis (as described here).
  • The Tools API to access data retrieval Tools built in Process Copilot. These tools can be called within any Agent platform (as described here).

• Replay subscription capability allowing a consumer to receive again events from Celonis event queues starting from any offset (details here).

• Filter expressions according to OData syntax as described in the new filtering section. Existing customers are behind a legacy filtering feature flag and are not affected. Your account and value teams will contact you to guide you on how to change the filter expression syntax you are currently using. The legacy version will be removed at the end of May 2025. Differences between the new filtering capabilities and the legacy filtering are described here.

• Return a JSON object upon Trigger subscription creation including the subscription Id (which in the sequel will be used to manage the subscription lifecycle).
• Event contract introduced and published Outbound Webhook API Reference.

• Introduction of the concept of subscription ownership: Only the subscription owner or administrators are allowed to manage the subscription lifecycle.

• Spontaneous event is now structured as JSON object (not flat text with escaped JSON any longer)
• Event Queue Offset is published at subscription metadata and in forwarded events

• Data retrieval at Knowledge Model level (using attributes of different records - parameter fields, Key Performance Indicator(s) - parameter kpis and fuzzy search capability - parameters searchTerm,searchField and searchPrecision).

• Odata protocol for Intelligence API released in beta, with one root service per Knowledge Model, metadata service and Knowledge Model record data retrieval supporting query options: $top, $skip, $select, $orderby, $count=true and $filter

• Select distinct option for data retrieval using the parameter options=distinct.

Semantic extension endpoints for 3P Agents, including:

• OpenAPI spec endpoint per Knowledge Model (intelligence/api/knowledge-models/{{km-id}}/spec),
• Knowledge Model record query endpoint (intelligence/api/knowledge-models/{{km-id}}/records/{{record-id}}/query) and
• Knowledge Model record column statistics summary endpoint (intelligence/api/knowledge-models/{{km-id}}/records/{{record-id}}/summary).

• New generation of record-less triggers supported

• Subscriptions with configuration to skip errors introduced
• Resume without history operation added
• Last successfully emitted event timestamp added to subscription metadata

• Filtering by date bug

• Checks for parameter pollution and tampering from malicious characters in intelligence/api/knowledge-models/{{km-id}}/records/{{record-id}}/data endpoint.

• Invalid parameter values are no longer echoed in error messages for security reasons.

• Capability to use filter expression predicates like in, contains(), startswith(), endswith() added.

• Capability to use logical operators in filter expressions added.

• Number of fields per data set increased from 20 to 200.
• Result data values are typed according to KM record field types.

• Capability to filter by augmented attributes and flags added.