const url = 'http://localhost:8000/v1/ratchet/examples';const options = {method: 'DELETE'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request DELETE \ --url http://localhost:8000/v1/ratchet/examplesErase the stored examples of one of the caller’s end users ({"end_user": "<user or safety_identifier>"}, as
for no-train; optional reason and dry_run, default false): their text goes for good, their hashes are never
stored again, and the end user’s hash is cleared from its request rows (FR-13.3). An API key erases its own end
users; an admin key a named client’s, or with no client every client’s (each configured key, every scope the
ledger holds end users in, and the keyless one). Open where chat completions are, like registering no-train: it
only removes data. A keyless caller (API keys off) gets the counts as null, so the endpoint cannot tell anyone
whether an identifier had stored examples. The end user is read from the body only: a URL with end_user is a 400,
because access logs keep URLs.
Parameters
Section titled “Parameters”Header Parameters
Section titled “Header Parameters”Responses
Section titled “Responses”Successful Response
object
Example generated
{}Validation Error
object
object
Example generated
{ "detail": [ { "loc": [ "example" ], "msg": "example", "type": "example" } ]}