Routy

Account integration: sign-in rejected

The affiliate program refused the credentials Routy has saved for this account, so we could not collect your stats.

What it means

Routy signs in to the program with the username and password, API key, or client ID and secret you saved on the account. The program answered that they are wrong. Nothing more is collected for this account until the credentials work again, and the account's runs show as Blocked.

The issue names the account, the program and the username we tried. The message after "Account integration failed:" is the program's own reason, worded however the program words it.

Why it happens

  • You changed your password at the program and the old one is still saved in Routy.
  • The program replaced or revoked your API key, or you generated a new one there.
  • The client ID or client secret is wrong or was reissued.
  • Your account at the program is locked, blocked or not yet activated. Some programs answer "Your account is blocked" or "not activated" in place of a sign-in error.
  • The value was pasted with a space at the start or end.

What you can do

  1. Sign in to the program's own site with the same details. If that fails too, reset your password or get a new API key there first.
  2. In Routy, open Accounts, click the account, click Edit, and go to the Integration step.
  3. Click the pencil next to the credential that changed and enter the new value.
  4. Click Test Integration. When it passes, click Save. Saving starts a run straight away and collects back to the start of the month three months ago, so the gap fills in.
  5. If you can sign in to the program yourself but the test still fails, ask your affiliate manager at the program whether API or reporting access is switched on for your account.

See Your account's integration and Adding an affiliate account.

When it clears

It closes by itself on the account's next run that completes, which is usually the one your Save starts. If no run is rejected for 3 days, it also closes on its own. An account on a slower tier may not run within those 3 days, so the issue can close and come back on its next run if the credentials are still wrong.