Changelog

Introducing API Proxy Transformation, which helps modernize your APIs and increase robustness of your API integrations with:

• Intuitive Transformation Editor: Effortlessly configure request and response transformations with drag-and-drop functionality.
• Schema Mapping & Key-Value Mapping: Define schemas, map data, and apply formulas for seamless data transformation between systems.
• Conditional Response Mapping: Route API responses based on HTTP status codes with conditional logic to improve error handling and flexibility.
• In-Line Formulas: Dynamically adjust data types and values for greater adaptability across APIs.

Benefits: Faster integrations, reduced development effort, enhanced compatibility, and secure data transformations.

This feature is in private release. Contact your Customer Success Manager to enable this feature.

API collections and endpoints have been updated with the following UI enhancements:

• Updated endpoint UI to include request & response schema, recipe actions, and key endpoint configuration that previously required opening the recipe separately to see
• New endpoint settings tab to provide a persistent view of key endpoint configuration settings, without having to navigate into the 'edit endpoint' pop-up
• Updated collections UI with new icons to easily distinguish API recipe collections and API proxy collection

The new Recipe Operations triggers for policy quota and rate limit violations are instrumental in giving administrators visibility and the ability to proactively monitor their client's API usage. With these new triggers, administrators can now receive active alerts about violations, and move quickly to address.

With this new settings menu, you can control how to handle requests during periods of high concurrency - to either queue requests and set queue sizes, or reject requests when the limit is reached. Additionally, our concurrency documentation has been updated to provide more insight on how concurrency works, and how to use these new settings to manage your concurrency strategy.

Users can now create API proxy collections that serve as an intermediary between an API client and an existing API server.

Rather than clients sending requests directly to your API, they can send requests to a secure proxy endpoint configured in Workato. This extends the benefits of Workato's modern API gateway to your existing API servers, including secure authentication protocols, monitoring, and access control features.

API Proxy is a lightweight service built for handling high volume with low latency. Highlights include:

• Simple configuration via Workato UI
• High capacity (upwards of 10k RPS)
• Low latency of 5ms
• No concurrency limit

This feature is available to all API Platform customers.

You can now increase timeout durations—from the default 30 seconds, up to 240 seconds for the endpoints that need it. Just note that this works only for endpoints created on the API platform.

API requests that exceed the workspace’s concurrency limit will no longer be rejected. Instead, when API requests spike, API throttling will come into play. This will delay the requests a little, depending on their size.

We introduced API Clients for Developer APIs this January, which allows users to grant clients granular role and project-based app access. It’s now enhanced with:

• IP Whitelisting
• Developer APIs to manage API clients
• Support for project-level lookup tables, project properties, API Platform collections and API Platform Clients
• Recipe Operator connector support for API Client tokens

See API Clients’ documentation for more.

With API Clients, users can now grant clients granular role and project-based app access. For greater security, view-once tokens are now available. Read this update’s documentation, or go to the revamped Workspace Access to start configuring.

The enhanced recipe API allows resetting one or more recipes either manually on an ad-hoc basis or through automations. Resetting a trigger makes it forget the data that it has picked up in the past so it will pick up the same historical data again. This is a great way to do a full data refresh for data replication, master data management, or reverse ETL type of use case.  Click to learn more about reset API.