Lists the caller's org's Sentry projects, each with its freshly-derived DSN.
Lists the caller's org's Sentry projects, each with its freshly-derived DSN.
GET /v1/o11y/sentinel/projects
| Address | https://api.hanzo.ai/v1/o11y/sentinel/projects |
| Method | GET |
| Operation | get_o11y_sentinel_projects |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Lists the caller's org's Sentry projects, each with its freshly-derived DSN.
Callers need the viewer role; the runtime's own gate enforces it.
Request
GET /v1/o11y/sentinel/projects takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | o11y.O11ySentryProjectsOut | ok |
200 body — 12 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | o11y.O11ySentryProjects | — | |
data.items | body | o11y.O11ySentryProject[] | — | Items are the projects. |
data.items[].createdAt | body | string (date-time) | — | CreatedAt is when the project was created. |
data.items[].dsn | body | string | — | DSN is the project's freshly-derived ingest DSN. |
data.items[].id | body | string | — | ID is the project id. |
data.items[].name | body | string | — | Name is the project's display name. |
data.items[].platform | body | string | — | Platform is the reporting runtime, e.g. |
data.items[].slug | body | string | — | Slug is the project's short name. |
data.items[].status | body | string | — | Status is the project's lifecycle state: active or disabled. |
data.items[].updatedAt | body | string (date-time) | — | UpdatedAt is when the project last changed. |
data.total | body | integer | — | Total is how many the org has. |
status | body | string | — | Status is "success". |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, O11yApi } from 'hanzoai';
const api = new O11yApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getO11ySentinelProjects();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import O11yApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = O11yApi(client).get_o11y_sentinel_projects()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.O11yAPI.GetO11ySentinelProjects(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, o11y_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = o11y_api::get_o11y_sentinel_projects(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.O11yApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new O11yApi(client).getO11ySentinelProjects();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/o11y/sentinel/projects \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches o11y through the o11y tool, which names its 340 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": "get_o11y_alert_last"
}
}
}'How is this guide?