Skip to main content

​
Affiliate and Partner APIs

Linquid affiliate architecture has two API surfaces:
  • owner/workspace surface (/affiliate/*)
  • partner-auth surface (/partner/*, marketplace, invite accept)

​
Feature gate

Owner /affiliate/* routes are gated by affiliate-program entitlement.

​
Program owner modules (/affiliate/*)

  • programs and rewards
  • partners and enrollments
  • groups and default links
  • commissions and payouts
  • fraud, analytics, customers, messages
  • bounties, discounts, referrals, invoices
  • invites and activity logs
  • automation rules
Representative endpoints:
  • GET /affiliate/programs
  • GET /affiliate/partners
  • GET /affiliate/enrollments
  • GET /affiliate/commissions
  • GET /affiliate/payouts
  • GET /affiliate/fraud/summary

​
Permission families

  • affiliates:read / affiliates:manage
  • payouts:read / payouts:process
  • fraud:read / fraud:write

​
Marketplace and public invite acceptance

  • GET /affiliate/marketplace/programs
  • POST /affiliate/marketplace/programs/:slug/apply
  • POST /invites/:token/accept
Notes:
  • Marketplace discovery/apply flows use partner context rules.
  • Invite acceptance is token-based and supports rate limiting and expiry handling.

​
Partner portal API (/partner/*)

Auth and account:
  • /partner/auth/*
  • /partner/csrf-token
  • /partner/settings
Operational:
  • /partner/dashboard
  • /partner/earnings
  • /partner/payouts
  • /partner/programs/*
  • /partner/messages
  • /partner/invitations
  • /partner/bounties/*
  • /partner/connect/*
Representative partner analytics endpoints:
  • GET /partner/analytics/earnings-timeseries
  • GET /partner/analytics/funnel
  • GET /partner/analytics/link-performance
  • GET /partner/analytics/activity

​
Money flows covered

  • commission creation/approval/cancel/refund/clawback
  • payout processing (including Stripe/PayPal paths)
  • invoice and payout history

​
Authorization notes

  • Owner APIs require workspace auth and affiliate feature entitlement.
  • Marketplace and partner APIs require partner session auth.
  • Sensitive actions are role-gated (affiliates:*, payouts:*, fraud:*).

​
Typical failures

  • 403 missing affiliate/payout/fraud permissions
  • 404 partner/program/enrollment/commission/payout not found
  • invite token errors (invalid, expired, already processed)
  • payout provider connectivity and compliance failures
Related docs:
  • /api-reference/affiliate/program-owner-modules
  • /api-reference/affiliate/partner-portal-api
  • /api-reference/affiliate/public-marketplace-and-invites
  • /user-guides/manual/ecosystem/affiliate-program-operations-reference
  • /user-guides/manual/ecosystem/partner-portal-reference
  • /user-guides/manual/ecosystem/affiliate-program-operations-reference
  • /user-guides/manual/ecosystem/affiliates-and-partners