Publishing Pages API Access

[JStuve]

Related Product
Which product is this feature related to?
Publishing

Is your feature request related to a problem? Please describe.
I would like to integration 3rd party webhook events to automatically update Publishing Page content. Specifically, when a new a Mailchimp newsletter is published, directly accessing the ability to update a "Link Image" url, on my "Home" Page, within Publishing, so I can stop manually having to do this.

Describe the solution you'd like
API access to update and manage Publish Page content.

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:

🟢 #1476 — downloading a hashed file eg: sermonaudio (Open)

Summary: User needs to download hosted sermon audio files from Publishing episodes but the API only returns metadata (name, signed_identifier) without documentation on how to access the actual file. While this is about downloading Publishing content rather than updating it, it demonstrates current API access limitations for Publishing file resources.

Key discussion points:

• The episodes API returns sermon_audio with a signed_identifier field but no documented endpoint to retrieve the actual audio file
• User tried multiple approaches and searched documentation without finding a solution
• The issue is currently open with no official response from Planning Center staff

🟢 #1472 — Form Submission API (Open)

Summary: User requests write access to People Forms API to enable custom form submission integration with their authentication system and to work around limitations in native forms. Similar to the new issue, this demonstrates demand for API write capabilities that don't currently exist for form content management.

Key discussion points:

• Native forms lack certain features like Spanish language support and full site integration
• User wants API-only forms that can be submitted via organizational access token to properly link responses to people
• The alternative of maintaining a separate database for custom forms is less desirable
• Bot referenced issue Google App Script downloading .heic form attachments #1465 showing form submissions are readable via API, and Archive forms via API #1455 demonstrating Forms endpoints are currently read-only

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

Summary: User requested POST/PATCH/DELETE capabilities for Groups shared resources to automate uploading weekly sermon discussion guides (DOCX files) to group types. This directly parallels the new issue's request for Publishing write access - both seek to automate content updates that currently require manual UI work.

Key discussion points:

• Groups API resources endpoint only supports GET operations despite OpenAPI spec suggesting write fields exist
• User wanted to automatically post weekly sermon discussion guides after each service rather than manual upload
• A related issue Allowing posting for Groups resources #1367 had the same request for Groups resources write access
• Another related issue Groups API event description write permission #1459 showed Groups Event descriptions also lack write permissions despite appropriate OAuth scopes

Resolution: Planning Center staff confirmed that creating/updating resources is not currently supported in the API. The request was added to their internal tracker for future Groups API improvements consideration. The issue was closed without implementation or timeline provided.

---

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

[soberstadt]

Hi @JStuve! I agree that it would be helpful. At this time, we are not ready to make a publicly available API for pages, but I will file the feature request. Please keep an eye out for future updates in our change log.