DonorSync API

Name: DonorSync API API
Brand: DonorSync API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbasic2 EndpointsREST

For Agents

Record donations in DonorSync and verify API credentials so an agent can confirm connectivity before posting contribution data.

Quickstart

Get started with DonorSync API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"record a donation in DonorSync"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with DonorSync API API.

Verify DonorSync API credentials by calling the /me connection test endpoint

Post a new donation record with donor identity, amount, and designation fields

Confirm successful donation creation and capture the returned donation identifier

Drive an external fundraising form to push contributions into DonorSync as they happen

GET STARTED

Start building with DonorSync API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for DonorSync API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for DonorSync API, keeping it validated and agent-ready. DonorSync provides a lightweight donation management interface for nonprofits and fundraising platforms to record donor contributions and verify connectivity. The API exposes a credential test endpoint and a donation creation endpoint, both authenticated via HTTP Basic credentials. It is designed to be embedded inside donor management workflows where a contribution event needs to be posted to DonorSync as the system of record.

Use Cases

Patterns agents use DonorSync API API for, with concrete tasks.

★ Form-to-CRM Donation Capture

Push donations submitted through a public fundraising form directly into DonorSync as the donor record of truth. Each form submission triggers a POST to /donation/create with donor name, amount, and campaign metadata so finance and stewardship teams see contributions in near real time without manual entry. Integration completes in a few hours given the two-endpoint surface and HTTP Basic authentication.

Submit a donation of $100 USD for donor jane@example.com tagged to the 'Spring Campaign' via POST /donation/create and return the resulting donation id.

Credential Health Monitoring

Run a scheduled connectivity check against DonorSync before nightly donation batches to catch revoked or rotated credentials early. The /me endpoint accepts the same HTTP Basic credentials and returns a quick success or failure signal, letting operations teams alert on auth drift before donor data is queued. This adds a 50ms preflight to existing pipelines.

Call POST /me with the configured DonorSync credentials and report whether authentication succeeded before the nightly donation upload runs.

Recurring Donation Replication

Mirror recurring donation events from a billing system into DonorSync so stewardship teams have a single view of giving history. As each successful charge clears upstream, the agent posts a corresponding donation to /donation/create with the donor identifier and amount. The two-call flow keeps the integration simple and avoids holding a write queue in the billing platform.

On each successful Stripe charge for a donor, create a matching DonorSync donation via POST /donation/create with the same amount and donor email.

AI Agent Donation Capture

Through Jentic, an AI agent can take a natural-language instruction such as 'record a $50 donation from John Doe to the literacy program' and resolve it to the DonorSync /donation/create call without browsing docs. Jentic handles credential injection and schema validation, so the agent only supplies the structured donation fields. End-to-end setup is under an hour after sign-up.

Use Jentic search for 'record a donation in DonorSync', load the donation create operation, and execute it with donor name, email, amount, and campaign tag.

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for donorsync api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/me

Test API connection and credentials

POST

/donation/create

Create a donation record

POST

/me

Test API connection and credentials

POST

/donation/create

Create a donation record

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

DonorSync HTTP Basic credentials are stored encrypted in the Jentic vault and injected only at execution time. The agent sees a scoped reference, never the raw username and password.

Intent-based discovery

Agents search by intent (e.g. 'record a donation in DonorSync') and Jentic returns the matching /donation/create operation with its input schema, so the agent calls the right endpoint without browsing DonorSync docs.

Time to first call

Direct DonorSync integration: a few hours for HTTP Basic auth wiring and donation payload mapping. Through Jentic: under 30 minutes from sign-up to first successful donation write.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Stripe API

Stripe processes the actual card payment; DonorSync records the donation against the donor.

Use Stripe when the agent needs to charge a card. Use DonorSync when the agent needs to log the resulting contribution against a donor record.

Complementary

PayPal Invoicing API

PayPal Invoicing handles the donor-facing invoice; DonorSync stores the resulting donation record.

Use PayPal Invoicing when the donor needs an invoice or a hosted pay link. Use DonorSync to persist the contribution after payment clears.

Complementary

Mailchimp Marketing API

Mailchimp powers the donor outreach; DonorSync owns the donation history.

Use Mailchimp to send the appeal or thank-you email. Use DonorSync to record the gift that the appeal generated.

FAQs

Specific to using DonorSync API API through Jentic.

Why is there no official OpenAPI spec for DonorSync API?

DonorSync does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call DonorSync API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the DonorSync API use?

DonorSync uses HTTP Basic authentication. You send your username and password as a base64-encoded Authorization header on every request. When called through Jentic, those credentials are stored encrypted in the Jentic vault and injected at execution time, so the raw values never enter the agent's context.

Can I create donations through the DonorSync API?

Yes. POST /donation/create accepts the donor identifying fields, the contribution amount, and campaign metadata, and returns a donation identifier on success. This is the primary write operation in the API.

How do I verify my DonorSync credentials are valid?

Call POST /me with your HTTP Basic credentials. A 2xx response confirms the credentials authenticate, which is useful as a preflight check before pushing donation batches.

How do I record a donation with DonorSync through Jentic?

Run pip install jentic, search for 'record a donation in DonorSync', load the donation create operation, and execute it with the donor and amount fields. Jentic returns the structured input schema so the agent can build a valid request without reading API docs.

What are the rate limits for the DonorSync API?

The published spec does not declare explicit rate limits. Build retry-with-backoff into your client and treat any 429 response as the signal to slow down. For high-volume imports, contact DonorSync directly to confirm thresholds.