Linking Giving.Person to People.Person

[SBTexasFoundationDev]

Related Product
Which product is this question related to?

• API, specifically Giving and People.

Describe the question
Non-anoymous Giving.Donation entries are related to Giving.Person entries. While that gives some useful information (the person's name, addresses, and contact information), it leaves out a lot of the information in People.Person (e.g. age and membership status).

There seems to be some sort of connection between the Giving.Person and People.Person entities behind the scenes; the docs say that Giving.Person.Addresses "can be managed via People", and access tokens for users who aren't authorized to use People can still access People.Person. However, Giving.Person.Id does not necessarily match People.Person.Id.

With that in mind, given a Giving.Person.Id (such as from Giving.Donation's Person relationship), how do I get to the person's People.Person?

What have you tried that didn't work?
Retrieving People.Person and Giving.Donation records, then trying to link them together based on Giving.Donation.Relationships.Person.Data.Id.

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:

🟢 #1467 — Check-ins No person ID (Open)

Summary: This issue addresses a different problem - people records in Check-Ins that lack person IDs entirely. While not directly related to linking Giving.Person to People.Person, it reveals that cross-product person ID relationships can be complex and sometimes problematic in Planning Center's system.

Key discussion points:

• Some Check-Ins person records were found without person IDs, appearing to be duplicate or orphaned records
• The issue appears to be systemic rather than isolated, recurring even after individual duplicates are cleaned up
• Engineering is investigating the root cause of why people records can exist without proper person IDs
• Data cleanup is being performed on a case-by-case basis while the underlying issue is being addressed

---

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