Networks
Network guides
Five networks, one schema, your own credentials on every call. Each guide covers where to find the credentials, what syncs, and the network's quirks.
The BYOC posture
AffiliateOS acts strictly as a processor of your own network data. Every request uses your credentials against official APIs. There is no cross-user pooling, no scraping, and no resale of network data. Credentials are sealed with libsodium before storage and decrypted only in worker memory at call time; they never appear in logs or webhook payloads.
Capability matrix
| Network | Programs | Transactions | Payments | Product search | Sub-ID param |
|---|---|---|---|---|---|
| Awin | clickref | ||||
| Impact | subId1 | ||||
| CJ (Commission Junction) | sid | ||||
| Rakuten Advertising | u1 | ||||
| Amazon Associates | ascsubtag |
Sync cadence
| Data | Frequency |
|---|---|
| Programs | every 12 hours, plus on demand |
| Transactions | hourly |
| Payments | daily |
You can force a sync from the dashboard or POST /v1/accounts/:id/sync, limited to once per five minutes per account. Programs alone are the cheap, high-frequency case, so POST /v1/accounts/:id/sync?kinds=programs (and the refresh_programs MCP tool) is limited to once per minute instead — call it right after joining a program rather than waiting for the next scheduled pass. A program search that comes back empty starts that refresh on its own and tells you when to retry. Each network’s own rate limits are enforced with per-account token buckets, and 429 responses honor Retry-After.