Affiliate program

Recruit an affiliate by hand (they normally join through the program's public signup link). Mints their referral code, portal link, and default tracked link. The result includes their portal URL — a private bearer link to send to that person, and only that person.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.add_affiliate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "name": "Example"
  }'

Over MCP the same operation is the tool affiliate_program_add_affiliate at https://app.chirply.io/api/mcp, same bearer token, same input.

Manually credit a person to an affiliate — for deals that arrived outside the tracked links (a phone call, a conference). Snapshots the program's current reward terms onto the referral; when this person later pays, those terms decide the commission. First touch wins: if the person is already a referral, the existing attribution is returned unchanged.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.add_referral \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_add_referral at https://app.chirply.io/api/mcp, same bearer token, same input.

Approve a pending affiliate (or reactivate a paused one): their referral links start earning attribution and their portal shows them as active.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.approve_affiliate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_approve_affiliate at https://app.chirply.io/api/mcp, same bearer token, same input.

Approve one pending commission, clearing it for payout — this confirms the account owes the money and lets 'Pay an affiliate' claim it.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.approve_commission \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "commission_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_approve_commission at https://app.chirply.io/api/mcp, same bearer token, same input.

Archive a program: its signup page and referral links stop working and no new clicks, referrals, or commissions are tracked. Existing referrals keep their snapshots and commission already earned STAYS OWED — archiving stops future tracking, it does not void money. There is no unarchive in the UI, so treat this as final.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.archive_program \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_archive_program at https://app.chirply.io/api/mcp, same bearer token, same input.

Ban an affiliate — an outward-facing action against a real person: their portal login stops working immediately, their links stop earning, and they can't be paid out while banned. Use for fraud or terms violations; use 'Pause affiliate' for anything temporary.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.ban_affiliate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_ban_affiliate at https://app.chirply.io/api/mcp, same bearer token, same input.

Call off a draft or active contest as if it never happened: no winners are computed, no prizes are owed, and it disappears from every affiliate's portal. Affiliates who were competing lose the contest they were told about — an outward-facing disappointment — and there is no undo.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.cancel_contest \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "contest_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_cancel_contest at https://app.chirply.io/api/mcp, same bearer token, same input.

Call off a payout that hasn't been sent yet: the commissions it claimed return to 'approved' and the affiliate's payable balance is restored. A payout already marked paid can't be canceled.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.cancel_payout \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "payout_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_cancel_payout at https://app.chirply.io/api/mcp, same bearer token, same input.

Create an affiliate contest as a DRAFT — a time-boxed competition with a metric, a window, and prizes by rank. Drafts are invisible to affiliates and cost nothing until you start them (affiliate_program.start_contest); the prizes are your own commitment to deliver, outside Chirply. Ties share a rank and every affiliate tied at a prized rank wins that prize.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.create_contest \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Example",
    "metric": "customers",
    "starts_at": "2026-09-17T15:00:00Z",
    "ends_at": "2026-09-17T15:00:00Z"
  }'

Over MCP the same operation is the tool affiliate_program_create_contest at https://app.chirply.io/api/mcp, same bearer token, same input.

Create a payout for an affiliate's approved commission — a COMMITMENT TO PAY REAL MONEY to a real person. Claims their approved commissions (oldest first, whole rows only, up to the optional cap) and marks them paid. The money itself moves outside Chirply (PayPal, bank transfer); mark the payout paid once it's sent, or cancel it to release the balance.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.create_payout \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "method": "paypal"
  }'

Over MCP the same operation is the tool affiliate_program_create_payout at https://app.chirply.io/api/mcp, same bearer token, same input.

Create an affiliate program (a campaign) for this account's own products: the offer (percent or flat per sale, one-time or recurring, optionally a multi-level ladder up to 10 levels deep), cookie window, approval and payout settings. THIS COMMITS REAL MONEY: the account owes the stated commission on every referred sale from the moment it exists, its signup URL is publicly live immediately, and commission rates are never backdated — so an over-generous rate cannot be corrected on referrals already captured under it.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.create_program \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Example"
  }'

Over MCP the same operation is the tool affiliate_program_create_program at https://app.chirply.io/api/mcp, same bearer token, same input.

