POST option for Groups shared resources

[dwelc023]

Related Product: Groups

Describe the question:
The Groups API endpoint seems to only support GET as I couldn't find any reference to POST, PATCH, or DELETE endpoints anywhere in the docs (/groups/v2/groups/{group_id}/resources or /groups/v2/group_types/{group_type_id}/resources).

Is creating/updating group resources via the API currently supported or planned? We're trying to automatically post a weekly sermon discussion guide (DOCX) to our group types after each service.

Additional context:
The resource_attributes in the OpenAPI spec defines name, description, type, visibility as non-read-only fields, suggesting write support was intended. The existing "Sermon Unifying Question" resources and sermon discussion guides in our groups were created manually through the UI. We're trying to automate that step.

[github-actions]

Potentially Related Issues

I found some existing issues that may be related to this one. Please check if any of them address your question before waiting for a response:

🟣 #1367 — Allowing posting for Groups resources (Closed)

Summary: User requested POST/write access to Groups resources endpoint to programmatically add linked resources (files). This is the same core functionality requested in the new issue - ability to create/update group resources via API instead of manual UI entry.

Key discussion points:

• User attempted to POST to resources endpoint but received a permissions error
• Primary need was for linked resources, with file resources as secondary
• Alternative of manual entry was not viable for their use case
• A follow-up commenter requested write access to group memberships (different from resources), which was confirmed to already exist in the API

Resolution: Planning Center confirmed that creating/updating resources is not currently accessible via the API. The request was noted in their internal tracking system for future Groups API improvements. The issue was closed without a timeline for implementation.

🟣 #1459 — Groups API event description write permission (Closed)

Summary: User tried to PATCH/update a Groups Event description field via OAuth app with groups scope but received 403 Forbidden, despite having UI edit permissions. This demonstrates another area where Groups API write operations are restricted.

Key discussion points:

• User had proper OAuth scope (groups) and could successfully GET event data
• The same user could edit event descriptions in the UI but not via API
• Received 403 error specifically stating user cannot update EventVertex

Resolution: Planning Center confirmed that most of the Groups API is currently read-only, including Events-related endpoints. The request was added to their internal tracking system for future Groups API improvements. No timeline provided for write access implementation.

🟣 #1462 — Feature Request: Add a /groups/v2/attendances?wheregroup=123456 endpoint (Closed)

Summary: User requested more efficient bulk endpoint for retrieving group attendance records to avoid making one API request per event. While focused on read operations rather than write, it illustrates ongoing Groups API feature development priorities.

Key discussion points:

• Current approach required individual API calls per event, inefficient for groups with long history
• Requested either a filtered attendances endpoint or group-scoped attendance endpoint
• CSV export via UI exists but isn't automation-friendly

Resolution: Planning Center acknowledged the feature request and added it to their tracker for attendance API improvements. Issue was closed without implementation, following the pattern of Groups API requests being tracked internally for future development.

---

This comment was generated automatically. If none of these match your issue, no action is needed — a team member will review your issue soon.

[americanmouths]

Hi @dwelc023 thanks for the request! Creating and updating resources isn't something our API supports right now but I've added it to our internal tracker as a feature request so we can consider it as we continue building out the Groups API.

I'm going to close this issue, but please don't hesitate to reach out if you have other questions or run into anything else!