Export memories
⚠️
Preview — this feature is being built; the design below is the spec.
POST https://app.syntic.ai/v1/memory_stores/{store_id}/exportWrite memories to a JSONL file in the Files API, one memory per line, for backups or access requests. Download it with Download file content.
For how this fits into a full workflow, see Memory stores.
Headers
| Header | Required | Value |
|---|---|---|
Authorization | Yes | Bearer <key>: a private inference key (sk_live_...). See Authentication. |
syntic-beta | Yes, while in preview | agents-2026-11-01. Without it the call fails with 400 beta_required. See Versioning. |
Content-Type | Yes | application/json |
Path parameters
| Parameter | Type | Description |
|---|---|---|
store_id | string | The memory store id, starting with mem_. |
Body parameters
| Parameter | Type | Required | Notes |
|---|---|---|---|
scope | string | No | Export one scope only. Default: the whole store. |
Response
202 Accepted, Content-Type: application/json
{
"file_id": "file_01JCC7E9G1J3L5N7Q9S1",
"status": "processing",
"memory_count": 37
}Large exports finish in the background; the file is processing until it is complete. Poll Get a file.
Examples
curl -sS https://app.syntic.ai/v1/memory_stores/mem_01JC1A3C5E7G9J1L3N5Q/export \
-H "Authorization: Bearer $SYNTIC_API_KEY" \
-H "syntic-beta: agents-2026-11-01" \
-H "Content-Type: application/json" \
-d '{
"scope": "customer:4821"
}'Errors
Errors use the error envelope and carry a request_id. Codes specific to this operation:
| Status | type | code | When |
|---|---|---|---|
| 400 | invalid_request_error | beta_required | The syntic-beta header is missing. |
| 404 | not_found_error | memory_store_not_found | No store with that id in this workspace. |
| 401 | authentication_error | invalid_api_key | The key is missing, unknown, revoked or expired. |
| 429 | rate_limit_error | rate_limited | Too many requests; wait for Retry-After. See Rate-limit headers. |
Related
Was this page helpful?