Export_erasures
const url = 'http://localhost:3000/api/export/erasures?limit=1000';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'http://localhost:3000/api/export/erasures?limit=1000' \ --header 'Authorization: Bearer <token>'Read the Workspace’s Erasures, oldest first (Enterprise; needs the export:read scope).
Each line of the body is an ExportErasureRow; every key is always present. Rows live for
the instance’s Event retention window and are kept for good when retention is off: a
consumer absent for longer re-seeds from an empty cursor.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Cursor from the X-Next-Cursor header of a previous page; empty reads from the beginning
Page size
Responses
Section titled “Responses”One page of an Export stream (Enterprise, ADR 0045): newline-delimited JSON, one row
per line with no envelope, so the body loads as ClickHouse JSONEachRow. The row
schema is named by each operation. The next cursor is the X-Next-Cursor header;
pass it as cursor for the next page. The cursor is the position after the last row of
the page and the next page includes everything at or after it, so rows that share an
updated_at across a page edge are not lost. A page with no rows returns the cursor it
was given. A row that changes is delivered again with a newer updated_at: keep the
newest version per id.
Example generated
binaryHeaders
Section titled “Headers”Opaque cursor for the next page
RFC 7807 bad request response
RFC 7807 Problem Details
object
Why the request was refused, when the client should act on it
A URI reference that identifies the problem type
A short, human-readable summary of the problem type
HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Validation errors grouped by field
object
Form-level validation error
Field validation errors
object
Seconds to wait before retrying; set on a 429 so a client that only sees the body can show the wait
Why a 500 happened, sent only by a development server (SPHERICON_ENV=development)
object
The error that failed the request, or the panic value
The goroutine stack of a panic; absent for an error a handler returned
The request id the server log carries for this request
The HTTP method of the failed request
The path of the failed request
Example
{ "code": "second_factor_required"}RFC 7807 unauthorized response
RFC 7807 Problem Details
object
Why the request was refused, when the client should act on it
A URI reference that identifies the problem type
A short, human-readable summary of the problem type
HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Validation errors grouped by field
object
Form-level validation error
Field validation errors
object
Seconds to wait before retrying; set on a 429 so a client that only sees the body can show the wait
Why a 500 happened, sent only by a development server (SPHERICON_ENV=development)
object
The error that failed the request, or the panic value
The goroutine stack of a panic; absent for an error a handler returned
The request id the server log carries for this request
The HTTP method of the failed request
The path of the failed request
Example
{ "code": "second_factor_required"}RFC 7807 not found response
RFC 7807 Problem Details
object
Why the request was refused, when the client should act on it
A URI reference that identifies the problem type
A short, human-readable summary of the problem type
HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Validation errors grouped by field
object
Form-level validation error
Field validation errors
object
Seconds to wait before retrying; set on a 429 so a client that only sees the body can show the wait
Why a 500 happened, sent only by a development server (SPHERICON_ENV=development)
object
The error that failed the request, or the panic value
The goroutine stack of a panic; absent for an error a handler returned
The request id the server log carries for this request
The HTTP method of the failed request
The path of the failed request
Example
{ "code": "second_factor_required"}