Queues a personalized email to every affiliate matching the chosen campaigns and statuses. This is REAL email to real people, sent from this account's own verified sending address and billed to its own Mailgun/Resend account. Subject and body support {{merge_fields}} and are rendered per affiliate, so each person gets their own referral link, code and balance. Affiliates who unsubscribed are skipped and the account's unsubscribe footer is added; affiliates with no email address are skipped too. The send runs as a background job so it can be paced, watched, paused or resumed, and start_at schedules it for later instead of sending now. Call affiliate_program.preview_email_audience first to see how many people that is.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.email_affiliates \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "subject": "Example",
    "body": "example"
  }'

Over MCP the same operation is the tool affiliate_program_email_affiliates at https://app.chirply.io/api/mcp, same bearer token, same input.

End an active contest NOW and FREEZE the final standings as its winners, with prizes attached by rank — affiliates see the result on their portals immediately. This is permanent: an announced result never changes, even if more sales land later, and the prizes you promised are now owed to real people. Ending before the scheduled close counts only what happened up to this moment.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.end_contest \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "contest_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_end_contest at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one affiliate with everything a manager sees: profile and status, their shareable referral link(s), their private portal URL (a bearer link — anyone holding it sees their dashboard, so share it only with the affiliate themself), and their commission balance.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.get_affiliate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_get_affiliate at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one contest with its full setup (metric, window, prizes) and its standings: LIVE standings computed over the contest window while it's a draft or active, or the FROZEN winners once it has ended. Names here are the affiliates' real names — this is a manager surface; the affiliates' own portals show peers masked.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.get_contest \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "contest_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_get_contest at https://app.chirply.io/api/mcp, same bearer token, same input.

The always-on affiliate leaderboard for a program — top active affiliates ranked by a metric over the last 30 days or all time, ties sharing a rank. Names here are real (this is a manager surface); on the affiliates' own portals every peer appears masked as first name + last initial. Affiliates who chose 'Hide me from the leaderboard' are left off this board too — it's a display surface, unlike contest standings which always count everyone.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.get_leaderboard \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "metric": "customers"
  }'

Over MCP the same operation is the tool affiliate_program_get_leaderboard at https://app.chirply.io/api/mcp, same bearer token, same input.

Check whether this account can pay affiliates automatically, and (optionally) where one affiliate stands: is PayPal connected, is Stripe connected, and for a given affiliate their saved payout method, PayPal email, and Stripe Connect onboarding status (none / onboarding / active / restricted — payouts only flow once it's active). The readiness card on the payouts page walks through the same prerequisites, including the one thing this can't verify from here: Stripe Connect must also be enabled on your own Stripe dashboard.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.get_payout_rails \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_get_payout_rails at https://app.chirply.io/api/mcp, same bearer token, same input.

Fetch one affiliate program with all of its settings — reward terms, tier-2 terms, cookie window, approval switches, hold days, minimum payout — plus its public signup URL.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.get_program \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_get_program at https://app.chirply.io/api/mcp, same bearer token, same input.

The public 'become an affiliate' URL for a program — the link to share anywhere you recruit affiliates. Anyone who opens it can apply to join the program (auto-approved if the program is set that way), so treat it as public.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.get_signup_link \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_get_signup_link at https://app.chirply.io/api/mcp, same bearer token, same input.

List the affiliates recruited into this account's program(s) — name, email, referral code, status, and custom rate — filterable by program and status, searchable by name, email, or code. Portal tokens are never included in lists; open one affiliate to get their portal link.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.list_affiliates \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "status": "pending"
  }'

Over MCP the same operation is the tool affiliate_program_list_affiliates at https://app.chirply.io/api/mcp, same bearer token, same input.

List the commission ledger — one row per tier per referred payment, with amount, status, and when it clears its hold. Pending + approved rows are real money the account owes its affiliates. Filterable by program, affiliate, and status.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.list_commissions \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_list_commissions at https://app.chirply.io/api/mcp, same bearer token, same input.

