Customer success

Archive Transcript

Take a transcript out of the client's view.

REVERSIBLE - /unarchive puts it back, and nothing is deleted. It is still tiered destructive, because that is what the shared /archive rule derives for every archive route in the contract and an exception here would make the tier mean two things.

No company gate on the route: this is addressed by transcript, not by company, so the caller's company scope is what authorises it - exactly as the app has it.

patch/customer-success/transcripts/{transcript_id}/archive

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/customer-success/transcripts/{transcript_id}/archive
  • Auth: HTTP bearer

Path parameters

transcript_idstring required

Transcript id.

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Response

Successful Response

dataOrgPayload required

An open envelope for a single role, team, member or account record.

Open on purpose. The app's own response models on this surface grow with the product - RoleResponse gained rep_limits and manages_role_slugs, TeamResponse gained channel counts and a campaign count - and a pinned mirror would SILENTLY DROP whatever it had not caught up on. A dropped permission in a role read is the worst possible kind of stale: it reads as "they do not have it".

Changes