Skip to content

feat: document missing e2e group key management endpoints #218

@Valyrian-Code

Description

@Valyrian-Code

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.acceptSuggestedGroupKey
  • GET /api/v1/e2e.fetchUsersWaitingForGroupKey
  • POST /api/v1/e2e.provideUsersSuggestedGroupKeys
  • POST /api/v1/e2e.rejectSuggestedGroupKey
  • POST /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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions