404 on OpenAPI spec for Registrations

[ntcho]

Affected Product
Which product does this bug affect?

Registrations

Describe the bug

The OpenAPI Description link (https://api.planningcenteronline.com/registrations/v2/open_api/2025-05-01) in https://api.planningcenteronline.com/docs/apps/registrations/versions/2025-05-01 page is returning 404 error.

I have..

• Reviewed the documentation found at https://developer.planning.center/docs
• Searched for previous issues reporting this bug
• 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:

🟣 #1336 — Personal Access Token API Version Lock Bug (Closed)

Summary: User experienced 404 errors when accessing the Registrations API attendees endpoint without explicitly setting the X-PCO-API-Version header, despite having their Personal Access Token (PAT) configured to use version 2025-05-01. This relates to the new issue as both involve accessing the 2025-05-01 version of the Registrations API.

Key discussion points:

• The attendees endpoint returned 404 errors when PAT version settings were configured but the X-PCO-API-Version header wasn't explicitly included
• Adding the X-PCO-API-Version: 2025-05-01 header resolved the issue
• The team attempted to reproduce the PAT version setting issue but couldn't replicate it
• Browser testing defaults to the oldest API version and doesn't use PAT settings

Resolution: The issue was initially marked as resolved when the X-PCO-API-Version header workaround was confirmed. However, the underlying PAT version setting behavior couldn't be reproduced by the team. The team suggested using curl to verify the x-pco-api-processed-as-version header to confirm which version was being used, but there's no follow-up confirmation of whether the PAT setting issue was definitively resolved.

🟣 #1333 — Registrations Attendees 500 Errror (Closed)

Summary: User encountered 500 Internal Server Error and then 403 Forbidden errors when accessing deeply nested Registrations resources (attendees and emergency contacts). While this issue dealt with different error codes than the new issue's 404, both involve problems accessing the Registrations API's 2025-05-01 version endpoints.

Key discussion points:

• Initially returned 500 errors when accessing /signups/{signup_id}/attendees/{attendee_id}
• After a fix was deployed, the endpoint worked but nested links returned 403 Forbidden errors despite org admin rights
• Permissions were not being handled correctly for deeply nested resources
• Workaround was to use include=emergency_contact parameter instead of accessing nested endpoints directly

Resolution: Resolved on July 8, 2025. The team deployed a fix that corrected permission handling for deeply nested resources in the Registrations API, allowing proper access to attendee-related endpoints and their nested resources.

🟣 #1331 — Registrations Signups Attendees: 404 error (Closed)

Summary: User received 404 errors when accessing both /registrations/v2/attendees and /registrations/v2/signups/{signup_id}/attendees endpoints in the 2025-05-01 version, despite having org admin access and being able to view the same data in the API explorer. This is very similar to the new issue which also reports 404 errors for the 2025-05-01 Registrations version.

Key discussion points:

• 404 errors occurred on attendee endpoints in the 2025-05-01 API version
• The same data was visible and accessible in the API Explorer
• User had Personal Access Token authentication and org admin rights
• The team initially suspected access permission issues but user confirmed org admin status
• Issue required team investigation via email for resolution

Resolution: Resolved on July 8, 2025. The issue was addressed through private email communication with the team. Based on the timing, this was likely resolved by the same fix that addressed issue #1333's permission handling problems for Registrations API endpoints.

---

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

[kapschy]

Thanks for reporting this! We apologize for the inconvenience. We've identified the issue and have a fix in progress. Closing the issue for now, but will post an update once it's resolved.

[kapschy]

@ntcho this issue is now resolved and the Registrations OpenAPI documentation at https://api.planningcenteronline.com/registrations/v2/open_api/2025-05-01 now loads successfully.