Form Submission API

[sGerli]

Related Product
Which product is this feature related to?

People Forms

Is your feature request related to a problem? Please describe.

Native forms lack the following features:

• Forms in spanish

• Have them fully integrated into our site

• This is more related to registrations but a Forms API could also help, but to use our own payment processor as we are in Costa Rica and Stripe is not available here, so we need to use local payment processors

Reference: https://community.planningcenter.com/c/api-development/submit-form-via-api

Describe the solution you'd like

Have a type of forms that can only be submitted through the api with an organizational access token. That way form response values can be collected in Planning Center and can properly relate to people. Our authentication service knows the people id of the user, so that can be used to submit the form and link it to the correct user.

Describe alternatives you've considered

Creating custom forms and saving the results in our own database.

Additional context

I have..

• Reviewed the documentation found at https://developer.planning.center/docs
• Searched for previous issues asking for this feature request
• Removed all private information from this issue (credentials, tokens, emails, phone numbers, etc.)
• Reviewed my issue for completeness

[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:

🟣 #1465 — Google App Script downloading .heic form attachments (Closed)

Summary: This issue dealt with downloading form submission attachments via the People API, specifically problems with .heic files in Google Apps Script. While not directly about form submission, it demonstrates that form submissions and their attachments are accessible through the People API's existing read endpoints.

Key discussion points:

• Form submissions can be fetched from the People API with attachment URLs (s3.amazonaws.com links)
• The issue was specific to Google Apps Script's limitations with HEIC files, not a Planning Center API problem
• Planning Center doesn't do anything special with file types - attachments are served directly from S3

Resolution: Confirmed as a Google Apps Script limitation, not a Planning Center API issue. The API successfully serves all file types including HEIC files; the problem was with GAS's UrlFetchApp.fetch() method handling large HEIC metadata.

🟣 #1455 — Archive forms via API (Closed)

Summary: User requested the ability to archive or delete forms programmatically via the API to manage stale forms. This is highly relevant as it demonstrates that the Forms endpoints are currently read-only, which is a key limitation for the form submission API feature request.

Key discussion points:

• User discovered they could patch the undocumented 'active' attribute on forms, but this only stops new submissions rather than archiving
• The /forms endpoints are intentionally read-only by design
• There is no current API support for archiving or deleting forms

Resolution: Planning Center confirmed that /forms endpoints are intentionally read-only. The request was added to their internal feature request board for future consideration, but no write operations (including archive/delete) are currently supported.

🟣 #1466 — POST option for Groups shared resources (Closed)

Summary: User requested POST/write access to Groups resources endpoint to automate posting sermon discussion guides. While this is about Groups rather than People Forms, it demonstrates a broader pattern of Planning Center limiting write access on certain API endpoints that are currently read-only.

Key discussion points:

• Groups API only supports GET operations for resources, no POST/PATCH/DELETE
• The OpenAPI spec showed resource_attributes as non-read-only, suggesting write support was considered
• User wanted to automate weekly content posting that was previously done manually through UI

Resolution: Planning Center confirmed that creating/updating resources is not currently accessible via the Groups API. The request was added to their internal tracking system for future Groups API improvements, but no timeline was provided for implementation.

---

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