Connect
impact.com: connect a publisher or brand account with an API token
TL;DR
impact.com connects with two values from an API token — the Account SID and the Auth Token — and the account kind: publisher (partner) or advertiser (brand). The token's scopes decide what the agent can read and change; the connection records which areas answer.
Required fields
| Field | Where it comes from | Notes |
|---|---|---|
| Account SID | impact.com → Settings → Technical → API → your token → API Credentials | Starts with IR. It names the account; every call is bound to it. |
| Auth Token | The same page | Stored encrypted, never shown again. Create a new token in impact.com to replace it. |
| Account kind | Your impact.com account | Publisher (partner) or Advertiser (brand). A token connected as the wrong kind is told so. |
Connect step by step
- 1In impact.com open Settings → Technical → API and create an API token. Choose read-only for reports only, or read/write with the scopes the agent may use.
- 2Open the token's API Credentials and copy the Account SID and Auth Token.
- 3In Agent Planners open Integrations → impact.com, choose Publisher (partner) or Advertiser (brand), paste both values and press Connect.
- 4Agent Planners checks them with impact.com, then reads one small page from each area (programs, actions, reports, invoices …) and records which ones the token can reach.
Several tokens for the same account can be connected — each is kept as its own sign-in.
Publisher and advertiser: what each kind reaches
| Publisher (partner) | Advertiser (brand) | |
|---|---|---|
| Tools that answer | 26 reads and 6 writes | 25 reads and 12 writes |
| Reads | Programs you joined, actions, action updates and inquiries, reports and performance, exports, invoices, contracts, promo codes, deals, ads, catalogs and product search, media properties | Programs, actions (one program at a time), partners, reports, exports, invoices, contracts, promo codes, deals, ads, catalogs |
| Changes | Tracking links, media properties; action inquiries (always a person) | Action updates and reversals, inquiry decisions, promo codes, deals, contracts, partner values, partner tracking links — every one waits for a person |
A tool for the other kind answers with a sentence and makes no call.
Limits we measured on a publisher account
- Company information and the jobs list answered 403 even on a token with every publisher scope; a single export job and its download answered. The agent says what is unavailable and reads the currency from invoices.
- Actions: 45 days per request. A longer window (up to a year) is read in 45-day pieces.
- Tracking links have no delete in impact.com, so they are created only when you ask.
- impact.com's own limits: 250 report runs an hour and 100 report exports a day for a partner account.
What needs a person, and what is refused
- By default every change waits for your approval card; auto-approve and an API key that applies changes at once are opt-in.
- Always a person, on every lane: every advertiser change, deleting a media property, an action inquiry, gateway writes to actions, contracts, promo codes or deals, and any delete.
- Refused: credentials and tokens, company information, users, invoices, tax, withdrawal and payment paths, creating partner accounts, and any path naming another account.
Frequently asked questions
- Read-only or read/write token?
- Read-only if you only want reporting — nothing can change. Read/write lets the agent create tracking links and media properties, and on a brand account propose changes that always wait for a person.
- Was the advertiser side tested on a live account?
- No. Publisher connections were tested on a live account; advertiser connections were tested against simulated impact.com answers, and no brand account was changed.
- Can I connect both a publisher and a brand account?
- Yes — each is its own connection with its own token, and a task can use either.