# Retrieve an event

Retrieve the same immutable Event returned by the list. Select the Workspace whose memory
produced it; current access is required even if you already have the Event ID.

## GET `/v1/events/{id}`

Read an immutable recorded Engram lifecycle event by its evt\_ id. Workspace access is checked on every request. The payload is the recorded lineage record, not the current Engram resource.

## Authentication

Use an API key with the AugentaKey authorization scheme. See [Authentication](https://augenta.pages.dev/docs/authentication.md).

## Request example

```bash
curl --fail-with-body --get "https://api.augenta.ai/v1/events/$AUGENTA_EVENT_ID" \
  -H "Authorization: AugentaKey $AUGENTA_API_KEY" \
  --data-urlencode "workspace=$AUGENTA_WORKSPACE_ID"
```

## Parameters

<a id="request-parameters-id"></a>

### `request.parameters.id`

`string` · required

path parameter.

<a id="request-parameters-workspace"></a>

### `request.parameters.workspace`

`string` · optional

query parameter. One assigned Workspace. Required for keys with multiple assignments; inferred for one.

## Response 200

The same Event resource returned in event lists.

Content-Type: `application/json`

```json
{
  "object": "event",
  "id": "evt_2226fd14918857cbd289a8930000000000000100000000000001",
  "type": "engram.created",
  "created": 1790812800,
  "data": {
    "object": {
      "object": "engram_change",
      "id": "eng_000000000000000000000001",
      "kind": "born",
      "claimCountBefore": 0,
      "claimCountAfter": 1,
      "into": [],
      "absorbed": [],
      "at": "2026-10-01T00:00:00.000Z"
    }
  }
}
```

<a id="response-200-object"></a>

### `response.200.object`

`string` · always present

The resource type. Always event.

Allowed values: `"event"`.

<a id="response-200-id"></a>

### `response.200.id`

`string` · always present

The ID of this recorded Event, starting with evt\_. Use it with GET /v1/events/{id} in the same Workspace. Read data.object.id for the affected Engram's eng\_ ID. Snapshot Events are returned inline and have no stored lookup URL.

<a id="response-200-type"></a>

### `response.200.type`

`string` · always present

What happened: an Engram was created, changed membership, split, merged or retired. These Events do not report every score or summary update.

Allowed values: `"engram.created"`, `"engram.changed"`, `"engram.split"`, `"engram.merged"`, `"engram.retired"`.

<a id="response-200-created"></a>

### `response.200.created`

`integer` · always present

Recorded event time as Unix seconds. Workspace event feeds follow committed order even when source clocks go backward; one-shot events describe the completed rebuild.

<a id="response-200-data"></a>

### `response.200.data`

`object` · always present

The recorded identity-lineage payload. Completed memory results return the same Event resource in events. This is not a historical Engram snapshot or a complete score/prose audit.

<a id="response-200-data-object"></a>

### `response.200.data.object`

`object` · always present

<a id="response-200-data-object-object"></a>

### `response.200.data.object.object`

`string` · always present

The recorded payload type. Always engram_change.

Allowed values: `"engram_change"`.

<a id="response-200-data-object-kind"></a>

### `response.200.data.object.kind`

`string` · always present

What happened to the affected Engram's identity or Claim membership. The enclosing Event exposes the corresponding dotted type, such as engram.created for born.

Allowed values: `"born"`, `"update"`, `"split"`, `"merge"`, `"retire"`.

<a id="response-200-data-object-id"></a>

### `response.200.data.object.id`

`string` · always present

The ID of the Engram affected by this transition. This is an eng\_ ID, not the Event's evt\_ ID. The Engram may have been retired since this Event was recorded.

<a id="response-200-data-object-claimcountbefore"></a>

### `response.200.data.object.claimCountBefore`

`integer` · always present

The affected Engram's total current Claims immediately before this transition. Zero for a new Engram.

Minimum: `0`.

<a id="response-200-data-object-claimcountafter"></a>

### `response.200.data.object.claimCountAfter`

`integer` · always present

The affected Engram's total current Claims immediately after this transition. Zero when the identity is retired.

Minimum: `0`.

<a id="response-200-data-object-into"></a>

### `response.200.data.object.into`

`array<string>` · always present

New Engram IDs created by a split. Empty for other transition kinds.

<a id="response-200-data-object-absorbed"></a>

### `response.200.data.object.absorbed`

`array<string>` · always present

Engram IDs merged into this surviving Engram and retired. Empty for other transition kinds.

<a id="response-200-data-object-at"></a>

### `response.200.data.object.at`

`string` · always present

When this transition was recorded, as an ISO-8601 timestamp. The enclosing Event's created field represents the same time in Unix seconds.

## Response 400

Invalid Event id or missing Workspace selection.

Content-Type: `application/json`

<a id="response-400-error"></a>

### `response.400.error`

`object` · always present

<a id="response-400-error-code"></a>

### `response.400.error.code`

`string` · always present

Stable. The Errors page lists every code.

<a id="response-400-error-message"></a>

### `response.400.error.message`

`string` · always present

Human-readable. May change; don't parse it.

<a id="response-400-error-retryable"></a>

### `response.400.error.retryable`

`boolean` · always present

<a id="response-400-error-retryafterseconds"></a>

### `response.400.error.retryAfterSeconds`

`integer` · conditional

Capacity retry interval, also present as Retry-After before stream headers commit. SSE error events retain this field after HTTP 200 is committed.

Minimum: `1`.

<a id="response-400-error-billingurl"></a>

### `response.400.error.billingUrl`

`string` · conditional

Top-up action when error.code is insufficient_balance (HTTP 402).

<a id="response-400-requestid"></a>

### `response.400.requestId`

`string` · always present

The request's id, as in the `X-Request-Id` response header.

## Response 401

Authentication required; revoked credentials are refused.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 402

insufficient_balance: add credits before reading billable memory.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 403

Workspace access denied or Connector disabled.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 404

Workspace or event not found in the selected Workspace.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 409

Workspace archived.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 429

rate_limited: retry after the Retry-After header.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 500

An internal failure; quote the requestId.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 502

Cognition failed or returned an invalid response.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 503

Cognition is unavailable or unconfigured.

Content-Type: `application/json`

Response fields use the same schema as Response 400.
