Coming soon
External API Roadmap
Public developer API docs are planned after the core affiliate, referral, and fleet add-on contracts settle. Today, ReferCommander uses same-origin app routes, internal service contracts, adapter paths, and exports. We are not offering a stable external API yet.
Hosted Referral Intake
Programs can use hosted affiliate, partner, or fleet intake while ReferCommander keeps reward proof inside the app.
Adapter Paths
Frappe CRM and Novu run as internal adapters; they do not replace app-owned reward or payout truth.
Exports
CSV and dashboard exports remain the low-risk option for current creator, affiliate, and operator workflows.
What needs to be true before public API docs
- Versioned external contracts for programs, referrers, referrals, candidates, rewards, and events
- Scoped API keys or service accounts with workspace-level permissions
- Rate limits, audit logs, and replay-safe event handling for partner integrations
- A sandbox story, examples, and support process that match the real product shape
Current status
Planned after the affiliate, operator, and referrer workflows stabilize.
Partner pilots should use the contact flow so access can be scoped manually.