chore: regenerate sdk

This commit is contained in:
Abhishek Kumar 2026-04-25 16:34:19 +05:30
parent 4171ad7a54
commit d6567eef28
4 changed files with 25 additions and 10 deletions

View file

@ -6,9 +6,12 @@
/**
* Public HTTP endpoint that launches the workflow.
* Public HTTP endpoints that launch the workflow.
*
* LLM hint: Exposes a public HTTP POST endpoint. External systems call the URL (derived from the auto-generated `trigger_path`) to launch this workflow. Requires an API key in the `X-API-Key` header.
* LLM hint: Exposes two public HTTP POST endpoints derived from the auto-generated `trigger_path`:
* Production: `<backend>/api/v1/public/agent/<trigger_path>` runs the published agent. Use this from production systems.
* Test: `<backend>/api/v1/public/agent/test/<trigger_path>` runs the latest draft, useful for verifying changes before publishing. Falls back to the published agent when no draft exists.
* Both require an API key in the `X-API-Key` header.
*/
export interface Trigger {
type: "trigger";
@ -21,7 +24,10 @@ export interface Trigger {
*/
enabled?: boolean;
/**
* Auto-generated UUID-style path segment that uniquely identifies this trigger. Do not edit manually.
* Auto-generated UUID-style path segment that uniquely identifies this trigger. Used in both URLs:
* Production: `/api/v1/public/agent/<trigger_path>` executes the published agent.
* Test: `/api/v1/public/agent/test/<trigger_path>` executes the latest draft.
* Do not edit manually.
*/
trigger_path?: string;
}