FundlyHub API
Build powerful fundraising integrations with the FundlyHub REST API.
Base URL
https://api.fundlyhub.org/api/v1
What you can do
| Capability | Endpoint | Auth |
|---|---|---|
| List fundraisers | GET /fundraisers | No |
| Create a campaign | POST /fundraisers | Session |
| Accept donations | POST /donations | Session |
| Process payments | POST /payments/create-intent | No |
| Search everything | GET /search?q=… | No |
| Manage organizations | CRUD /organizations | Session |
Architecture
FundlyHub uses a 3-database architecture:
- Primary DB — Core transactional data (fundraisers, donations, users)
- Events DB — Domain events for async workflows
- Analytics DB — Read-optimized projections for dashboards
The REST API provides synchronous operations. The Event System enables asynchronous processing, CQRS projections, and saga orchestration.
Authentication
Most write endpoints require an authenticated session via AWS Cognito. Sessions use httpOnly cookies — include credentials: 'include' in fetch calls.
bash
# Sign in first to set session cookies, then use cookie jar
curl -b cookies.txt -c cookies.txt \
https://api.fundlyhub.org/api/v1/fundraisersCore Features
| Feature | Details |
|---|---|
| Automatic Caching | 5-minute TTL for improved performance |
| Retry Logic | Exponential backoff with 3 retries |
| Row Level Security | Built-in data access policies |
| Real-time Updates | WebSocket subscriptions available |
| 54 Domain Events | Across 6 domains for async workflows |
| Full-text Search | tsvector with fuzzy matching |
Next Steps
- Quick Start — Make your first API call in under 2 minutes
- Authentication — Cognito sign-in, Google SSO, and session management
- Payouts & the money lifecycle — How funds move from held → settled → released → paid out
- Interactive Explorer — Try every endpoint with Swagger UI
- Code Examples — Copy-paste JavaScript and cURL snippets