Skip to main content
DELETE
Hard-erase a candidate and return a content-free receipt
Hard-erase one Praxa memory candidate and receive a content-free, replay-safe deletion receipt without deleting its provider source.
Availability: Qualification preview. Required scope: memory:write.

Authenticate safely

Create a disposable personal workspace API key with exactly memory:write. Send it as Authorization: Bearer $PRAXA_API_KEY. A Gateway OAuth token, Supabase JWT, provider credential, or organization memory key is not interchangeable with this key. The hosted playground sends the credential from your browser session to the documented API through the configured playground proxy. Use test data, never share the key, and revoke it when the check ends.

Request fields

string
required
recordId path parameter.
string
required
Stable key for one logical mutation. Reuse only with the exact same request; changed input under the same key returns a conflict.

Runnable request examples

What success means

A 200 response confirms candidate erasure or exact deletion replay. Provider-owned source data is unchanged.

Successful response

200 — Candidate content erased or exact deletion replayed.
v1
required
apiVersion response field.
true
required
erased response field.
boolean
required
replayed response field.
object
required
receipt response field.

Handle failures

Example problem

Verify the result

  1. Require erased: true and a content-free receipt.
  2. Query the subject and confirm candidate content is absent.
  3. Replay with the same key and require the same receipt.

Retry, cleanup, and production use

  • Treat 401, 403, and 409 as authority or state signals, not generic retry prompts.
  • Reuse the idempotency key only for an exact retry of the same logical mutation.
  • For 429 or retryable 5xx responses, follow server retry guidance and keep a bounded attempt budget.
  • Move the request into a trusted application backend before production; never ship the Praxa key in browser or mobile code.
  • Revoke the disposable key, disable test webhooks, and erase disposable candidate data after validation.
Continue with API authentication, the failure and retry guide, and the end-to-end coverage matrix.
Last modified on August 14, 2026