Documentation changelog
Track the public documentation’s verified coverage.
On this page
What you need
No sign-in. Each article displays its reviewed date; the API transport version remains part of the actual HTTP contract.
Steps
- Read the relevant guide’s reviewed date and current product behavior.
- Use the public API reference and MCP catalog for supported operations/tools.
- Report a mismatch with the article URL and reproducible product result, without private credentials.
Expected result
Public documentation covering current source-backed workflows and interfaces rather than an unimplemented roadmap.
7 October 2026
Initial complete public documentation: onboarding and data-source setup; analytics, customer segments and Flows; affiliate programs, referral/financial review and manual payment confirmations; developer identification, browser/backend events, signed install claims and webhooks; all 15 public affiliate REST operations and all 25 MCP tools; account/billing, troubleshooting and machine-readable access.
The publication does not add automated transfers or assume exact merchant activation events. Those instructions describe the current HeyCrust product.
Troubleshooting
If a provider UI changes, use the linked official provider instructions and report the mismatch. A schema example validates shape; business eligibility and real external journeys still require their own verification.