Add closed attribute to signups in Registrations API

[symmetry-admin]

Related Product
Which product is this feature related to?

Registrations

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

I need to use the API to determine if a signup is closed or not so I can disable the button on our website that links to the registration page on Church Center. If the registration status is set to "Open" with "Close registration automatically" set, then the close_at attribute is set and I can use that. However, if the registration status is just "Closed", there is no attribute that shows then when fetching a signup (close_at is null and open_at is null)

Describe the solution you'd like

Add a boolean closed attribute when fetching a signup

Describe alternatives you've considered

It looks like the internal API has a closed attribute that is used on the Church Center website, but I cannot use the internal API
https://api.churchcenter.com/registrations/v2/events/{id}

Additional context

API endpoint: /registrations/v2/signups/{id}

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:

🟣 #1374 — Apis under registration/v2/signups/{id}/selectiontypes works in API Explorer but not when url is called in a browser (Closed)

Summary: This issue involved incorrect URL links being returned in the signup API response - specifically, links were still referencing the old 'events' endpoints instead of the new 'signups' endpoints when accessing selection_types and attendee_types data.

Key discussion points:

• The links in the API response were using outdated 'events' endpoints instead of 'signups' endpoints
• The user was getting 404 errors when trying to access selection_types endpoint
• The problem was initially thought to be a bug in the API, but was actually due to the user not updating their API version header to the new version (2025-05-01)

Resolution: User resolved the issue themselves by updating the API version in their console. The problem was not with the API itself, but with the user still using the legacy API version rather than the new 2025-05-01 version. Once the version header was updated, the correct signup endpoints were returned.

🟣 #1369 — Registration Attendees, ordering/filtering by updatedat (Closed)

Summary: This feature request asked for an endpoint to fetch all registration attendees with ordering/filtering by updated_at, rather than having to page through all signups and make individual requests for each signup's attendees - similar to what the new issue is requesting for determining signup status.

Key discussion points:

• The user needed to keep an up-to-date list of all registered attendees but the current approach required one API call per signup, which was very slow
• They wanted a theoretical registrations/v2/attendees endpoint with ordering by updated_at
• The legacy unofficial API had this endpoint but without proper ordering capabilities
• User noted that filtering with 'where' clauses isn't generally applicable across all endpoints in the API

Resolution: The Planning Center team confirmed that recreating the legacy /attendees endpoint is on their backlog, though it wasn't included in the initial public release due to performance considerations that need to be addressed first. The team also fixed some related 500 errors the user discovered. The issue was closed as acknowledged but not yet implemented.

---

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

[symmetry-admin]

An alternative solution could be setting close_at to the current datetime (instead of null) when setting the registration status to Closed

[robertleib]

@symmetry-admin these attributes should be available now (open and closed booleans)

[symmetry-admin]

Awesome, thanks!