List this account's affiliate contests — time-boxed competitions ('most new customers this month wins $500') with live standings on every affiliate's portal. Each row includes its status (draft = not visible yet, active = live and counting, ended = winners frozen, canceled = never happened), metric, window, and prizes.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.list_contests \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "status": "draft"
  }'

Over MCP the same operation is the tool affiliate_program_list_contests at https://app.chirply.io/api/mcp, same bearer token, same input.

List payouts to affiliates — amount, method, destination, and status. A pending payout has claimed its commissions but the money hasn't been sent yet. Filterable by affiliate, program, and status.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.list_payouts \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_list_payouts at https://app.chirply.io/api/mcp, same bearer token, same input.

List this account's affiliate programs — the offers it runs (reward terms, cookie window, approval and payout settings) — each with its public signup URL.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.list_programs \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "include_archived": false
  }'

Over MCP the same operation is the tool affiliate_program_list_programs at https://app.chirply.io/api/mcp, same bearer token, same input.

List the people affiliates have referred — leads and customers — with the reward terms snapshot each referral locked in at capture time. Filterable by program, affiliate, and status.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.list_referrals \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_list_referrals at https://app.chirply.io/api/mcp, same bearer token, same input.

Confirm the money actually left — the PayPal send or bank transfer happened. Stamps who processed it and when, and settles the affiliate's balance so those commissions are never queued for payment again. It does not move money itself, which is exactly the risk: marking a payout paid that was never sent quietly writes off what the account still owes a real person, and there is no un-mark.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.mark_payout_paid \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "payout_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_mark_payout_paid at https://app.chirply.io/api/mcp, same bearer token, same input.

Headline numbers for this account's own affiliate program (the program it runs for its products, not Chirply's): affiliate counts by status, clicks, referrals, referred customers, commission totals by status, and the top-earning affiliates. Optionally narrowed to one program or a start date.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.overview \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "since": "2026-09-17T15:00:00Z"
  }'

Over MCP the same operation is the tool affiliate_program_overview at https://app.chirply.io/api/mcp, same bearer token, same input.

Pause an affiliate: new clicks on their links stop earning attribution until they're approved again. Their existing referrals and earned commission are untouched.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.pause_affiliate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_pause_affiliate at https://app.chirply.io/api/mcp, same bearer token, same input.

Counts the affiliates a broadcast would go to, without sending anything: how many match the chosen campaigns and statuses, and how many of those actually have an email address on file. The second number is the real send size, because affiliates with no address are skipped. Also lists the merge fields an affiliate email can fill. Run this before affiliate_program.email_affiliates to see exactly what that call would do.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.preview_email_audience \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP the same operation is the tool affiliate_program_preview_email_audience at https://app.chirply.io/api/mcp, same bearer token, same input.

Record a referred payment by hand and write the commission it earns — REAL MONEY the account then owes its affiliate(s), one ledger row per tier, at the terms snapshot on the referral. Use for sales that happened outside connected Stripe. Supply external_ref to make retries safe: the same reference is never recorded twice.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.record_sale \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "amount_cents": 1
  }'

Over MCP the same operation is the tool affiliate_program_record_sale at https://app.chirply.io/api/mcp, same bearer token, same input.

Refuse a pending or approved commission (fraud, dispute, self-referral) — the affiliate permanently loses this money from their balance. Already-paid commissions can't be rejected.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.reject_commission \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "commission_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_reject_commission at https://app.chirply.io/api/mcp, same bearer token, same input.

Send a pending payout down its rail RIGHT NOW — this moves real money from your own PayPal or Stripe account to the affiliate immediately. The rail is the affiliate's saved payout method unless you override it: 'paypal' sends a PayPal payout from your connected PayPal (settles within minutes), 'stripe' transfers out of your own Stripe balance into the affiliate's Stripe account instantly, and 'manual' just records that you already sent the money yourself. If the provider refuses, the payout is marked failed and the claimed commissions are released back to the affiliate's balance so nothing is silently swallowed.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.send_payout \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "payout_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_send_payout at https://app.chirply.io/api/mcp, same bearer token, same input.

