GiveLinkDocs
Integrations

Integrations Overview

Connect GiveLink with your existing tools — Stripe, Zapier, webhooks, and more. API-first architecture means everything is programmable.

GiveLink is built API-first. Every feature in the platform — campaigns, donations, donors, subscriptions, events — is accessible through a RESTful API. The dashboard itself is a consumer of this API, which means anything you can do in the UI, you can do programmatically.

This philosophy ensures that GiveLink fits into your existing tech stack rather than replacing it.

All integrations are included at the standard 1% platform fee. There are no premium tiers, integration add-on charges, or per-connection fees.


Available Integrations


Planned Integrations

Salesforce (NPSP + NPC)

Status: In Development

Bi-directional sync between GiveLink and Salesforce, supporting both Nonprofit Success Pack (NPSP) and Nonprofit Cloud (NPC) data models.

  • Sync donations as Opportunities / Gift Transactions
  • Sync donors as Contacts and Accounts
  • Campaign mapping between GiveLink campaigns and Salesforce campaigns
  • Recurring gift sync with Salesforce recurring donation records
  • Custom field mapping configuration

QuickBooks

Status: Planned

Automatically sync donation revenue, refunds, and fee data to QuickBooks Online for streamlined nonprofit accounting.

  • Revenue recognition by campaign and fund
  • Automatic journal entries for donations and refunds
  • Fee categorization (platform fees, processing fees)
  • Monthly reconciliation reports

Have an integration you need? Contact us at hello@givelink.ai — we prioritize integrations based on user demand and can build custom connectors for organizations with specific requirements.


API-First Architecture

The GiveLink REST API is the foundation of every integration. Whether you are using a native connector, Zapier, or building something custom, the API is the source of truth.

API Highlights

FeatureDetails
AuthenticationAPI keys with scoped permissions (read-only, read-write, admin)
FormatJSON request and response bodies
VersioningURL-based versioning (/v1/) with backward compatibility guarantees
PaginationCursor-based pagination on all list endpoints
FilteringQuery parameters for filtering, sorting, and field selection
Rate limiting100 requests per minute per API key
DocumentationFull OpenAPI spec with interactive examples

Common API Use Cases


API Key Management

API keys are managed from Dashboard > Settings > API Keys. Each key has scoped permissions and can be revoked at any time.

Generate a new API key

Click Create API Key, give it a descriptive name (e.g., "Salesforce Sync" or "Data Warehouse"), and select the permission scope: Read Only, Read/Write, or Admin.

Copy the key

The full API key is displayed only once at creation time. Copy it and store it securely. If you lose it, you will need to generate a new key.

Use the key in requests

Include the API key in the Authorization header of every request:

curl -H "Authorization: Bearer gl_live_abc123..." \
     https://api.givelink.ai/v1/donations

Rotate or revoke keys

From the API Keys settings page, you can revoke any key immediately. Revoked keys stop working within 60 seconds. Generate a new key before revoking the old one to avoid downtime.

Never expose API keys in client-side code, public repositories, or browser requests. API keys should only be used in server-side applications. If you believe a key has been compromised, revoke it immediately from the dashboard.


Rate Limiting

All API endpoints are rate-limited to 100 requests per minute per API key to ensure platform stability and fair usage.

Rate Limit Headers

Every API response includes headers indicating your current rate limit status:

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 87
X-RateLimit-Reset: 1709164800
HeaderDescription
X-RateLimit-LimitMaximum requests allowed per minute
X-RateLimit-RemainingRequests remaining in the current window
X-RateLimit-ResetUnix timestamp when the rate limit window resets

When You Hit the Limit

If you exceed the rate limit, the API returns a 429 Too Many Requests response. Your application should:

  1. Read the X-RateLimit-Reset header to determine when to retry
  2. Implement exponential backoff for retries
  3. Queue non-urgent requests to spread them across time windows

If your integration requires higher throughput, contact us at hello@givelink.ai. We offer increased rate limits for organizations with legitimate high-volume use cases like real-time data warehouse syncing.


Zapier Recipes

Get started quickly with these popular Zapier automations:

Donation to Google Sheets

Log every donation to a Google Sheet automatically. Great for finance teams who need a live spreadsheet of incoming gifts.

New Donor to Mailchimp

Add new donors to a Mailchimp audience automatically. Tag them by campaign so you can segment your email outreach.

Donation Alert to Slack

Post a message to a Slack channel every time a donation is received. Include donor name, amount, and campaign. Great for team morale.

Recurring Donor to CRM

When a new recurring subscription is created, automatically create or update a contact in HubSpot, Salesforce, or your CRM of choice.

How is this guide?

On this page