Wholechain · Authentication Profile

Wholechain Authentication

Authentication

Wholechain API uses API keys for authentication, which must be included in request headers.

Wholechain declares 1 security scheme(s) across its OpenAPI definitions.

CompanySupply ChainTraceabilityBlockchainFood SafetyComplianceGS1Logistics

Methods: Schemes: 1 OAuth flows: API key in:

Security Schemes

API Key apiKey

Source

Authentication Profile

generated: '2026-10-18'
method: searched
generator: extract-docs-artifacts.py (deepseek)
source: https://developers.wholechain.com/GettingStarted/Authentication/
sources:
- https://developers.wholechain.com/GettingStarted/Authentication/
- https://developers.wholechain.com/GettingStarted/Introduction/
- https://developers.wholechain.com/GettingStarted/SandboxSetup/
description: Wholechain API uses API keys for authentication, which must be included in request headers.
schemes:
- type: apiKey
  name: API Key
  evidence: The Wholechain API uses API keys as the primary method of authentication.
  header: Authorization
  location: header
  how_to_obtain: 'Log into Your Wholechain Account: Use your credentials to log into your Wholechain platform account. Navigate to Settings: Once
    logged in, go to the settings section by clicking on the settings icon located in the top right corner of the dashboard. Account Settings:
    On the left-hand side panel, select Account Settings . Scroll Down to Integration Settings: In the Account Settings page, scroll to the bottom
    until you reach the section labeled Integration Settings . Generate Your API Key: Under Integration Settings , you will see an option labeled
    API Key . Click the Generate API Key button. This will generate a new API key for your account. Use Your API Key: Once the key is generated,
    you can copy it and use it in the headers of your API requests.'
docs: https://developers.wholechain.com/GettingStarted/Authentication/
note: The documentation mentions using the API key "in the headers of your API requests" but doesn't specify the exact header name. The Authorization
  header is a common convention for API keys, but the page doesn't explicitly state which header to use.

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/wholechain-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.

GitHub Google LinkedIn

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