/v1/deletions (POST)

POST

/v1/deletions

const url = 'https://api.reindeer.example.tr/v1/deletions';
const options = {
  method: 'POST',
  headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
  body: '{"kind":"record","ids":["example"],"batch_seq":1}'
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request POST \
  --url https://api.reindeer.example.tr/v1/deletions \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "kind": "record", "ids": [ "example" ], "batch_seq": 1 }'

Scope deletions:write, fresh step-up for people. Ids are turned into HMAC pseudonyms and never stored in clear. A batch deletion always waits for an approver. Record deletions wait when the request, the principal’s items accepted without approval in the last 24 hours plus the request, or the tenant’s items accepted without approval in the last 24 hours plus the request pass limits.large_deletion or limits.tenant_deletions; author deletions use limits.large_authors and limits.tenant_authors. The 24 hour cool-off starts when the approver decides and can be cancelled until it ends.

Authorizations

mutualTLS
session

Parameters

Header Parameters

Idempotency-Key

string

<= 255 characters

Request Body^required

object

kind

required

string

Allowed values: record author record_before batch

ids

Array<string>

batch_seq

integer

One id per line; kind and batch_seq as query parameters

string format: binary

Example ^generated

binary

Responses

202

Accepted into the ledger or awaiting approval