See Registration Type via API

[teharmond]

Related Product
Which product is this feature related to?
Registrations

Is your feature request related to a problem? Please describe.
Simple count and named attendees have different ways to best get registrant info. With simple counts, the only option is to get the registrant contact and the count. However, for named attendees, the attendees endpoint is more accurate to if that specific person has signed up. Without knowing what type of registration it is, it's a bit of a guess on which data-point is best to use.

Describe the solution you'd like
Ideally the signup endpoint would return a signup_type value.

Describe alternatives you've considered
I'm currently just pulling both for all registrations. It works okay for my use case, but I'd love a bit more detail.

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:

🟢 #1485 — BUG: All calls to /registrations/v2/signups/:id/registrations return 403 (Open)

Summary: Users experienced widespread 403 Forbidden errors when accessing registration-related endpoints (both /signups/:id/registrations and /registrations/v2/registrations). While not directly related to the new issue's feature request, this demonstrates that the registrations API has had stability issues and that accessing registration data through different endpoints can be problematic.

Key discussion points:

• The issue affected multiple organizations and broke integrations for over 100 customers starting June 10-11, 2026
• Both PAT and OAuth 2.0 authentication methods were affected, and even Organization Administrators were denied access
• The problem was vertex-wide, blocking RegistrationVertex collection access while sibling resources (signups, attendees) remained accessible
• Multiple users confirmed timing and cross-organization impact

🟢 #1488 — Obtain registration "total due" from API (Open)

Summary: Users requested access to financial fields (total_due, balance_due_cents, total_payments) via the API for registrations. Currently these fields are only available in browser sessions using the private API but not through PAT requests. This relates to the new issue as both request additional registration data that exists internally but isn't exposed through the public API.

Key discussion points:

• Financial fields like total_due are visible in logged-in browser sessions but not returned via PAT requests to the same endpoint
• User attempted workarounds using price_cents from selection_types but found it unreliable due to discounts and multi-attendee scenarios
• The discrepancy exists because browser sessions use Planning Center's private internal API while PAT requests use the limited public API

---

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

[laurencecasta]

Thanks for the request! This is a deliberate design choice on our end, and we don’t have plans to add this at this field at this time. I’ll close this out for now. Feel free to reopen or reach out if your use case changes or this becomes a blocker.