Release 13.5 – April 2026
LearningBuilder version 13.5 delivers a major expansion of the API Specifications feature, giving administrators powerful new ways to create, test, and configure API-driven integrations. This release also includes improvements to Member and Edit Role Workflow handling, along with several other configuration and usability enhancements.
API and Integration Enhancements
A recurring theme across this release is extending what LearningBuilder Administrators can do with third-party integrations on their own, without needing the Heuristics team to perform configuration. Release 13.5 extends the API Specifications feature with authentication, testing, and a more streamlined way to set up integrations that call out to other systems.
- New “Manual API Call” data type expands how Administrators can make one-time API calls. This supports a range of use cases:
- Letting staff manually invoke third-party services from within a Workflow, for example, to look up or push a record to an external system as part of processing an application, without leaving LearningBuilder.
- Filling gaps where Automated Behaviors are not the right fit, such as one-off administrative actions that should stay in human hands but still benefit from being triggered inside the Workflow context.
- Administrators may also find this useful for rehearsing and testing integrations without waiting on a third-party system to send real data. This is especially valuable for exam vendor integrations, where vendor test environments can be unreliable and realistic outcomes (such as a passing exam result) often require a human to complete the exam. By simulating the inbound payload, Administrators can exercise the resulting Workflow logic on demand.
- OAuth2 Client Credentials authentication for API Specifications. API Specifications now support OAuth2 Client Credentials, one of the most common standards for securely connecting LearningBuilder to other systems. Admins can configure and test the connection directly from the setup screen, and LearningBuilder automatically manages ongoing authentication.
- “Call External API” Behavior now supports API Specifications. The “Call External API” Behavior can now be configured using an API Specification, in addition to the existing REST Endpoint plus System Template approach. Admins can select a specification and operation, map input parameters to Workflow Attributes or static values, and optionally map the API response body to an Attribute for storage.
- Test API calls directly from the API Specifications page. Admins can now test an API Specification without setting up a downstream feature, such as a Behavior. From the full-page editor, users can select a Server and Operation, provide input parameter values, and make a live API call. Results are displayed directly on the page. The test panel is locked when there are unsaved changes, so tests always reflect the saved configuration.
- Clearer validation for unsupported OpenAPI features: When saving an API Specification, the editor now validates and rejects configurations that use unsupported OpenAPI features, providing specific error messages to guide admins in correcting their specifications. This makes it easier to identify and fix issues up front, rather than running into unexpected behavior later.
- New OpenAPI Client service: This release introduces a code service for making API calls from an OpenAPI specification. This service powers the API Specifications enhancements above and is available for future API-driven features.
- Groundwork for backdated Learning Hub syncs: When LearningBuilder is the Subscriber in a Learning Hub integration, a Publisher’s data (for example, from an LMS) may reference a user who does not yet exist in LearningBuilder, leaving that data with nowhere to land. If that user later registers in LearningBuilder, their information needs to be backfilled, and historically there has been no automated way to do this. For 13.5, we created a system template that works with Integration Services and the “Call External API” Behavior to trigger that sync process. This development lays the foundation for a fully automated solution in a future release.
Configuration Enhancements
- Edit Role Workflow Instances are now reused instead of recreated. This release eliminates conditions that could occur when multiple Edit Role instances existed simultaneously for the same role. When a Grant Role Workflow is completed, an Edit Role Workflow Instance is now automatically created and maintained for the life of the role. Clicking “Edit” on the Account Profile page reuses this single instance rather than creating a new one each time.
- Custom CSS classes for Workflow Attributes on popups: When admins use Attributes to display long-form instructions on a Workflow popup, the result can be awkward spacing between the instructions and the next field. Admins can now attach a custom CSS class to a Workflow Attribute, which is applied when the Attribute renders in a Workflow popup — making it possible to adjust spacing and other presentation details as needed.
- New “Activity Contact” data type: Every Activity in LearningBuilder has a designated contact person, typically a staff member at the Provider organization responsible for that Activity. Until now, that contact could only be set when the Activity was first created, and changing it later required a separate process outside the normal Workflow. With the new Activity Contact data type, administrators can add an editable contact field directly to a Workflow Step, allowing the contact to be updated inline as part of a renewal, duplication, or resubmission. This is a meaningful improvement for programs that work with approved providers and continuing education activities, where staff turnover often means the original contact is no longer the right one by the time an Activity comes up for renewal.
Usability Enhancements
- Member Attributes now log value changes to the Workflow Value Log: Member Attributes now record change history in the Workflow Value Log, consistent with how other Workflow Attribute types behave. Log entries display the old and new values in a standardized format including the member’s name, email, and unique identifier (if available). If the value did not change, no log entry is written.
- A faster, more flexible Admin Print Queue page. The Admin Print Queue page previously took a long time to load when there were a lot of historical records. To improve the usability of that area, we added settings that control the default page size and maximum number of search results, along with the ability to search by date range (so that historical data is accessible if needed).
