← All integrations

Daffy

15 operations0 webhooks

Donor-advised fund platform for charitable giving, gifts, and nonprofit search.

Get started with Daffy on Corsair Hub

Complete your first operation in <1 min

Get started

Supported operations

  • Cancel DonationDestructive

    Cancel a pending donation owned by the API key holder.

  • Create DonationWrite

    Create a donation to a nonprofit (minimum $10 USD).

  • Get BalanceRead-only

    Retrieve the authenticated user's fund balance.

  • Get ContributionsRead-only

    List contributions made to the authenticated fund.

  • Get DonationRead-only

    Retrieve a single donation by user and donation ID.

  • Get DonationsRead-only

    List donations made by the authenticated user.

  • Get User By UsernameRead-only

    Retrieve a public user profile by username.

  • Get User CausesRead-only

    Retrieve a user's supported charitable causes.

  • Get User DonationsRead-only

    Retrieve a user's public donations.

  • Get User ProfileRead-only

    Retrieve the authenticated user's profile.

FAQ

Install corsair and @corsair-dev/daffy, add the Daffy plugin, and connect with an API key. Then call methods like corsair.daffy.api.accounts.cancelDonation() from your app. Corsair keeps each tenant isolated.

Yes. Daffy requires an API key from your Daffy account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Daffy, GitHub, Notion, Stripe, and the rest. Trigger Daffy from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for donor-advised fund platform for charitable giving, gifts, and nonprofit search. Common builds include sync jobs, admin tooling, and agents that call Daffy APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Daffy API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/daffy in the open repo. When Daffy ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Daffy data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Daffy data on your behalf.