---
title: DonorPerfect API Integration on Truto
slug: donorperfect
category: CRM
canonical: "https://truto.one/integrations/detail/donorperfect/"
---

# DonorPerfect API Integration on Truto



**Category:** CRM  
**Status:** Beta

## MCP-ready AI tools

Truto exposes 54 tools for DonorPerfect that AI agents can call directly.

- **list_all_donor_perfect_address_udfs** — List address user defined fields (DPADDRESSUDF table) with a dynamic SELECT, ordered by address_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **create_a_donor_perfect_address** — Add a secondary (seasonal) address for a donor with dp_saveaddress. Returns the new address_id. Required: donor_id. DonorPerfect procedure: dp_saveaddress.
- **update_a_donor_perfect_address_by_id** — Update a secondary address with dp_saveaddress. Every field is overwritten; send all values. Required: id, donor_id. DonorPerfect procedure: dp_saveaddress.
- **list_all_donor_perfect_addresses** — List secondary / seasonal addresses (DPADDRESS table) with a dynamic SELECT, ordered by address_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **get_single_donor_perfect_address_by_id** — Get one row of secondary / seasonal addresses (DPADDRESS table) by address_id with a dynamic SELECT. Required: id.
- **donor_perfect_checkbox_fields_bulk_update** — Set the checked values of one checkbox field for a donor with mergemultivalues: codes in valuestring are checked, all others in that field are unchecked. Required: matchingid, fieldname, valuestring. DonorPerfect procedure: mergemultivalues.
- **create_a_donor_perfect_checkbox_value** — Check one checkbox value (DPUSERMULTIVALUES) for a donor with dp_savemultivalue_xml. checkbox_fields.bulk_update is usually better. Required: matching_id, field_name, code. DonorPerfect procedure: dp_savemultivalue_xml.
- **donor_perfect_checkbox_values_bulk_delete** — Uncheck ALL checkbox values on one screen tab (MAIN, GIFT, PLEDGE, BIO or OTHER) for a donor with dp_deletemultivalues_xml. Irreversible; prefer checkbox_fields.bulk_update to change one field. Required: matching_id, table_name. DonorPerfect procedure: dp_deletemultivalues_xml.
- **list_all_donor_perfect_checkbox_values** — List checked checkbox values (DPUSERMULTIVALUES table) with a dynamic SELECT, ordered by id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **create_a_donor_perfect_code** — Add a code (GL code, solicitation, campaign, ... as in Code Maintenance) with dp_savecode, or update one by setting original_code and overwrite=Y. Required: field_name, code, description. DonorPerfect procedure: dp_savecode.
- **list_all_donor_perfect_codes** — List code values used in drop-downs (DPCODES table; filter by field_name, e.g. GL_CODE, SOLICIT_CODE, CAMPAIGN, FLAG, MEMORY_HONOR) with a dynamic SELECT, ordered by code_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **create_a_donor_perfect_contact** — Create a contact record (activity / task on the Contact screen) for a donor with dp_savecontact. Returns the new contact_id. Required: donor_id. DonorPerfect procedure: dp_savecontact.
- **update_a_donor_perfect_contact_by_id** — Update a contact record with dp_savecontact. Every field is overwritten; send all values. Required: id, donor_id. DonorPerfect procedure: dp_savecontact.
- **list_all_donor_perfect_contacts** — List contact records (DPCONTACT table) with a dynamic SELECT, ordered by contact_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **get_single_donor_perfect_contact_by_id** — Get one row of contact records (DPCONTACT table) by contact_id with a dynamic SELECT. Required: id.
- **list_all_donor_perfect_donor_gifts** — List all gifts of one donor with dp_gifts (a fixed set of fields: gift_id, gift_date2, amount, gl, solicit_code, campaign, record_type, balance...). For other fields use gifts.list with donor_id. Required: donor_id. DonorPerfect procedure: dp_gifts.
- **list_all_donor_perfect_donor_udfs** — List donor user defined fields (DPUDF table, one row per donor) with a dynamic SELECT, ordered by donor_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **get_single_donor_perfect_donor_udf_by_id** — Get one row of donor user defined fields (DPUDF table, one row per donor) by donor_id with a dynamic SELECT. Required: id.
- **donor_perfect_donors_search** — Search donors like the DonorPerfect search screen (% is a wildcard, e.g. last_name=Pa%). Returns donor_id, name, address, gifts and gift_total for each match. DonorPerfect procedure: dp_donorsearch.
- **create_a_donor_perfect_donor** — Create a donor (constituent) with dp_savedonor. Returns the new donor_id as the record value. DonorPerfect procedure: dp_savedonor.
- **update_a_donor_perfect_donor_by_id** — Update a donor with dp_savedonor. IMPORTANT: DonorPerfect overwrites every field of the donor; fields you leave out are cleared. Read the donor first (donors.get) and send all values back with your changes. Required: id. DonorPerfect procedure: dp_savedonor.
- **list_all_donor_perfect_donors** — List donors (DP table: name, address, phones, email, giving totals...) with a dynamic SELECT, ordered by donor_id. The connector pages through all rows 500 at a time (OFFSET/FETCH). modified_since matches COALESCE(modified_date, created_date), the incremental pattern in the DonorPerfect manual.

