kayako-api-function

To add a Kayako API function, define it in src/api.php using validation-first input checks, wrap each SOAP call in its own try/catch block, and return a standardized status/status_text array for consistent error reporting.

The validation-first pattern requires checking inputs before executing operations, initializing Kayako SOAP config, isolating each API call in a per-operation try/catch, and returning a standardized status array to ensure safe ownership verification.

Standardize error reporting by returning a consistent status/status_text array from every procedural function, ensuring that create, view, and reply ticket operations handle exceptions uniformly through isolated try/catch blocks.

No, this approach applies exclusively to procedural functions in src/api.php. You should not use it for modifying src/Plugin.php hook registration or for implementing class-based API work.

You need per-operation try/catch blocks when adding ticket-related API enhancements like creating, viewing, or replying to tickets, ensuring safe ownership checks and isolating SOAP failures without disrupting the entire request.

Your Kayako API function likely lacks the standardized status/status_text array return format or is missing per-operation try/catch blocks, which are required to preserve safe ownership checks and consistent error reporting.