Connect impact.com
impact.com authenticates with an Account SID (your API username) and an Auth Token, created together inside your account settings. ChaffChing reads your actions/commissions only — your keys stay in your device Keychain.
- Account SID
- Auth Token
Heads up — legacy tokens are being phased out. The Account SID + Auth Token pair is impact.com's legacy credential. From July 1, 2026, impact.com stops letting you copy legacy Read/Write and Read-Only tokens. Existing connections keep working, but if you're setting up after that date and can't reveal a token, generate one before the cutoff or contact impact.com about scoped tokens.
Before you start
- You need an active, approved impact.com partner account you can sign in to.
- If you manage several brands, each account has its own SID — make sure you copy the credentials for the account whose sales you want in ChaffChing.
Step 1 — Open the API settings
- Sign in at app.impact.com.
- Open your profile menu (top right) → Settings.
- In the Technical column, choose API.
Step 2 — Copy your Account SID & Auth Token
- On the API page, select Enable Legacy Tokens if the SID/Token aren't already shown (new accounts hide them by default).
- Open the API Credentials card. You'll see the Account SID plus the Auth Token for the Read/Write and Read-Only tokens.
- Copy the Account SID and an Auth Token (Read-Only is enough for ChaffChing) into the matching fields.
The Account SID is the same value impact.com uses in API paths like /Mediapartners/{AccountSID}/. If you ever need a modern scoped token instead, the same API page has Create Access Token in the upper right.
Troubleshooting
I can't see an Account SID or Auth Token
Click Enable Legacy Tokens on the API page. If the option is gone, your account is past the legacy cutoff — reach out to impact.com support about API access.
"Could not authenticate"
You likely copied the SID/Token from the wrong account, or the Auth Token was reset. Re-open Settings → Technical → API for the correct account and copy both values again.