Turn bulk notification email off (RFC 8058 one-click)
const url = 'https://api.tovarifinancial.com/notifications/unsubscribe';const options = {method: 'POST'};
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.tovarifinancial.com/notifications/unsubscribeUNAUTHENTICATED, and EVERY OUTCOME IS THE SAME 200 with the same body: a valid token, an invalid one, an expired one, an absent one and an internal failure are indistinguishable. With no authentication, any difference between those cases would be an oracle an attacker could enumerate, so there is no error code and no details here by design. The token is read from the ?t= QUERY STRING on both body forms, which is what lets one code path serve a mail client’s List-Unsubscribe=One-Click form POST and the confirmation page’s JSON POST. It accepts NO X-Idempotency-Key — the idempotency store is org-scoped and this path has no org context — and needs none: the effect is convergent. Unsubscribing turns BULK mail off; transactional security and data-export notices, which carry no List-Unsubscribe header, keep sending, and the in-app feed is never affected.
Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”The opaque unsubscribe token from the message.
Responses
Section titled “Responses”Acknowledged — byte-identical for every outcome
object
object
Examplegenerated
{ "data": { "ok": true }, "message": "example", "requestId": "example", "timestamp": "2026-04-15T12:00:00Z"}