- **get_single_donor_perfect_donor_by_id** — Get one row of donors (DP table: name, address, phones, email, giving totals...) by donor_id with a dynamic SELECT. Required: id.
- **create_a_donor_perfect_flag** — Set a flag on a donor with dp_saveflag_xml. Fails with a duplicate key error if the flag is already set. Required: donor_id, flag. DonorPerfect procedure: dp_saveflag_xml.
- **donor_perfect_flags_bulk_delete** — Remove ALL flags from a donor with dp_delflags_xml (single flags can't be removed). Read them first with flags.list and re-add the ones to keep. Required: donor_id. DonorPerfect procedure: dp_delflags_xml.
- **list_all_donor_perfect_flags** — List donor flags (DPFLAGS table) with a dynamic SELECT, ordered by donor_id, flag. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **create_a_donor_perfect_gift_tribute** — Associate a gift with one or more tributes (dp_tribAnon_AssocTribsToGift). Required: giftid, tributeid_list. DonorPerfect procedure: dp_tribAnon_AssocTribsToGift.
- **list_all_donor_perfect_gift_udfs** — List gift user defined fields (DPGIFTUDF table, one row per gift) with a dynamic SELECT, ordered by gift_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **get_single_donor_perfect_gift_udf_by_id** — Get one row of gift user defined fields (DPGIFTUDF table, one row per gift) by gift_id with a dynamic SELECT. Required: id.
- **create_a_donor_perfect_gift** — Create a gift with dp_savegift (record_type G gift, M main gift of a split, S soft credit; pledges use pledges.create). Pledge payments are gifts with plink = the pledge's gift_id. Returns the new gift_id. Required: donor_id, record_type, gift_date, amount. DonorPerfect procedure: dp_savegift.
- **update_a_donor_perfect_gift_by_id** — Update a gift with dp_savegift. IMPORTANT: every field is overwritten; fields you leave out are cleared. Read the gift first (gifts.get) and send all values back. Also used for gift adjustments (see the README). Required: id, donor_id, record_type, gift_date, amount. DonorPerfect procedure: dp_savegift.
- **list_all_donor_perfect_gifts** — List gifts and pledges (DPGIFT table; record_type G gift, P pledge, M split main, S soft credit) with a dynamic SELECT, ordered by gift_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **get_single_donor_perfect_gift_by_id** — Get one row of gifts and pledges (DPGIFT table; record_type G gift, P pledge, M split main, S soft credit) by gift_id with a dynamic SELECT. Required: id.
- **create_a_donor_perfect_link** — Link two donors (Links tab) with dp_savelink; the reciprocal link is created automatically. Returns the link_id. Required: donor_id, donor_id2, link_code. DonorPerfect procedure: dp_savelink.
- **update_a_donor_perfect_link_by_id** — Update a donor link with dp_savelink. Required: id, donor_id, donor_id2, link_code. DonorPerfect procedure: dp_savelink.
- **list_all_donor_perfect_links** — List donor links (DPLINK table) with a dynamic SELECT, ordered by link_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **create_a_donor_perfect_other_info** — Create an Other Info record for a donor with dp_saveotherinfo. Returns the other_id (use it as matching_id for its user defined fields). Required: donor_id. DonorPerfect procedure: dp_saveotherinfo.
- **update_a_donor_perfect_other_info_by_id** — Update an Other Info record with dp_saveotherinfo. Every field is overwritten; send all values. Required: id, donor_id. DonorPerfect procedure: dp_saveotherinfo.
- **list_all_donor_perfect_other_info** — List Other Info records (DPOTHERINFO table) with a dynamic SELECT, ordered by other_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **get_single_donor_perfect_other_info_by_id** — Get one row of Other Info records (DPOTHERINFO table) by other_id with a dynamic SELECT. Required: id.
- **list_all_donor_perfect_other_info_udfs** — List Other Info user defined fields (DPOTHERINFOUDF table) with a dynamic SELECT, ordered by other_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **create_a_donor_perfect_payment_method** — Store an EFT payment method reference (SafeSave vault, masked card or bank digits) for a donor with dp_PaymentMethod_Insert. Only for systems with EFT Transactions enabled; never send full card numbers. Required: donor_id, accounttype, dppaymentmethodtypeid. DonorPerfect procedure: dp_PaymentMethod_Insert.
- **list_all_donor_perfect_payment_methods** — List EFT payment method references (DPPAYMENTMETHOD table) with a dynamic SELECT, ordered by DpPaymentMethodID. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **create_a_donor_perfect_pledge** — Create a pledge (parent recurring commitment, record_type P) with dp_savepledge. Payments are created with gifts.create using plink. Returns the pledge's gift_id. Required: donor_id, gift_date, start_date, total, bill, frequency. DonorPerfect procedure: dp_savepledge.
- **update_a_donor_perfect_pledge_by_id** — Update a pledge with dp_savepledge. IMPORTANT: every field is overwritten; send all values. Required: id, donor_id, gift_date, start_date, total, bill, frequency. DonorPerfect procedure: dp_savepledge.
- **donor_perfect_queries_execute** — Run your own read-only SQL SELECT on the DonorPerfect tables (DP, DPUDF, DPGIFT, DPGIFTUDF, DPCODES, DPADDRESS, DPCONTACT, DPFLAGS, DPLINK, DPOTHERINFO, DPUSERMULTIVALUES, DPPAYMENTMETHOD, ...). At most 500 rows per call; page with OFFSET ... FETCH NEXT. Required: sql.
- **list_all_donor_perfect_tribute_gift_links** — List gift-to-tribute associations (DPTRIBUTESANON_GIFTASSOC table) with a dynamic SELECT, ordered by gift_id. The connector pages through all rows 500 at a time (OFFSET/FETCH).
- **create_a_donor_perfect_tribute_notification** — Create the tribute gift notification record for a recipient (dp_tribNotif_Save); it appears as a Send Notification gift on the recipient. Required: donor_id, glink, tlink, amount, total. DonorPerfect procedure: dp_tribNotif_Save. Optional membership fields (membership_type, membership_level, membership_enr_date, membership_exp_date) are sent only when given.

- **create_a_donor_perfect_tribute_recipient** — Add a notification recipient for one tribute gift (dp_tribAnon_SaveTribRecipient). Follow with tribute_notifications.create. Required: donorid, tributeid, giftid. DonorPerfect procedure: dp_tribAnon_SaveTribRecipient.
- **list_all_donor_perfect_tributes** — List tributes (In Honor Of / In Memory Of) with gift totals and notification names, via dp_tribAnon_MyTribSummary. DonorPerfect procedure: dp_tribAnon_MyTribSummary.
- **donor_perfect_tributes_search** — Search tributes by name with dp_tribAnon_Search. Required: keywords. DonorPerfect procedure: dp_tribAnon_Search.
- **create_a_donor_perfect_tribute** — Create a tribute with dp_tribAnon_Create. Required: name, dpcodeid, activeflg, usercreatedt. DonorPerfect procedure: dp_tribAnon_Create.
- **update_a_donor_perfect_tribute_by_id** — Update a tribute and its notification recipients with dp_tribAnon_Update. Recipients must list ALL recipients (existing ones not listed are removed). Required: id, name, dpcode_id, activeflg, usercreatedt, recipients. DonorPerfect procedure: dp_tribAnon_Update.
- **create_a_donor_perfect_user_defined_field_value** — Set one user defined field (UDF) value on a donor, gift, contact, other info or address record with dp_save_udf_xml (creates or replaces the value). The UDF must already exist. Required: matching_id, field_name, data_type. DonorPerfect procedure: dp_save_udf_xml.

## How it works

1. **Link your customer's DonorPerfect account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app.
2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request.
3. **Call Truto's API to reach DonorPerfect.** The Proxy API is a 1-to-1 mapping of the DonorPerfect API.
4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field.

## Use cases

- **Push external revenue into the nonprofit system of record** — Event ticketing, e-commerce, or peer-to-peer fundraising platforms can offer their nonprofit customers automatic sync of transactions into DonorPerfect as gifts or pledges, mapped to the correct campaign, solicitation, and GL codes.
- **Enrich donor records with external intelligence** — Wealth screening, address verification, and analytics vendors can read constituent data from DonorPerfect, process it externally, and write insights back into User Defined Fields and Flags so fundraisers see actionable data where they already work.
- **Sync audiences for marketing and engagement tools** — Email, SMS, and marketing automation platforms can build two-way constituent sync, using DonorPerfect Flags and Checkbox fields to segment donors (e.g., monthly givers, major gift prospects) without forcing nonprofits to export CSVs.
- **Automate tribute and memorial gift processing** — Checkout and donation-form providers can capture 'In Memory Of' details at the point of sale and create the Tribute, link the Gift, and register Notification Recipients in DonorPerfect so nonprofits can send acknowledgment cards automatically.
- **Log volunteer and engagement activity on the donor record** — Volunteer management and event platforms can push shift hours, RSVPs, and touchpoints into DonorPerfect as Contacts or Other Info entries, giving development teams a unified view of each constituent's engagement.

## What you can build

- **Transactional gift sync with code mapping** — Create gifts and pledges in DonorPerfect with full support for record types (G, P, M, S) and dynamic mapping of Campaign, Solicitation, and GL codes pulled live from the customer's own code lists.
- **Donor dedupe and upsert on checkout** — Search existing donors by email or name before creating a new constituent, preventing duplicate records when pushing transactions from external donation flows.
- **UDF-based write-back for enrichment data** — Write wealth scores, suggested ask amounts, alumni data, or any custom attribute into donor, gift, and other-info User Defined Fields without hardcoding schemas per customer.
- **Flag and checkbox segmentation sync** — Create, bulk update, and bulk delete Flags and Checkbox values to keep DonorPerfect segments aligned with external audience lists in marketing or engagement tools.
- **Soft credit and relationship tracking for peer-to-peer** — Record donations as soft credits against a fundraiser's profile and establish relational links between donors so nonprofits can attribute revenue to the right advocate.
- **Tribute gift capture with notification recipients** — Create Tributes, attach incoming Gifts, and register Tribute Notification Recipients in a single flow so grieving families automatically receive acknowledgment mail.
- **Custom SQL-powered reporting pipelines** — Use DonorPerfect's query execution to run read-only SELECT statements across DP, DPGIFT, and DPUDF tables for high-volume data extraction without hitting hundreds of REST endpoints.

## FAQs

### How does authentication to DonorPerfect work through Truto?

DonorPerfect uses an API key tied to each nonprofit's account. Truto handles the credential capture, storage, and injection on every request, so your end users connect their DonorPerfect account once and your app never touches the raw key.

### How do updates to donors and gifts work given DonorPerfect's overwrite behavior?

DonorPerfect's save endpoints overwrite the entire record. The recommended pattern through Truto is read-modify-write: call the get endpoint (e.g., get_single_donor_perfect_donor_by_id), mutate only the fields you need, and send the full payload back via the update endpoint to avoid erasing existing data.

### Can we write to User Defined Fields (UDFs)?

Yes. Truto exposes list endpoints for donor, gift, address, and other-info UDFs so you can discover each customer's custom schema at runtime, and create_a_donor_perfect_user_defined_field_value lets you write values back into DPUDF or DPGIFTUDF.

### Does the integration support soft credits and split gifts?

Yes. The create and update gift endpoints accept DonorPerfect's record_type values including G (standard gift), P (pledge), M (main split), and S (soft credit), so peer-to-peer, split, and matching gift workflows are all supported.

### Can we run custom SQL queries against DonorPerfect?

Yes. The donor_perfect_queries_execute tool lets you run read-only SELECT statements against DonorPerfect tables such as DP, DPGIFT, and DPUDF, which is useful for batch extraction and complex reporting pipelines.

### How do we handle Campaign, Solicitation, and GL codes that vary per customer?

Use list_all_donor_perfect_codes to pull each nonprofit's active code tables at runtime and expose them in your UI as mapping dropdowns, so gifts are always posted with codes that match the customer's chart of accounts.

### Is data access real-time or batch?

All Truto calls to DonorPerfect are made on-demand in real time. For high-volume use cases like nightly enrichment or reporting, you can combine queries_execute with scheduled jobs in your own system to pull large result sets efficiently.

## Related reading

- [Connect DonorPerfect to Claude: Sync Giving and Tribute Records](https://truto.one/blog/connect-donorperfect-to-claude-sync-giving-and-tribute-records/) — Learn how to connect DonorPerfect to Claude using a managed MCP server to automate fundraising operations, giving records, and tribute workflows.
- [Connect DonorPerfect to ChatGPT: Manage Donors, Gifts, and Pledges](https://truto.one/blog/connect-donorperfect-to-chatgpt-manage-donors-gifts-and-pledges/) — Learn how to connect DonorPerfect to ChatGPT using a managed MCP server. Automate donor research, gift entry, and custom SQL queries without writing integration code.
- [Connect DonorPerfect to AI Agents: Automate Fundraising Operations](https://truto.one/blog/connect-donorperfect-to-ai-agents-automate-fundraising-operations/) — Learn how to safely connect DonorPerfect to AI Agents using Truto's /tools endpoint. Discover how to handle destructive updates, XML payloads, and rate limits.
