Triple Whale · Authentication Profile
Triple Whale Authentication
Authentication
Triple Whale secures its APIs with apiKey and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).
E-CommerceAnalyticsAttributionShopifyPixel TrackingROASDirect to ConsumerMarketing
Methods: apiKey, oauth2
Schemes: 2
OAuth flows: authorizationCode
API key in: header
Security Schemes
apiKeyAuth apiKey
· in: header (x-api-key)
mcpOAuth oauth2
· flows: authorizationCode
Source
Authentication Profile
generated: '2026-08-13'
method: searched
source:
- https://triplewhale.readme.io/reference/creating-and-managing-triple-whale-api-keys
- https://triplewhale.readme.io/reference/troubleshooting-common-triple-whale-api-errors
- https://mcp.triplewhale.com/.well-known/oauth-authorization-server
derived_from:
- openapi/triple-whale-api-keys-api-openapi.yml
- openapi/triple-whale-compliance-api-openapi.yml
- openapi/triple-whale-data-in-api-openapi.yml
- openapi/triple-whale-data-out-api-openapi.yml
docs: https://triplewhale.readme.io/reference/creating-and-managing-triple-whale-api-keys
summary:
types: [apiKey, oauth2]
api_key_in: [header]
oauth2_flows: [authorizationCode]
note: >-
The REST API is API-key only — every published operation is secured by
apiKeyAuth (x-api-key) and no OpenAPI declares an oauth2 scheme. OAuth 2.1
appears only on the hosted MCP server, which is a separate surface.
schemes:
- name: apiKeyAuth
type: apiKey
in: header
parameter: x-api-key
surface: rest
sources:
- openapi/triple-whale-api-keys-api-openapi.yml
- openapi/triple-whale-compliance-api-openapi.yml
- openapi/triple-whale-data-in-api-openapi.yml
- openapi/triple-whale-data-out-api-openapi.yml
issuance:
console: https://app.triplewhale.com/api-keys
path: Data > APIs > Generate
shown_once: true
revocable: true
revocation_irreversible: true
scoped: true
scopes: scopes/triple-whale-scopes.yml
verification:
operation: validate-your-triple-whale-api-key
request: GET https://api.triplewhale.com/api/v2/users/api-keys/me
note: Returns the scopes attached to the presented key.
constraints:
- Shopify session JWTs and other token types are explicitly not accepted.
- >-
Keys are bound to the user who created them; if that user loses workspace
access, the key stops working.
- Separate keys are recommended per environment (production, testing, development).
failure_mode:
status: 401
causes: [missing header, revoked or expired key, missing scope, wrong token type]
- name: mcpOAuth
type: oauth2
surface: mcp
resource: https://mcp.triplewhale.com/sse
flows:
- flow: authorizationCode
authorizationUrl: https://mcp.triplewhale.com/authorize
tokenUrl: https://mcp.triplewhale.com/token
registrationUrl: https://mcp.triplewhale.com/register
code_challenge_methods: [S256]
grant_types: [authorization_code, refresh_token]
scopes: [moby:read, offline, offline_access]
token_endpoint_auth_methods: [none]
bearer_methods: [header]
discovery:
- https://mcp.triplewhale.com/.well-known/oauth-authorization-server
- https://mcp.triplewhale.com/.well-known/oauth-protected-resource
files:
- well-known/triple-whale-oauth-authorization-server.json
- well-known/triple-whale-oauth-protected-resource.json
method: probed
probed: '2026-08-13'
note: >-
Public client with dynamic client registration and PKCE; no client secret
(token_endpoint_auth_methods is ["none"]). An "MCP: Read" API key is the
alternative, non-OAuth path documented for the same server.
anonymous_surfaces:
- endpoint: GET https://api.triplewhale.com/api/v2/bi/avg
auth: none
spec: openapi/triple-whale-bi-benchmarks-openapi.json
evidence: >-
https://api.triplewhale.com/.well-known/ai-plugin.json declares auth type
"none" for this API.
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This security artifact
curl "https://apis.io/api/v1/security/triple-whale-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.