Skip to main content
GET
Export one subject's candidate and deletion history
Export one subject’s Praxa memory candidates and content-free deletion history as cursor-paged NDJSON.
Availability: Qualification preview. Required scope: memory:read.

Authenticate safely

Create a disposable personal workspace API key with exactly memory:read. 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
subject query parameter.
integer
limit query parameter.
string
cursor query parameter.

Runnable request examples

What success means

A 200 response streams one JSON object per line; X-Praxa-Next-Cursor indicates another page.

Successful response

200 — Newline-delimited candidate and content-free deletion events.

Handle failures

Example problem

Verify the result

  1. Parse every non-empty line independently.
  2. Use the cursor exactly as returned.
  3. Require deletion entries to contain no erased content.

Retry, cleanup, and production use

  • Treat 401, 403, and 409 as authority or state signals, not generic retry prompts.
  • 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