API Engine Release Notes - 1.22.2026081428.303683

Delimited (CSV) Response Support

• Functions can read responses that arrive as delimited text, not only JSON or XML, so report downloads and file-based exports can be mapped like a JSON array.
• Choose comma, tab, semicolon or pipe, and indicate whether row one supplies the column names (if not, columns become Column1, Column2 and so on).
• Quoted values, separators and line breaks inside quotes, and escaped quotes are handled. Optional settings tolerate extra columns or reject non-standard quoting. Rows with missing columns always fail the message, so a truncated feed cannot load into the wrong fields.

GraphQL Variables Builder

• Paste a query or mutation, and optionally its variables as JSON, and the builder creates the API Variables that drive the request: operations, fields, aliases, arguments, directives, fragments and variable declarations.
• Open it from the API Functions list or the Function card. Input is checked first, so invalid text changes nothing, and you confirm before existing body variables are replaced.

GraphQL Directives

• Directives can be attached to an operation, type or field and carry their own arguments, so one stored query can serve conditional shapes instead of needing a function per variation.

API Set Deletion with Impact Review

• Deleting an API set now shows what will be affected first: the functions and credentials that will be deleted, plus the automations, application executions and application operations that reference it. You can drill into the affected records before deciding.
• Deletion runs through a dedicated action so the review is not skipped. Automations lose their API references and are switched off. Executions and operations keep their records and only lose the reference.

Automation Enablement Rules

• A step cannot be switched on unless the API it calls can be resolved, from either an API set and function or an application, operation and module. Extensible for apps that add their own automation types.

Build Payload Action on API Messages

• Assembles a message's request without sending it, so a configuration can be inspected first. The built request is saved onto the message.

Whole Number Value Conversion

• Two methods convert between whole number and decimal amounts, as many payment APIs require: 1099 to 10.99, and 10.99 to 1099. Available for mapping and variable values.

Automation Step Details Pane

• The API Automation Groups page shows the selected step's details inline.

Updated

API Automation Groups

• The Description appears earlier in the row as it is a more prominent field and should have priority. Tooltips on code, description, sequence, enabled and type now explain what each control.

API Automation Steps

• The API Set Code and API Function Code are hidden on the steps list. You can configure them on the step card.

Enabling all Steps in a Group

• This function asks once whether to set a Last Run timestamp for steps without one. If a step cannot be switched on the rest still are, with one summary of how many were skipped.

API Function Card

• CSV options appear only for a delimited function and appear as soon as the setting changes. Switching an existing function to CSV defaults it to having a header row.

Fixed

Dates No Longer Depend on Regional Settings

• A date held as a request parameter is stored in a fixed international format, so the same configuration produces the same value whoever runs it. Parameters saved by earlier versions are still read.

• A value that cannot be read as a date now logs a warning naming the parameter and the rejected text instead of returning a blank.

Whole Numbers in Numeric Variables

• A numeric variable whose stored value is a whole number is read as a number instead of as no value.

Log Entries Can Be Traced to Their Message

• Log rows written during a call now carry the API message identifier.