Heads up
This is a pre-release list of features for Celigo platform version 2026.7.1 scheduled for incremental release July 6 – 9, 2026.
APIs now participate in the same Integration Lifecycle Management model as flows - with full support for revisions, cloning, pull/ merge, and environment promotion.
Until now, APIs lived outside the integration lifecycle — teams couldn't snapshot, clone, or promote API changes alongside their flows. This forced manual tracking, increased the risk of configuration drift across environments, and slowed down teams iterating on APIs and flows together.
With full ILM support, APIs now follow the same workflows teams already use for flows. Environment promotions are safer because APIs travel with the integration bundle, parallel development works because clones capture complete integration state, and rollbacks are reliable because revisions include APIs — not just flows. For teams operating across multiple environments or coordinating API changes across developers, this eliminates a significant operational gap.
All users managing APIs within integrations will be able to use this functionality. The following platform capabilities are added to manage the API lifecycle in an Integration tile:
-
Revisions: Create a snapshot/revision for an integration including APIs. Revert to a previous snapshot which restores the API state along with flows.
Download/upload: Download and upload integration bundles (.zip) that include APIs, with source IDs preserved.
-
Cloning: Clone an API within an integration, or clone an entire integration containing APIs.
-
Pull/merge: Promote API changes from a clone to the original integration using the same pull/merge workflow used for flows. A new APIs section appears on the Review Changes page, and changed API details are visible in the "View resource changed" tab.
-
Parallel development: Multiple clones can be used for parallel API development without relying on external tracking - the same pattern teams already use for flows.
-
Configurable ignore fields: Selected API fields (name, version, relative URI) can be excluded from pull/merge to avoid overwriting environment-specific values.
You can now create and manage APIs directly inside an integration using the new APIs tab.
-
Manage access: Create, edit, delete, clone, move, group, and download APIs within an integration
-
Monitor access: View APIs, request logs, audit logs, and OpenAPI specs
-
Account admins & owners: No changes
-
Clone APIs within the same integration or across integrations
-
Move APIs between integrations (where you have access)
-
Create API groups to organize related APIs
-
Download a single API or an entire integration (including APIs, flows, and tools) as a ZIP file
-
Upload a ZIP file to create an integration with all included APIs and resources
-
When creating an API outside an integration, you can now choose to create it within a new or existing integration
This release introduces the following enhancements to API builder and API Management:
-
Configurable API timeouts: Override the default 120-second timeout for APIs built in API Builder, configurable at both the account and individual API levels. This helps prevent any degraded performance and enables client applications to retry or fail over gracefully when there’s a timeout.
-
Flexible versioning support: Use select special characters, such as dots and underscores, in the Version field to better align with semantic versioning standards.
-
In-context script execution logs: View script execution logs directly within API Builder, eliminating the need to switch to the Scripts page.
-
Step-level runtime debugging: Enable and view runtime debug logs for specific steps in API Builder to quickly isolate and troubleshoot issues.
-
Accurate cURL-based external testing: When importing cURL into external API testing tools such as Postman or Bruno, all request parameters – including headers, query parameters, and the request body - are automatically populated for seamless testing.
-
Updated routing configuration in APIM Console: Automated routing configuration and policies in the API Management console to ensure API requests are consistently routed to the correct backend service endpoints.
-
Enhanced Push to APIM options: Ability to configure multi-segment context paths, and support for pushing APIs with the PATCH method to API Management.
You can now keep track of your API entitlements and monitor your usage without leaving the Celigo platform. Navigate to Account > Subscription to track your API call usage, including the following activity:
-
Custom APIs built with API Builder or JavaScript
-
Import and export APIs
-
APIs proxied in API Management
You’ll also see a breakdown of API call usage, allowing you to sort and filter by environment and API type (API builder, JavaScript, or other resources), to identify your most frequently used APIs and uncover valuable insights.
Each account includes a built-in monthly allotment of API calls, with the flexibility to scale through additional API call add-ons or API Management. Historical usage data is also available, making it easy to choose the plan that best fits your needs.