# Create issues URL: https://docs.hanzo.ai/docs/openapi/o11y/post-o11y-errortracking-issues-by-id > Changes an issue's lifecycle — resolve, ignore, reopen or assign — and returns the updated issue. `POST /v1/o11y/errortracking/issues/{id}` > [O11y →](https://docs.hanzo.ai/docs/openapi/o11y) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides) | | | | ------------- | -------------------------------------------------------- | | **Address** | `https://api.hanzo.ai/v1/o11y/errortracking/issues/{id}` | | **Method** | `POST` | | **Operation** | `post_o11y_errortracking_issues_by_id` | | **Auth** | `Authorization: Bearer $HANZO_API_KEY` | Changes an issue's lifecycle — resolve, ignore, reopen or assign — and returns the updated issue. Fields left unset are left unchanged. Callers need the editor role; the runtime's own gate enforces it. ## Request 4 fields, body `application/json` (required). | Field | In | Type | Required | Description | | ---------- | ---- | ------ | -------- | ------------------------------------------------------------------- | | `id` | path | string | yes | ID is the issue id. | | `assignee` | body | string | — | Assignee is who the issue is assigned to. | | `id` | body | string | yes | ID is the issue id. | | `status` | body | string | — | Status is the new lifecycle state: unresolved, resolved or ignored. | ## Response | Status | Body | Meaning | | --------- | ---------------------- | ----------------- | | `200` | o11y.O11yErrorIssueOut | ok | | `202` | Approval | held for approval | | `default` | problem-details | refused | `200` body — 21 fields. | Field | In | Type | Always | Description | | ------------------ | ---- | ------------------- | ------ | -------------------------------------------------------------------- | | `data` | body | o11y.O11yErrorIssue | — | | | `data.assignee` | body | string | — | Assignee is who the issue is assigned to. | | `data.count` | body | integer (int64) | — | Count is how many occurrences have landed on the issue. | | `data.createdAt` | body | string (date-time) | — | CreatedAt is when the issue was first recorded. | | `data.culprit` | body | string | — | Culprit is where it came from — the function or route blamed for it. | | `data.environment` | body | string | — | Environment is the deployment the issue was seen in. | | `data.fingerprint` | body | string | — | Fingerprint is the grouping key that puts like errors in one issue. | | `data.firstSeen` | body | string (date-time) | — | FirstSeen is when the earliest occurrence was recorded. | | `data.id` | body | string | — | ID is the issue id. | | `data.lastSeen` | body | string (date-time) | — | LastSeen is when the latest was. | | `data.level` | body | string | — | Level is the issue's severity, e.g. error, warning, info. | | `data.platform` | body | string | — | Platform is the reporting runtime, e.g. go, python, javascript. | | `data.regressed` | body | boolean | — | Regressed marks an issue that reopened after being resolved. | | `data.release` | body | string | — | Release is the version that produced it. | | `data.resolvedAt` | body | string (date-time) | — | ResolvedAt is when the issue was resolved, if it is. | | `data.serviceName` | body | string | — | ServiceName is the service that reported it. | | `data.status` | body | string | — | Status is the lifecycle state: unresolved, resolved or ignored. | | `data.type` | body | string | — | Type is the exception type. | | `data.updatedAt` | body | string (date-time) | — | UpdatedAt is when the issue last changed. | | `data.value` | body | string | — | Value is the exception value. | | `status` | body | string | — | Status is "success". | Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors). ## Examples **CLI** ```bash hanzo o11y errortracking issues add ``` **SDK** **.ts** ```ts import { Configuration, O11yApi } from 'hanzoai'; const api = new O11yApi(new Configuration({ accessToken: process.env.HANZO_API_KEY })); const { data } = await api.postO11yErrortrackingIssuesById({ id: 'id', id: "" }); ``` **.py** ```python 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_errortracking_issues_by_id(id='id', id="") ``` **.go** ```go cfg := hanzoai.NewConfiguration() cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY")) client := hanzoai.NewAPIClient(cfg) resp, _, err := client.O11yAPI.PostO11yErrortrackingIssuesById(context.Background()).Execute() if err != nil { return err } ``` **.rs** ```rust use hanzo_client::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_errortracking_issues_by_id(&cfg, Default::default()).await?; ``` **.java** ```java import ai.hanzo.cloud.ApiClient; import ai.hanzo.cloud.api.O11yApi; ApiClient client = new ApiClient(); client.setBearerToken(System.getenv("HANZO_API_KEY")); var result = new O11yApi(client).postO11yErrortrackingIssuesById(); ``` **HTTP** ```bash curl -X POST https://api.hanzo.ai/v1/o11y/errortracking/issues/ \ -H "Authorization: Bearer $HANZO_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "id": "" }' ``` **MCP** MCP reaches **o11y** through the `o11y` tool, which names its 307 operations with its own verbs — this one among them, under a name only MCP declares. `describe` explains any of them: ```bash 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_o11y_autocomplete_aggregate_attributes" } } }' ``` --- [O11y API](https://docs.hanzo.ai/docs/openapi/o11y) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)