OpenapiFunctions
Is one function's past runs, newest first — each with its status, HTTP code,…
Is one function's past runs, newest first — each with its status, HTTP code, method, time and duration.
GET /v1/functions/{name}/invocations
| Address | https://api.hanzo.ai/v1/functions/{name}/invocations |
| Method | GET |
| Operation | get_functions_by_name_invocations |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Is one function's past runs, newest first — each with its status, HTTP code, method, time and duration.
These are real recorded rows, not a projection: an invocation appears here only once it actually ran. Requires a validated principal; the read is scoped to its org.
Request
2 fields.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
name | path | string | yes | Name is the function the URL names. |
limit | query | integer | — | Limit caps the page, defaulting to 100. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | invocationList | ok |
200 body — 7 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
invocations | body | invocationView[] | — | Invocations is one row per past run, newest first. |
invocations[].durationMs | body | integer | — | how long it took |
invocations[].id | body | string | — | the invocation's handle |
invocations[].method | body | string | — | the HTTP method that triggered it |
invocations[].status | body | string | — | how the run ended: ok, error or timeout |
invocations[].statusCode | body | integer | — | Code is the status the function's OWN code answered with, which is not the status of the reply — a program can answer 500 through a healthy sandbox. |
invocations[].time | body | string | — | when it ran, RFC3339 |
Failure carries the platform error shape — see Errors.
Examples
hanzo functions invocations <name>import { Configuration, FunctionsApi } from 'hanzoai';
const api = new FunctionsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getFunctionsByNameInvocations({ name: 'name' });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import FunctionsApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = FunctionsApi(client).get_functions_by_name_invocations(name='name')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.FunctionsAPI.GetFunctionsByNameInvocations(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, functions_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = functions_api::get_functions_by_name_invocations(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.FunctionsApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new FunctionsApi(client).getFunctionsByNameInvocations();curl https://api.hanzo.ai/v1/functions/<name>/invocations \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches functions through the functions tool, which names its 10 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_functions"
}
}
}'How is this guide?