Rotates a project's DSN key — bumping its rotation watermark so keys below it…
Rotates a project's DSN key — bumping its rotation watermark so keys below it stop verifying — and returns the project with its new DSN.
POST /v1/o11y/sentinel/projects/{id}/keys/rotate
| Address | https://api.hanzo.ai/v1/o11y/sentinel/projects/{id}/keys/rotate |
| Method | POST |
| Operation | post_o11y_sentinel_projects_by_id_keys_rotate |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Rotates a project's DSN key — bumping its rotation watermark so keys below it stop verifying — and returns the project with its new DSN.
Callers need the editor role; the runtime's own gate enforces it.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
id | path | string | yes | ID is the project id. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | o11y.O11ySentryProjectOut | ok |
200 body — 10 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | o11y.O11ySentryProject | — | |
data.createdAt | body | string (date-time) | — | CreatedAt is when the project was created. |
data.dsn | body | string | — | DSN is the project's freshly-derived ingest DSN. |
data.id | body | string | — | ID is the project id. |
data.name | body | string | — | Name is the project's display name. |
data.platform | body | string | — | Platform is the reporting runtime, e.g. |
data.slug | body | string | — | Slug is the project's short name. |
data.status | body | string | — | Status is the project's lifecycle state: active or disabled. |
data.updatedAt | body | string (date-time) | — | UpdatedAt is when the project last changed. |
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.postO11ySentinelProjectsByIdKeysRotate({ id: 'id' });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).post_o11y_sentinel_projects_by_id_keys_rotate(id='id')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.O11yAPI.PostO11ySentinelProjectsByIdKeysRotate(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::post_o11y_sentinel_projects_by_id_keys_rotate(&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).postO11ySentinelProjectsByIdKeysRotate();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 -X POST https://api.hanzo.ai/v1/o11y/sentinel/projects/<id>/keys/rotate \
-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?