lark-openapi-explorer

You can call a Lark OpenAPI endpoint by discovering the correct native API specification through official markdown docs and executing it directly via the lark-cli api command. This ensures precise GET, POST, PUT, or DELETE operations without guessing paths or parameters.

To find the correct Feishu OpenAPI request details, retrieve the official module index and walk through specific API markdown documentation layer-by-layer. This document-driven discovery process ensures you source the exact method, path, required parameters, and permissions accurately.

Yes, lark-cli supports executing native OpenAPI operations safely by enforcing confirmation guardrails for write and delete operations. It requires document-sourced specifications to generate the exact API call, preventing unauthorized or incorrect modifications to your Lark environment.

The best way to automate uncovered Lark tasks is to use document-driven API discovery to locate the required native OpenAPI endpoint. Then, generate a complete lark-cli api command based strictly on the official markdown specification to execute the automation safely.

You should not use direct OpenAPI calls if an existing Lark skill or lark-cli command already covers your requirement. Direct API execution should be reserved for specific scenarios where built-in commands lack the functionality needed for your precise automation task.

Yes, you can use lark-cli to perform GET, POST, PUT, and DELETE requests on Lark APIs. It constructs the native request execution using the discovered HTTP method, path parameters, query parameters, and body fields extracted directly from official API documentation.