Confirm you deleted the records
Confirms that the records named in a user.erased delivery are gone from your
systems. event_id is the event_id of that delivery.
Call this only when the deletion is done. There is no way to report a failure and no state to park a request in: not calling it is the signal, and a request that stays unacknowledged is escalated on our side.
The body is almost empty on purpose. There is no free-text field, because the one
thing anybody would write there is a detail about the person whose erasure is
being confirmed. completed_at is recorded as your claim about when you
finished; the acknowledged_at we return is our own receipt clock and is the
figure that appears in our compliance record.
Your acknowledgment never blocks or delays the erasure itself. Maat completes on its own clock; this is the recipient-notification record.
Repeat calls are safe and return the same acknowledged_at as the first — a
compliance timestamp does not move because a request was retried.
Sandbox: this records your confirmation. Production: 501. No production
partner has ever been sent a user.erased delivery, so there is nothing there to
acknowledge, and answering 200 would let you record satisfying a request you
never received. Do not treat a 501 from this endpoint as evidence of anything.
Authorizations
A short-lived partner token, obtained by exchanging your API key at
POST /token. Send it as Authorization: Bearer <access_token>.
Tokens live for fifteen minutes by default and never for more than an hour. Mint one per batch of work, not one per request.
The token carries the workspace and the environment its key was issued for. You cannot change either by asking: the exchange ignores everything in the request body for exactly that reason.
Never send it as a cookie or in a query string, and never store it — store the API key, mint tokens from it.
Path Parameters
The event_id of the user.erased delivery being acknowledged.
Body
When you completed the deletion. Defaults to the time we receive this.