docs: document GET /groups/:id full schema, list vs detail delta, and subgroup field additions

[Quazmoz]

What's changed

GET /groups/:id (index.md)

• Added full response schema table documenting all fields returned by the detail endpoint
• Added List vs Detail comparison table clarifying which fields are exclusive to the detail view (members, messages metadata) vs the index endpoint
• Corrected the example response to remove the messages.preview block, which is present on the list endpoint but not returned by the detail endpoint
• Documented that members[] objects include a membership-scoped id field in the detail view that is absent from the list view

Subgroups (subgroups.md)

• Added !!! warning noting that id, parent_id, and creator_user_id are returned as integers in subgroup responses, unlike the rest of the API which uses strings
• Added previously undocumented field message_edit_period (value: 15) to both Index and Show response examples
• Added last_message_updated_at to the messages object in subgroup responses — this field is present on subgroups but absent from the standard group messages object
• Added !!! note clarifying the above distinction

How this was verified

All schema changes were verified via live API capture using a working GroupMe MCP server against real group data.

[AlureonTheVirus]

Hey! These changes look good. I'm a little confused by your comment "All schema changes were verified via live API capture using a working GroupMe MCP server against real group data."What exactly is your process here? There are no public sandbox APIs for GroupMe, and as far as I'm aware, MCP stands for model context protocol.On Mar 19, 2026 4:09 PM, Quinn ***@***.***> wrote:What's changed GET /groups/:id (index.md) Added full response schema table documenting all fields returned by the detail endpointAdded List vs Detail comparison table clarifying which fields are exclusive to the detail view (members, messages metadata) vs the index endpointCorrected the example response to remove the messages.preview block, which is present on the list endpoint but not returned by the detail endpointDocumented that members[] objects include a membership-scoped id field in the detail view that is absent from the list view Subgroups (subgroups.md) Added !!! warning noting that id, parent_id, and creator_user_id are returned as integers in subgroup responses, unlike the rest of the API which uses stringsAdded previously undocumented field message_edit_period (value: 15) to both Index and Show response examplesAdded last_message_updated_at to the messages object in subgroup responses — this field is present on subgroups but absent from the standard group messages objectAdded !!! note clarifying the above distinction How this was verified All schema changes were verified via live API capture using a working GroupMe MCP server against real group data. You can view, comment on, or merge this pull request online at:   #45 Commit Summary 3ba1df0 docs: document GET /groups/:id full schema and list vs detail deltaaf4bc2f docs: add verified subgroup schema fields, preview object, and single subgroup endpoint6ac5144 fix File Changes (2 files) M docs/api/groups/index.md (73) M docs/api/groups/subgroups.md (86) Patch Links: https://github.com/groupme-js/GroupMeCommunityDocs/pull/45.patchhttps://github.com/groupme-js/GroupMeCommunityDocs/pull/45.diff —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>