docs(fundamentals): link the GDPR entry to the relevant REST APIs - #491
Open
ketanyekale wants to merge 1 commit into
Open
docs(fundamentals): link the GDPR entry to the relevant REST APIs#491ketanyekale wants to merge 1 commit into
ketanyekale wants to merge 1 commit into
Conversation
Expands the GDPR bullet in the Compliances section so it points to the specific endpoints customers use when servicing data subject requests: retrieving a user's data, and permanently deleting a user along with their messages and conversations. The delete link is deep-linked to the permanent body parameter. Also aligns the feature-table entry with the compliance standards listed alongside it, updates the section intro to cover privacy standards as well as security standards, and fixes a HIPAA typo.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
pushpesh-cometchat
approved these changes
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Expands the GDPR entry in the Compliances section of
fundamentals/overview.mdxso it points readers to the specific REST APIs used when servicing data subject requests, plus three small consistency fixes on the same page.Why
The GDPR bullet previously described our API support in general terms. Naming the endpoints and linking them directly saves readers a search and makes the compliance story concrete and actionable at the point where they're evaluating it.
Changes
permanentbody parameterHIPPA→HIPAAEndpoints referenced
For reviewers, the APIs available to a controller servicing a data subject request:
GET /users/{uid}— profile, status, role, metadata, tagsGET /conversationswithonBehalfOf: uid— conversationsGET /messages?sender={uid}— messages, withattachmentsincluded inlineGET /calls?uid={uid}— call logsFor this use case the
/messagescall is made as admin withoutonBehalfOf, since setting it scopes results to common conversations.Note on the anchor
#body-permanentis verified against the rendered page. It's the first#body-*anchor in the repo — every other/rest-api/...#...link targets a normal heading slug — and it resolves because Mintlify generates ids for OpenAPI body parameters.Possible follow-up
A short guide showing those four calls composed into a single walkthrough, which the GDPR bullet could then link to instead of individual endpoints.
🤖 Generated with Claude Code