feat: document missing e2e group key management endpoints
Maintainers usually reply within 1 day
@Roxie-32 is already working on this.
Since Jul 27, 2026.
Assessment
This issue has not been assessed yet.
Description
While reviewing the inconsistencies noted in #171, I identified five e2e
group key management endpoints that exist as REST routes in the Rocket.Chat
source (apps/meteor/app/api/server/v1/e2e.ts) but are not documented in
the OpenAPI spec:
POST /api/v1/e2e.acceptSuggestedGroupKeyGET /api/v1/e2e.fetchUsersWaitingForGroupKeyPOST /api/v1/e2e.provideUsersSuggestedGroupKeysPOST /api/v1/e2e.rejectSuggestedGroupKeyPOST /api/v1/e2e.resetRoomKey
These are all part of the E2E group key rotation flow introduced alongside
the suggested key distribution system.
I have drafted spec entries for all five, following the same pattern as the
existing e2e.* entries in settings.yaml. Happy to open a PR if this is
a good direction.
Closes part of #171
- Dominant language
- No language data
- Stars
- 16
- Forks
- 18
- Avg merge
- 16m
- Merged PRs (30d)
- 24
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RocketChat/Rocket.Chat-Open-API
-
Inconsistencies Found Between Source Code and API SpecificationMay be free again @Roxie-32 claimed this 111 days ago, and no pull request is open. Open
RocketChat/Rocket.Chat-Open-API#171 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day