Partner API Documentation

Fund My Squad (FMS) is a fundraising platform for youth sports. The Partner API lets external platforms (league management, team apps, registration software) offer built-in fundraising to their users. Partners earn commission on every donation processed through fundraisers created via their integration.

Integration Flow:

┌─────────────────────────────────────────────────────────────────┐
│                     PARTNER INTEGRATION FLOW                     │
└─────────────────────────────────────────────────────────────────┘
1. SETUP
   Apply at /partners → Get staging API key → Build & test in sandbox
2. CREATE FUNDRAISER (your platform → FMS API)
   Your user wants to fundraise
   → POST /partner/v1/fundraisers {title, goalAmount, externalId}
   → FMS returns id, publicUrl, donateUrl
3. COLLECT DONATIONS (donors → FMS hosted page)
   Share the donateUrl or embed link
   → Donor visits FMS donation page
   → FMS processes payment via Stripe
4. ENABLE PAYOUTS (fundraiser creator → Stripe Connect)
   POST /partner/v1/fundraisers/:id/connect/onboard
   → Redirect user to Stripe onboarding
   → User completes KYC/banking setup
5. TRACK & DISPLAY (FMS API → your platform)
   GET /partner/v1/fundraisers/:id → Show progress
   GET /partner/v1/fundraisers/:id/donations → Show donors
6. COMMISSION PAYOUT (automatic on each donation)
   Donor pays $100 → Stripe fee ~$3.20
   → Platform fee (10%): $10.00
     → Partner commission (e.g. 4%): $4.00
     → FMS keeps: $6.00
   → Fundraiser creator receives: $86.80

Quick Start: 1. Apply at https://fundmysquad.com/partners 2. Once approved, log in to the Partner Portal 3. Generate a staging API key from the API Keys tab 4. Test all endpoints in the Sandbox tab 5. Request a production API key 6. Integrate into your platform and go live

Full machine-readable docs: https://fundmysquad.com/llms.txt

All API requests require your partner API key in the x-partner-api-key header:

curl https://api.fundmysquad.com/partner/v1/fundraisers \
  -H "x-partner-api-key: fms_partner_abc123..."

Base URL: Always use https://api.fundmysquad.com for all requests.

Environments:

Partners always use the same base URL. The API detects whether your key is staging or production and routes accordingly. Staging key requests never touch the production database.

POST /partner/v1/fundraisers

Required fields:

curl -X POST https://api.fundmysquad.com/partner/v1/fundraisers \
  -H "x-partner-api-key: fms_partner_abc123..." \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Tigers Spring Travel Fund",
    "goalAmount": 5000,
    "goalType": "team",
    "externalId": "team_8472",
    "sport": "baseball",
    "endsAt": "2026-06-01T00:00:00Z"
  }'

Returns the created fundraiser with its id, publicUrl, and donateUrl.

GET /partner/v1/fundraisers

Query parameters:

curl "https://api.fundmysquad.com/partner/v1/fundraisers?externalId=team_8472&status=active" \
  -H "x-partner-api-key: fms_partner_abc123..."

GET /partner/v1/fundraisers/:id

Returns full details including current stats (raised amount, donation count, supporter count, progress %) and the 10 most recent donations.

Lookup by external ID:

GET /partner/v1/fundraisers/by-external-id/:externalId

PATCH /partner/v1/fundraisers/:id

Updatable fields: title, description, goalAmount, startsAt, endsAt, category, sport, heroImageUrl, externalId, metadata

Only include the fields you want to change. Omitted fields are left unchanged.

curl -X PATCH https://api.fundmysquad.com/partner/v1/fundraisers/abc123... \
  -H "x-partner-api-key: fms_partner_abc123..." \
  -H "Content-Type: application/json" \
  -d '{ "goalAmount": 7500 }'

Close a fundraiser:

POST /partner/v1/fundraisers/:id/close

Reopen a closed fundraiser:

POST /partner/v1/fundraisers/:id/reopen

List donations:

GET /partner/v1/fundraisers/:id/donations?limit=50&offset=0

Fundraiser stats (with 14-day trend):

GET /partner/v1/fundraisers/:id/stats

Portfolio summary:

GET /partner/v1/summary

Onboard a fundraiser creator for payouts:

POST /partner/v1/fundraisers/:id/connect/onboard

Required fields:

{
  "onboardingUrl": "https://connect.stripe.com/...",
  "stripeAccountId": "acct_...",
  "message": "Redirect the fundraiser creator to onboardingUrl..."
}

Redirect your user to onboardingUrl. After completing Stripe's KYC/banking setup, they'll be redirected to your returnUrl.

Check Connect status:

GET /partner/v1/fundraisers/:id/connect/status

Returns connected (boolean), chargesEnabled, payoutsEnabled, detailsSubmitted.

Commission splits: When a donation is made to a partner-created fundraiser with a connected payout account:

POST /partner/v1/connect/onboard

GET /partner/v1/connect/status?externalOwnerId=...

Attach to a fundraiser — either pass connectExternalOwnerId when creating the fundraiser, or link an existing fundraiser:

POST /partner/v1/fundraisers/:id/connect/link

The per-fundraiser /connect/onboard flow above still works for one-off fundraisers.

Sell products (candy, cookie dough, merch) instead of — or alongside — donations.

Turn on the shop: set shopEnabled: true when creating a fundraiser (or PATCH it on later), plus optional shopHeadline and shopDescription. Adding the first product also enables the shop automatically.

curl -X POST https://api.fundmysquad.com/partner/v1/fundraisers \
  -H "x-partner-api-key: fms_partner_abc123..." \
  -H "Content-Type: application/json" \
  -d '{ "title": "Tigers Candy Sale", "goalAmount": 2000, "externalId": "team_8472", "shopEnabled": true }'

Payouts required: a shop only accepts orders once the creator finishes Stripe Connect onboarding. Until then checkout returns PAYOUT_NOT_CONFIGURED.

Three ways to stock a shop: a pre-configured bundle (simplest), individual catalog products by id, or fully custom products you supply & ship.

Browse the same platform-fulfilled products website users pick from.

List catalog products:

GET /partner/v1/catalog/products

List bundles (curated packs):

GET /partner/v1/catalog/bundles

Add a whole bundle in one call:

POST /partner/v1/fundraisers/:id/bundles

Requires products:read to browse, products:write to add.

Add a product:

POST /partner/v1/fundraisers/:id/products

GET    /partner/v1/fundraisers/:id/products
PATCH  /partner/v1/fundraisers/:id/products/:productId
DELETE /partner/v1/fundraisers/:id/products/:productId

List orders:

GET /partner/v1/fundraisers/:id/orders?status=&source=&limit=50&offset=0

Single order:

GET /partner/v1/fundraisers/:id/orders/:orderId

Product sales also appear in fundraiser stats (a productSales block + combinedRaisedAmount) and in GET /partner/v1/summary. Requires products:read.

Error format:

{ "error": "description of what went wrong" }

External IDs: The externalId field bridges your platform and FMS. Pass your unique identifier for teams or users. Create multiple fundraisers for the same team and look them all up with one call.

Partner Metadata: The metadata field is a free-form JSON object. Store league info, coach contacts, season details — FMS preserves it as-is.

Scopes:

Sandbox vs Production: Staging API keys create sandbox fundraisers (not public, no real donations). Production keys create real fundraisers that accept real donations.