← Changelog
UpdatedApps

Action params are checked before the action runs

An action's export const params used to type calls and nothing more: a caller over the API, MCP, a job or a webhook could pass the wrong type, and the action failed somewhere inside run, or didn't. Every run is now checked against them first, and a call that doesn't match is refused with 400 invalid_request, its problems naming each param by its path.

Required params must be there, and each param must be its declared type: text, a number, true or false, a date and time, one of an enum's options, an object with its properties, or a list of its items. Keys the file doesn't name still pass, so a create or update action takes the model's fields as before, and an action without params takes anything.

The SDK's test harness (0.16.4) checks the same way, so a test catches a call that production would refuse.

More in Params.