flowus-api-call

FlowUs API Call Skill

Use the flowus CLI with --json for every command.

Commands

• Without body: flowus --json api call <METHOD> <PATH_TEMPLATE> --param key=value
• With body: flowus --json api call <METHOD> <PATH_TEMPLATE> --param key=value --body <body.json>
• With headers: flowus --json api call <METHOD> <PATH_TEMPLATE> --header key=value

Rules

• If authentication is unclear, use flowus --json doctor; use flowus login for interactive login.
• Credential precedence is --token, then FLOWUS_TOKEN, then the token saved by flowus login.
• Use only when a high-level FlowUs skill does not cover the needed operation.
• Prefer a high-level FlowUs skill whenever one covers the needed operation.
• Do not call FlowUs V2 API with curl.
• Do not print or save bearer tokens.
• Path templates may use either OpenAPI braces (/v2/pages/{page_id}) or developer-doc colons (/v2/pages/:page_id).
• --param values fill matching path parameters; unused params become query parameters.
• Use repeated --header key=value for documented headers such as Idempotency-Key or If-Match.
• Prefer explicit JSON body files over inline shell strings.
• For write operations or DELETE, confirm the method, path, params, and body file if present come from user-authorized input; DELETE is destructive.
• Treat ok: false as a failed operation even if the process output is parseable JSON.