Clickwise · Authentication Profile

Clickwise Authentication

Authentication

Clickwise secures its APIs with apiKey and http across 4 declared security schemes, as derived from its OpenAPI definitions.

CompanyAffiliate MarketingAffiliate NetworkPerformance Marketingtracked-linksPublishersE-CommerceMCP
Methods: apiKey, http Schemes: 4 OAuth flows: API key in: cookie, header

Security Schemes

apiKeyAuth apiKey
· in: header (X-API-Key)
cookieAuth apiKey
· in: cookie (sessionid)
tokenAuth http
scheme: bearer
mcpOAuth oauth2
· flows:

Source

Authentication Profile

Raw ↑ 
generated: '2026-11-04'
method: searched
source:
- openapi/clickwise-net-panel-openapi.yml, openapi/clickwise-net-publisher-openapi.yml
- https://partners.clickwise.net/developers/
- https://partners.clickwise.net/llms-full.txt
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - cookie
  - header
schemes:
- name: apiKeyAuth
  type: apiKey
  in: header
  parameter: X-API-Key
  sources:
  - openapi/clickwise-net-panel-openapi.yml
  - openapi/clickwise-net-publisher-openapi.yml
- name: cookieAuth
  type: apiKey
  in: cookie
  parameter: sessionid
  sources:
  - openapi/clickwise-net-panel-openapi.yml
- name: tokenAuth
  type: http
  scheme: bearer
  sources:
  - openapi/clickwise-net-panel-openapi.yml
  - openapi/clickwise-net-publisher-openapi.yml
- name: mcpOAuth
  type: oauth2
  flows:
  - authorizationCode
  pkce: S256
  scopes:
  - affiliate:read
  - affiliate:links
  applies_to: https://partners.clickwise.net/api/v1/mcp/account
  metadata: https://partners.clickwise.net/.well-known/oauth-authorization-server
  sources:
  - https://partners.clickwise.net/llms-full.txt
docs: https://partners.clickwise.net/llms-full.txt
credentials:
- name: Sandbox key
  prefix: cw_sbx_
  works_on: Publisher Products API only plus MCP search_products
- name: Publisher API key
  header: 'X-API-Key or Authorization: Bearer'
  works_on: whole Publisher API v1, MCP account tools, HasOffers/TUNE endpoint
- name: Reporting API token
  header: 'Authorization: Bearer'
  works_on: /api/v1/affiliate-reporting/*
- name: Offers credential
  prefix: cw_off_
  works_on: /offers/ and /offers.csv (pilot)
- name: Merchant conversions key
  prefix: cw_mk_
  header: X-Merchant-Key
  works_on: POST /api/v1/conversions/
- name: Site widget public key
  prefix: cw_pub_
  works_on: /api/v1/feeds/products/ and widget loader
notes: 'Send keys only in the X-API-Key or Authorization: Bearer header, never in URLs, page source or browser code.'

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.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/clickwise-net-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.