Administration

Request record deletion from Postman

Use OAuth and the Approval Inbox for audited CRM and custom record deletion.

How to do it

  1. In BU Settings → Developer & AI, register an OAuth app and permit the records.delete scope. The authorizing BU user also needs integration management and the object’s Delete permission.
  2. In Postman choose DELETE https://login.supachrome.com/api/v1/records/contact (replace contact with the object API name). Set Authorization: Bearer YOUR_OAUTH_ACCESS_TOKEN and Content-Type: application/json.
  3. In Body → raw → JSON send {"recordIds":["SUPACHROME_RECORD_ID"],"confirmation":"contact"}. Use 1–200 distinct IDs from the current business.
  4. After HTTP 202, review the request and Cascade impact in Approval Inbox. The reviewer needs the object’s Delete permission and settings access. In an object list, Select records to delete opens the same reviewed process.

Check your result

HTTP 202 means requested, not deleted. Review the final approval result and any protected records.

Good to know

Orders, payments and posted adjustments retain financial history. Use cancellation, rejection or reversal in their original workflows. A source key cannot authorize deletion.

Still need help?

Tell us your BU code and the step where you got stuck. Do not include passwords, BU PINs, tokens or recovery codes.

Contact SupaChrome support