Skip to content
DashboardGet API key

Delete an item

View .md
DELETE

Idempotent: deleting a key that is not there, or a key of a collection that does not exist, still answers 204. Deletes are never refused for quota reasons.

Authorization

  • Authorizationheaderrequired

    Bearer YOUR_API_KEY. Create a key in the dashboard.

Path parameters

  • collectionstringrequired

    Collection name.

  • keystringrequired

    Item key. 1-255 chars from A-Z a-z 0-9 . _ : @ -

Query parameters

  • scopestring

    Which scope to address: contact:<contactId>, conversation:<conversationId>, or omitted for the project scope.

    Note the asymmetry with POST /v1/memory and POST /v1/memory/search, which take the scope in the request BODY as scope plus contactId/conversationId. Every other Memory endpoint takes it here.

Headers

  • If-Matchstring

    Make the write conditional on the item's current revision, as returned by a previous read or write (plain 3 or ETag-quoted "3"). The write is refused with 409 revision_conflict if the item moved on in between. Without it, the write always wins and silently overwrites a concurrent one.

Responses

204Item deleted.
400Invalid collection name, key, `scope`, or `If-Match`.
  • codestringrequired
  • messagestringrequired
  • detailsobject
401Unauthorized.
  • codestringrequired
  • messagestringrequired
  • detailsobject
409`revision_conflict`: the item changed since the revision in `If-Match`. Re-read it and retry.
  • codestringrequired
  • messagestringrequired
  • detailsobject