Churn audits

When you clean up the data of a churned customer — as opposed to the ongoing retention-window cleanup — report it to this separate endpoint. Churn audits are filed under a separate storage prefix so the two audit types stay segregated and can carry different retention rules.

Endpoint#

POST https://core-api.heysadie.ai/v1/churn/audits
Content-Type: application/json
Authorization: ApiKey YOUR_ORG_API_KEY

Everything is identical to the retention audits endpoint:

• Note this is a /v1 path.
• Authenticate with your organization-level API key; no X-Tenant-Id header. Tenant-level keys are rejected — see Organization-level access.
• The body is any JSON object (max 10MB), stored exactly as sent. Only runId (UUID) is required — it names the stored file, and re-sending the same runId overwrites the same file, so retries are idempotent. finishedAt (ISO 8601) is recommended: it anchors the year/month folder the audit is filed under.
• source is derived server-side from your authenticated organization id and cannot be spoofed.

{
  "runId": "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee",
  "finishedAt": "2026-06-11T03:01:30.000Z",
  "status": "completed",
  "customerId": "<your-internal-customer-id>",
  "recordsDeleted": 4213
}

Responses#

A successful submission returns the standard envelope with { "stored": true, "runId": "..." }.

Which endpoint do I use?#