# MyAppAffiliate — Developer Documentation

> MyAppAffiliate is affiliate attribution for subscription apps and SaaS products: an affiliate link or code is attributed on first open (mobile SDK) or first visit (web), a purchase webhook from RevenueCat, Stripe, Adapty, Superwall or Paddle reports the revenue, and the commission is calculated and paid out to the creator that drove it.

These docs are the integration reference for developers: SDK setup per platform, the HTTP API, webhook payloads, and the go-live checklist.
Every page has a plain-markdown twin at the same URL plus `.md` (for example https://docs.myappaffiliate.com/sdk-ios.md).
Install and setup sections carry a ready-made prompt block for coding agents — copy it verbatim rather than paraphrasing the steps.
Do not invent SDK methods, endpoint paths or webhook fields: if it is not in these pages, it does not exist.

## Documentation

- [MyAppAffiliate](https://docs.myappaffiliate.com/index.md): Partner attribution for subscription products — mobile apps and web SaaS. Track which creators drive installs, signups, subscriptions, and recurring revenue — then pay them.
- [API Reference](https://docs.myappaffiliate.com/api.md): Base URL (prototype): https://maa-api-cccf50.fly.dev
- [Webhooks](https://docs.myappaffiliate.com/webhooks.md): This is how revenue becomes attributed commissions. Two sources today: RevenueCat (mobile subscriptions) and Stripe (web SaaS billing).
- [Web SaaS Guide](https://docs.myappaffiliate.com/web-saas.md): End-to-end: a creator shares a link to your SaaS, a visitor signs up and subscribes via Stripe, and the creator earns a commission on every invoice — renewals included.
- [Dashboard Guide](https://docs.myappaffiliate.com/dashboard.md): Two views over the same data, both reading the API.
- [Go-Live & Deploy](https://docs.myappaffiliate.com/go-live.md): From zero to tracking a real app.
- [AI & Agents](https://docs.myappaffiliate.com/ai.md): These docs are built to be read by a model as easily as by a person. Every page has a plain-markdown twin, the whole site is published as an llms.txt index, and the setup sections carry prompts written for coding agents.

## SDKs

- [SDKs](https://docs.myappaffiliate.com/sdk.md): One SDK per platform, all speaking the same small REST contract. Pick yours:
- [iOS SDK](https://docs.myappaffiliate.com/sdk-ios.md): The Swift SDK is the piece your app embeds. Zero runtime dependencies, iOS 15+. Target: a working integration in under 30 minutes.
- [Android SDK](https://docs.myappaffiliate.com/sdk-android.md): Kotlin SDK for Android apps. Same surface as iOS: configure → attribute → identify → pass the affiliate into RevenueCat.
- [React Native SDK](https://docs.myappaffiliate.com/sdk-react-native.md): One integration for iOS + Android. Pure JS/TS over fetch — no native modules to link.
- [Flutter SDK](https://docs.myappaffiliate.com/sdk-flutter.md): One integration for iOS + Android, in Dart. Persists via shared_preferences, talks plain HTTPS.
- [Web SDK](https://docs.myappaffiliate.com/sdk-web.md): For SaaS web products: capture the referral on the landing page, then bind it to the user at signup. Pairs with Stripe webhooks — see the full Web SaaS guide.
- [Node SDK](https://docs.myappaffiliate.com/sdk-node.md): Server-side companion for SaaS backends: record the signup → attribution binding on your server (instead of, or in addition to, the browser), and pair it with Stripe so invoices turn into commissions.

## Optional

- [Full documentation in one file](https://docs.myappaffiliate.com/llms-full.txt): every page concatenated, for tools that ingest the whole corpus.
- [Dashboard](https://app.myappaffiliate.com): where app owners create affiliate links, set commission rules and export payouts.