The Developer Portal is where you register an OAuth app that other Triple Whale merchants can connect. After Triple Whale approves the app, merchants grant it on a consent screen that shows your name, logo, and the permissions you requested. Your app then calls the Triple Whale API on their behalf.
An API key is a different path. Create a key in the Triple Whale app when the integration is only for your own shop. See API Keys vs OAuth Apps.
Which Developer Docs Do You Need?
| If you are... | Go to |
|---|---|
| Working on your own shop: sending data in, pulling data out, or creating a key in the Triple Whale app | Triple Whale API |
| Building a product that many merchants connect, with your name and logo on their consent screen | Developer Portal (this section) |
| Adding tracking to an iOS, Android, or React Native app | Triple Pixel Mobile SDK |
| Having Triple Whale push data into your warehouse on a schedule | Data Warehouse Export |
What You Can Do
- Create a developer account. The same email and password you use on app.triplewhale.com work here.
- Submit an app for review. Approval creates the app's
client_id. - Generate a client secret. Triple Whale does not create the secret for you, and it is shown once.
- Send merchants through the OAuth flow, or try it in the Playground first.
- Call the API with the access token. Granted shops is the quickest check that a token works.
Environments
Accounts, apps, and credentials are separate per environment. An app registered on staging does not exist in production.
| Environment | Portal | API |
|---|---|---|
| Production | developers.triplewhale.com | api.triplewhale.com |
| Staging | staging.developers.triplewhale.com | staging.api.triplewhale.com |