Give one affiliate a personal deal that replaces the campaign's standard terms — their own multi-level commission ladder, and/or their own recurring window. THIS CHANGES WHAT A REAL PERSON EARNS on referrals they capture FROM NOW ON, and never touches the past: every referral already captured keeps the terms it locked in, so a deal set by mistake cannot be reversed for anything captured while it stood. Pass null for a field to clear it back to the campaign's terms (an affiliate with no overrides simply follows the campaign, so raising the campaign later raises them too).

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.set_affiliate_deal \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_set_affiliate_deal at https://app.chirply.io/api/mcp, same bearer token, same input.

Give one affiliate a personal commission percent that replaces the program's percent, or clear it back to the program rate. THIS CHANGES WHAT A REAL PERSON IS PAID. It applies to referrals they capture FROM NOW ON — existing referrals keep the terms they locked in, because rates are never backdated, so neither a raise nor a cut can be undone for anything captured while it stood.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.set_affiliate_rate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "percent": 1
  }'

Over MCP the same operation is the tool affiliate_program_set_affiliate_rate at https://app.chirply.io/api/mcp, same bearer token, same input.

Save how an affiliate gets paid from now on: 'paypal' (automatic PayPal payout to their saved email), 'stripe' (automatic transfer to the Stripe account they set up from their portal), or 'manual' (a human sends the money and marks it paid). THIS DECIDES WHERE REAL MONEY GOES — affiliate_program.send_payout follows whatever is stored here — and it overwrites the previous setting with no record of it. Changes future sends only; payouts already on their way are untouched.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.set_payout_method \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11",
    "method": "paypal"
  }'

Over MCP the same operation is the tool affiliate_program_set_payout_method at https://app.chirply.io/api/mcp, same bearer token, same input.

Take a draft contest live: it appears on every affiliate's portal leaderboard page and the standings start counting over its window. This is OUTWARD-FACING and it PROMISES A PRIZE — every ACTIVE affiliate is entered automatically, including ones who hide themselves from the always-on leaderboard, and they will see the contest and its stated reward. Starting one by accident commits the account to it in front of everybody.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.start_contest \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "contest_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_start_contest at https://app.chirply.io/api/mcp, same bearer token, same input.

Update one affiliate's payout email, private notes, or personal commission rate — mirroring the 'Payout details & notes' editor on their detail page. paypal_email is where affiliate_program.create_payout defaults their payout to when no destination is given, so a wrong address bounces the payment or pays a stranger; confirm it with the affiliate before saving. notes are private and never shown to the affiliate. override_reward_percent does the same job as affiliate_program.set_affiliate_rate (kept working for compatibility) — it applies to referrals they capture FROM NOW ON, never to ones already snapshot. Omitted fields are left alone; pass null to clear paypal_email, notes, or override_reward_percent back to unset.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.update_affiliate \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "affiliate_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_update_affiliate at https://app.chirply.io/api/mcp, same bearer token, same input.

Update a draft or active contest's setup — name, description, metric, window, or prizes. Omitted fields are left alone. An ended or canceled contest can't be edited: a result that has been announced is history.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.update_contest \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "contest_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_update_contest at https://app.chirply.io/api/mcp, same bearer token, same input.

Update a program's settings — name, terms, reward (including the multi-level ladder), cookie window, approval switches, hold days, minimum payout, destination URL, or pause/resume it. Omitted fields are left alone. THIS CHANGES WHAT THE WORKSPACE OWES on every sale from now on, and the public signup and terms pages change with it. Rate changes apply to NEW referrals only — every existing referral keeps the terms it was captured under, so a rate raised by mistake cannot be walked back on referrals captured in the meantime.

Marked confirm: this operation is irreversible, reaches real people, or spends money. Holding a credential is itself the confirmation for API and MCP callers — call it only when you mean it. The in-app assistant refuses to run it without a human approving first.

Parameters

Example

curl -X POST https://app.chirply.io/api/v1/actions/affiliate_program.update_program \
  -H "Authorization: Bearer chp_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "program_id": "2f6a1c1e-6c3b-4c62-9f6e-8a2d4b7c9e11"
  }'

Over MCP the same operation is the tool affiliate_program_update_program at https://app.chirply.io/api/mcp, same bearer token, same input.