openmemory
Docs
Actions

Change an action's meta

PATCH
/v1/actions/{id}

Merges into meta, in any status, for example to keep a chat message id with the action. Set a field to null to remove it. Nothing else can be changed: what the owner approved stays as it was.

Authorization

headerAuthorizationBearer <token>

Your space key (om_...). Create one with POST /v1/spaces.

Path Parameters

id*string

Short action id, e.g. A7

Length1 <= length <= 32

Request Body

application/json
  1. body
meta*

Merged into the existing meta (for example a chat message id). Set a field to null to remove it. Nested objects are merged too.

Response Body

Updated

application/json
  1. response
id*string
class*string
summary*string
payload*
payload_hash*string
preconditions*array<unknown>
meta*
idempotency_key*string
status*ActionStatus
Value in"pending""approved""executing""done""failed""denied""expired""superseded""blocked"
receipt*|null
expires_at*string|null
created_at*string
updated_at*string
Example Request
curl -X PATCH 'https://api.openmemory.sh/v1/actions/string' \  -H 'Content-Type: application/json' \  -d '{  "meta": {    "property1": null,    "property2": null  }}'
Example Response
{  "id": "string",  "class": "string",  "summary": "string",  "payload": {    "property1": null,    "property2": null  },  "payload_hash": "string",  "preconditions": [    null  ],  "meta": {    "property1": null,    "property2": null  },  "idempotency_key": "string",  "status": "pending",  "receipt": {    "property1": null,    "property2": null  },  "expires_at": "string",  "created_at": "string",  "updated_at": "string"}

Move an action to a new status, only if it is still in `from` POST

Compare-and-set: two callers cannot both move A7 from approved to executing. Allowed: pending→approved|executing|denied|expired|superseded|blocked, approved→executing|denied|expired|superseded, executing→done|failed, blocked→pending|denied|superseded, failed→pending. Expired actions cannot be approved or executed.

Apply several writes atomically POST

All ops succeed or none do. Version and status checks abort the whole batch with 409, and error.details.op_index says which op failed when that can be told. Ops that read first (record.update, journal merge, action.propose) see the state from before the batch.