Overview
Because these credentials are managed directly within each third-party platform, Triple Whale cannot revoke them on your behalf. Please follow the instructions below for each applicable integration connected to your Triple Whale account.
Important: You only need to complete the steps for integrations you currently have connected to Triple Whale.
Integration Instructions
Use the links below to navigate directly to the instructions for your integration.
OpenAI
Step 1: Generate a New ChatGPT Ads API Key
Log in to ChatGPT Ads Manager.
Select the affected advertising account.
Navigate to Settings → General → API Keys.
Click Create New Key.
Enter a recognizable name for the key, such as "Triple Whale".
Click Create.
Copy or download your new API key and store it securely.
Important: Your API key is displayed only once. Make sure to save it before closing the dialog.
You do not need to manually revoke the affected key, as OpenAI has already invalidated it.
Step 2: Reconnect ChatGPT Ads in Triple Whale
Log in to Triple Whale.
Navigate to Data → Integrations.
Find your existing ChatGPT Ads integration.
Disconnect the existing integration.
Locate ChatGPT Ads again and click Connect.
Paste your newly generated ChatGPT Ads API key.
Click Save.
For additional guidance, see our ChatGPT Ads Integration Guide.
Outbrain
First, log into Outbrain, and open your Account Settings: https://my.outbrain.com/login
Then update your password: https://my.outbrain.com/user-settings
Updating your password will delete all of your old integrations.
Next, In the Triple Whale app, select Data -> Integrations, find the Outbrain tile, and click connect. Enter your user name and password to reconnect.
Okendo
Step 1: Revoke and Replace Your Okendo API Key
Log in to your Okendo Admin dashboard.
Navigate to Settings → Integrations.
Locate the Okendo section and open its API settings.
Locate your existing Merchant REST API Key.
If a revoke, delete, or regenerate option is available, use it to invalidate your existing key and generate a replacement.
If you cannot revoke or regenerate the key, contact Okendo Support and request that your existing Merchant REST API key be invalidated and replaced.
Copy your newly generated API key and keep it secure.
Important: Your existing API key must be invalidated. Simply copying the current key or reconnecting Triple Whale does not revoke it.
Step 2: Reconnect Okendo in Triple Whale
Log in to Triple Whale.
Navigate to Data → Integrations.
Find your Okendo integration.
Click Disconnect next to the existing connection.
Locate Okendo in the integrations list and click Connect.
Enter your newly generated Okendo API key and any other required account information.
Save the connection.
For additional guidance, see our Okendo Integration Guide.
Podscribe
Log into your podscribe account. From the main screen, open the Account and Settings option: app.podscribe.com
From here, simply select API, and click Regenerate: app.podscribe.com/settings/
Next, click Copy. Then navigate to the Triple Whale app, go to Data -> Integrations, and find the Podscribe tile. Click connect, and paste in the API Key.
Rokt
Triple Whale connects to Rokt with an App ID and App Secret. To revoke them, remove them in Rokt, generate new ones, then reconnect Rokt in Triple Whale.
You need access to Rokt's One Platform. If you don't have it, ask your Rokt account manager to add you as a managed user.
Step 1: Remove the old credentials in Rokt
Sign in to One Platform at my.rokt.com.
Click your account icon at the bottom left, then select Profile Settings.
Remove the API credentials you created for Triple Whale. If there is no option to remove them, ask your Rokt account manager to revoke them.
Step 2: Generate new credentials
In Profile Settings, scroll to Generate Personal API Credentials.
Enter an app name (for example, Triple Whale) and click Generate.
Copy the App ID and App Secret right away. You can't view the App Secret again after this step.
Step 3: Reconnect in Triple Whale
In Triple Whale, go to Data > Integrations (in the left sidebar, click Data, then Integrations).
Search for Rokt and click Manage on its card. Once the old key stops working, the card may show Reconnection required.
In the Rokt window, click Edit auth details.
In the Edit Rokt auth details window, enter the new App ID and App Secret, then click Save.
Notes
Prefer to start fresh? In the Rokt window, click Disconnect instead. Then click Connect on the Rokt card and enter the new App ID and App Secret.
Personal credentials. Rokt API credentials belong to the user who created them, and can only pull data from accounts that user can access.
Event API. The same credentials also work for Rokt's Event API. If you use them there, update it with the new credentials too.
For setup details, see the Rokt Integration article.
StackAdapt
Step 1: Revoke and Replace Your StackAdapt API Key
Contact your StackAdapt Account Manager or Customer Success Manager.
Request that they revoke your existing GraphQL (GQL) API key and generate a new one.
Explain that you need a replacement GQL API key for your Triple Whale integration.
Once StackAdapt provides the new key, copy it and store it securely.
If you don't have a dedicated StackAdapt account manager, contact StackAdapt Support.
Important: Your existing API key must be revoked to ensure it can no longer be used. Simply generating a new key does not necessarily invalidate the previous one.
Step 2: Reconnect StackAdapt in Triple Whale
Log in to Triple Whale.
Navigate to Settings → Integrations.
Find your existing StackAdapt integration.
Disconnect the existing integration.
Locate StackAdapt again and click Connect.
Enter your newly generated StackAdapt GQL API key.
Save the connection.
For additional guidance, see our StackAdapt Integration Guide.
Affiliates
Awin
Log into the Awin App, select the user menu, and select API Credentials
Enter your password, and
select Revoke my Auth Token. The password is the same as you use to log into Awin.
Direct Link https://ui.awin.com/awin-api
Refresh the page, enter your password again, and then click Show my API Token:
In the Triple Whale app, select Data -> Integrations, find the Awin tile, and click connect:
This is where you will paste your refreshed OAuth2 Token
GRIN
Integrations are managed under Profile menu → Settings → Integrations. Each connected app has its own Settings link, and you disconnect it from there. It takes about four clicks.
Steps
Step 1 — Open your profile menu
Log in to GRIN at app.grin.co. On the Home page, click your profile avatar (the grey circle) in the top-right corner of the navigation bar.
Step 2 — Click Settings
A panel slides out from the right. Under Privacy & Settings, click Settings.
Step 3 — Go to Integrations
The Settings page opens on your Profile. In the left sidebar, under Your Integrations, click Integrations.
Step 4 — Open the integration's Settings and disconnect
You now see every connected app (for example CreatorCommerce, GRIN API Integration, Instagram, Klaviyo). Find the integration you want to remove, then click the ⚙ Settings link on its connected row (for example next to exampleshop.myshopify.com or @exampleshop). In the settings that open, click Disconnect and confirm.
Notes
The integration stays listed after you disconnect. Its row changes to "Integration available. Click “Connect” to get started."
To reconnect, click Connect on the same card.
How to Reconnect GRIN to Triple Whale
Triple Whale reads your GRIN data with a GRIN API key. To reconnect, turn the GRIN API Integration back on in GRIN, copy its API key, and paste the key into Triple Whale.
Step 1 — Reconnect the GRIN API Integration in GRIN
In GRIN, go to Profile menu → Settings → Integrations (Steps 1–3 above). Find GRIN API Integration and click Connect on its card.
Step 2 — Copy your API key
Click ⚙ Settings on the GRIN API Integration row and copy the API key shown there. Use the key shown now, not one you saved before disconnecting, because the old key may no longer work.
Step 3 — Open GRIN in Triple Whale
Log in to Triple Whale at app.triplewhale.com and select your store. Open Integrations, search for GRIN, and click Connect.
Step 4 — Paste the API key
Paste the key from Step 2 into the API Key field and save. Triple Whale checks the key against GRIN before it continues.
Step 5 — Choose your brand
Triple Whale lists the GRIN brands that the key can see. Select your brand to finish connecting.
Notes
Data can take up to 48 hours to appear after the first connection, because GRIN enables API access manually on its side. You don't need to do anything while you wait.
History is backfilled automatically. After reconnecting, Triple Whale pulls past GRIN conversions, so the gap from while you were disconnected fills in.
If the key is rejected, check that the GRIN API Integration is connected in GRIN (Step 1) and that you copied the full key.
Impact.com
To revoke your API Key, navigate to your Account, select settings, and go to the technical section: Direct Link https://app.impact.com/secure/advertiser/api/fr/api-access-tokens-ui.ihtml
Then, in your Triple Whale integration, select the … menu, and delete:
Next, create a new API Token;
Give the token a name:
Enter a user name and email who will be your contact for the impact app, this has no bearing on Triple Whale.
Give the token GET (read) access to these scopes:
Accounts
Actions
Ads
Clicks
Conversions
Jobs Management
Partner Groups
Partners
Reports
PromoCodes
Click create in the corner
Now click on on the newly created tile:
In here you will find your Account ID and Token.
In the Triple Whale app, select Data -> Integrations, find the impact tile, and click connect:
This is where you will paste the ID and Token:
Partnerize
Triple Whale connects to Partnerize with your User application key and User API key. To revoke access, generate new API keys in Partnerize, then reconnect Partnerize in Triple Whale with the new keys.
Step 1: Generate new API keys in Partnerize
Log in to Partnerize at console.partnerize.com.
Click your account name at the top left. Under Settings & preferences, click Settings.
On the Your account page, in the Account tab, click Generate new API keys.
Step 2: Copy both keys
On the same page, click the eye icon next to User application key and User API key to show each key, then copy both.
Step 3: Reconnect in Triple Whale
In Triple Whale, go to Data > Integrations (in the left sidebar, click Data, then Integrations).
Search for Partnerize and click Manage on its card. Once the old key stops working, the card may show Reconnection required.
In the Partnerize window, click Edit auth details.
In the Edit Partnerize auth details window, enter the new User application key and User API key, then click Save.
Notes
Prefer to start fresh? In the Partnerize window, click Disconnect instead. Then click Connect on the Partnerize card and enter both keys.
Use both keys together. The two keys work as a pair. Copy both again after generating new keys, so they match.
Other tools. Other tools that use your Partnerize API keys need the new keys too.
New interface. These steps show the classic Partnerize interface. If you have turned on New Interface at the top right, the menus may look different.
For setup details, see the Partnerize Integration article.
Pepperjam
Triple Whale connects to Pepperjam (Ascend by Partnerize) with an API Key, its Version, and your PID. To revoke the key, generate a new one in Ascend, which replaces the old key, then reconnect Pepperjam in Triple Whale.
Only primary users on the Ascend account can view and manage API keys.
Step 1: Generate a new key in Ascend
Log in to your Ascend (Pepperjam) account as the primary user.
In the left menu, click Resources, then API Keys.
Click Generate New Key. This replaces your old key.
Copy the new API Key and its Version, shown in the Version column.
Note your PID, shown at the top right next to your account name.
Step 2: Reconnect in Triple Whale
In Triple Whale, go to Data > Integrations (in the left sidebar, click Data, then Integrations).
Search for Pepperjam and click Manage on its card. Once the old key stops working, the card may show Reconnection required.
In the Pepperjam window, click Edit auth details.
In the Edit Pepperjam auth details window, enter the Version, new API Key, and PID again (all three are needed, even if only the key changed), then click Save.
Notes
Prefer to start fresh? In the Pepperjam window, click Disconnect instead. Then click Connect on the Pepperjam card and enter the Version, API Key, and PID.
Older menus. Some accounts show this page as Developer Kit > API Keys.
Other tools. If you used the old key in other tools, update them with the new key too.
For setup details, see the Pepperjam Integration article.
Rakuten
Log into your account, https://rakutenadvertising.com/ and click on login -> Affiliate Advertiser.
After logging in, go to Reports -> Reporting
Click on Update API Key
You will get a new Token for the same report. To find the API key, Click the arrow next to View Report, click on Get API. Everything in the long string after token= is the API key.
Go to the triple whale app, navigate to Data -> Integrations. Find the Rakuten card, select Manage, and select Edit Auth details. In there is a field for MID and Token. Paste the new API in the token field of the Rakuten reconnect.
If you need to refill your MID, it is found in the Rakuten App, in the top right corner next to your store name.
Superfiliate
Log into your account, https://auth.superfiliate.com/sign-in and navigate to Settings, then select Developers:
Select Revoke on the Triple Whale integration. Next, Click Generate new API Key. Check:
Campaigns.read
Conversions.read
Customers.read
Reports.read
Reports.write
Give the key an easy to understand name, like Triple Whale Integration,
After clicking generate keys, you will be shown the API Keys once. Make sure to save the values before closing the pop up.
Go to the Triple Whale App, navigate to data -> Integrations, open the superfiliate card, and paste in the Client ID and Secret.
Subscriptions
Loop Subscriptions
To revoke the API token you gave Triple Whale, remove it in Loop, create a new one, then reconnect Loop in Triple Whale.
Step 1: Remove the old token in Loop
In Loop admin, go to Settings > API tokens & webhooks.
Find the token you created for Triple Whale and click Remove, then confirm.
Once removed, the token can't be recovered, and any tool still using it stops working.
Step 2: Create a new token
On the same page, click Generate New Token.
Enter a name (for example, Triple Whale). Make sure Subscription Contracts and Orders are ticked and set to Read only, then click Generate.
Click Show token and copy it.
Step 3: Reconnect in Triple Whale
In Triple Whale, go to Data > Integrations (in the left sidebar, click Data, then Integrations).
Search for Loop Subscriptions and click Manage on its card. Once the old key stops working, the card may show Reconnection required.
In the Loop Subscriptions window, click Edit auth details.
In the Edit Loop Subscriptions auth details window, enter the new token in the API Key field, then click Save.
Notes
Double-check the token. Triple Whale does not test a Loop token when you save it, so a mistyped token is not flagged right away.
Prefer to start fresh? In the Loop Subscriptions window, click Disconnect instead. Then click Connect on the Loop Subscriptions card and enter the new token.
Other tools. If you used the old token in other tools, update them with a new token too.
Editing is not enough. Changing a token's name or scopes keeps the same token. To get a new one, use Generate New Token.
Order tagging. Keep order tagging on in Loop, with the matching tags set in Triple Whale's Subscription Order Tags settings. See the Loop Subscriptions Integration article.
Shipping
ShipHero
Log in to ShipHero and go to My Account > Developer Users. The direct link is app.shiphero.com/dashboard/users .
Find the developer user that was created for Triple Whale. You can identify it by the name and email entered when it was set up.
In the Actions column on that row, click De-activate.
Confirm. Both the API Access Token and the Refresh Token stop working right away.
A deactivated developer user cannot be reactivated. That is expected. The next step creates a replacement.
On the same Developer Users page, click:
Add Third-Party Developer at the top.
Enter a First Name, Last Name and Email. The email must not be used by any other ShipHero user.
Click Add Developer.
Copy the API Access Token and the Refresh Token that appear.
ShipHero shows the Access Token only once, so copy it before leaving the page.
Navigate to Triple Whale, Data -> Integrations. Find the ShipHero tile, click Edit auth details, and paste in the refresh token.
ShipStation
Log into your ship station account https://ship4.shipstation.com/home
Click on the gear icon to open your account settings:
Open API Settings:
From API settings, delete the existing token
Confirm and delete the key.
Generate a new V1 API key
Next select any timeframe you would like, you’ll be sent a code to your email to generate the code.
On the next screen you will have your only chance to save your API Key and Secret, save them, or paste them right into Triple Whale, but when you click done you will not be able to recover them.
In the Triple Whale app, select Data -> Integrations, find the ShipStation tile, and click connect. In this screen you will be able to paste your API key and Secret.
Vibe
Triple Whale connects to Vibe with an API key. To revoke it, create a new key and revoke the old one in Vibe, then update Triple Whale with the new key right away.
Vibe API keys stop working in January 2027, as Vibe notes on its API keys page.
Step 1: Replace the key in Vibe
Log in to Vibe at vibe.co/sign-in. Click your account name at the top right, then Account settings.
In the left menu, under Developer tool, click API keys.
Click Create API key.
Name the key (for example, Triple Whale), then copy the new key and keep it somewhere safe.
Find the old key you created for Triple Whale. In the Actions column, click the three-dot menu, then Revoke.
Step 2: Update the key in Triple Whale
In Triple Whale, go to Data > Integrations (in the left sidebar, click Data, then Integrations).
Search for Vibe and click Manage on its card. If the old key has already stopped working, the card shows Reconnection required.
In the Vibe window, click Edit auth details.
In the Edit Vibe auth details window, paste the new key into the API Key field, then click Save.
Check that Settings > Clicks & Deterministic Views > Vibe is turned on.
Notes
Prefer to start fresh? In the Vibe window, click Disconnect instead. Then click Connect on the Vibe card and enter the new key.
Update Triple Whale right away. Once you revoke the old key, Triple Whale stops receiving Vibe data until you save the new key, and Vibe click and view data is not filled in later.
Other tools. If you used the old key in other tools, update them with the new key too.
For setup details, see the Vibe.co Integration article.
Stay AI
Credentials: API Key
Revocation Instructions
To revoke the API token you gave Triple Whale, delete it in Stay AI, create a new one, then reconnect Stay AI in Triple Whale.
Step 1: Replace the key in Stay AI
In your Stay AI Merchant Portal, go to Account > API Tokens in the left menu.
Next to the key you created for Triple Whale, click Delete. Then click New API Key.
Fill in Name (for example, Triple Whale), Description, and Email, then click OK.
Click the copy icon next to the new key to copy it.
Step 2: Reconnect in Triple Whale
In Triple Whale, go to Data > Integrations (in the left sidebar, click Data, then Integrations).
Search for Stay AI and click Manage on its card. Once the old key stops working, the card may show Reconnection required.
In the Stay AI window, click Edit auth details.
In the Edit Stay AI auth details window, enter the new key in the API Key field, then click Save.
Notes
Prefer to start fresh? In the Stay AI window, click Disconnect instead. Then click Connect on the Stay AI card and enter the new key.
Other tools. If you used the old token in other tools, update them with a new token too.
For setup details, see the Stay AI Integration article.
Data Exports
Snowflake
Credentials: Account ID, Warehouse, Database, Schema, Username, Role, and Password / PAT / Private Key



































































