Need to get a list of discounts applied to each event registration

[vbaarda]

Related Product
Registrations

Describe the question
For each event registration, I need to know the cost and name of each discount applied.

What have you tried that worked?

I cannot find anything that works.

What have you tried that didn't work?

• https://api.planningcenteronline.com/registrations/v2/registrations/xxx has a total_cost_minus_discounts attribute, but it has several problems:
  • It's in whole dollars -- the cents get dropped.
  • All discounts are combined, not listed separately.
  • It assumes I know the total cost for this registration. Not impossible to find, but it takes more API calls.
• https://api.planningcenteronline.com/registrations/v2/registrations/xxx/attendees has no discount information.

Additional context
In the GUI, this information is readily available at https://registrations.planningcenteronline.com/registrations/xxx -- all attendees are listed, along with all discounts applied per attendee. So far I cannot find the same data in the API. Am I just missing it?

I have..

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

🟣 #1395 — Getting Registration Payments via API (Closed)

Summary: Multiple users requested API access to registration payment information for accounting integrations. While related to financial aspects of registrations, this focused on payment records rather than discount details.

Key discussion points:

• Users wanted to query registrations by attendee ID or people ID to check payment status
• Primary use case was syncing payments/donations to QuickBooks Online for accounting purposes
• Multiple users expressed interest in this feature over time

Resolution: Feature request was acknowledged and added to the team's backlog for prioritization. As of closure, the team committed to investigating when it could be implemented but no specific timeline was provided.

🟣 #1377 — Registrations Add-ons (Closed)

Summary: User requested API access to registration add-ons, which are additional details associated with registrations that can be viewed in the UI but were not accessible via API at the time.

Key discussion points:

• Add-ons store important additional details but couldn't be exported via API
• User suggested add-ons should be available as an includable item on relevant endpoints
• Alternative considered was using user-defined fields if they existed

Resolution: Feature request was acknowledged by the team and added to their board to be prioritized alongside other work items. The issue was closed with acknowledgment but no implementation timeline.

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

Summary: Users needed a more efficient way to retrieve all registration attendees and keep the list updated, requesting filtering/ordering by updated_at timestamp. The current approach required paginating through signups and making individual requests for each signup's attendees.

Key discussion points:

• The legacy unofficial API had a /attendees endpoint that was more efficient but lacked proper ordering capabilities
• Users wanted to filter by updated_at to only fetch records changed since their last sync
• Similar efficiency issues existed with the Services API requiring per-person requests
• Two endpoints were throwing 500 errors which were discovered and reported

Resolution: The team confirmed that recreating the legacy /attendees endpoint with proper filtering/sorting is on their backlog. The 500 errors were fixed quickly. For the similar Services API request, users were directed to open a separate issue.

🟣 #1337 — Method of Retrieving Registration Information (Closed)

Summary: User needed to retrieve detailed registration information including custom questions (church attendance) and attendee questions (allergies) for camp registrations, but found the current API required hundreds of individual calls and didn't expose all needed data.

Key discussion points:

• Current approach required paginating through attendees then making individual API calls to People endpoint for each person's details
• Some required information (church attendance from registration questions, allergies from attendee questions) was not accessible via API at all
• Manual CSV export worked but wasn't automated
• Over 800 registrants required making 800+ API calls

Resolution: Team acknowledged there was no programmatic CSV retrieval available. They committed to investigating making more person information available via the attendees endpoint and exploring access to questions/answers data, but provided no specific timeline or implementation details.

---

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

[vbaarda]

The Potentially Related Issues are interesting, but they are not really related to this use case.

[mikereinmiller]

Thanks for the detailed write-up — it really helps to understand exactly what you need.

To give you some context on where things stand: we're moving third-party API access to a new public API. The endpoints you're currently using will eventually be gone. You can opt into the new public API today by including the X-PCO-API-Version: 2025-05-01 header in your requests.

I do want to be upfront with you though — the cost and discount information you're looking for isn't available in the new public API yet, and we're no longer adding new features to the current API. Future development is focused on the new public API.

We understand this is a real gap for your use case. The underlying data is all there on our end — discount names,
amounts, types per attendee — it just hasn't been surfaced through the public API yet. I'm adding this as a feature
request to our backlog. I can't commit to a timeline, but we will work on getting this prioritized for you.

In the meantime, if it helps to know what's coming, the new public API is where to focus your integration going
forward. So if there are additional missing features on the new public API, we would love to hear about them.

[vbaarda]

@mikereinmiller -- thanks for the information. For your backlog, a user story might be helpful:

As a member of the finance team, I need to charge discounts to more than one budget in QuickBooks. For example, early-bird discounts get charged to the ministry in charge of the camp, but employee discounts get charged to an account in our all-church Special Events budget. Therefore, for each event registration, I need to know the cost and name of each discount applied.

Here's an example from the GUI of exactly what I need:

[bcannon-scc]

Hi there - @mikereinmiller - I thought this would be a good place to include two missing features our organization would find helpful on the new public API for registrations.

1. User Story: API Exposure for Registration Attendance
   As a Developer or Data Analyst using the Registrations API,

I want to access attendance session data and "present" markers via API endpoints,

So that I can generate accurate reports on actual event attendance rather than just registration intent mirroring the 'Attendance' registrations UI feature.

2. User Story: Expose Custom Question Responses in Registrations API
   As a developer or church administrator using Planning Center,

I want to access signup questions and attendee responses via the Registrations API v2,

So that I can automate event reporting and data workflows without having to perform manual CSV exports from the web interface.

These may already be on your all's radar but wanted to share -- thanks!

[mikereinmiller]

@bcannon-scc Thanks for the feedback! These features are already on our roadmap, and input like this helps us prioritize. We appreciate it!

[hodgendazs]

It would be helpful to have a payment_status or paid field on the Attendee object so we can determine whether someone has completed payment for their registration — not just whether they’ve finished filling out their forms. Currently there’s no way to get this from the API without going outside the Registrations module.​​​​​​​​​​​​​​​​ I also checked the 2025 API you referenced and there doesn’t seem to be anything for that as well.