SpyFu · Authentication Profile
Spyfu Authentication
Authentication
SpyFu secures its APIs with apiKey and http across 3 declared security schemes, as derived from its OpenAPI definitions.
SEOPPCCompetitive IntelligenceKeyword ResearchAd HistoryBacklinksDomain AnalyticsSERP
Methods: apiKey, http
Schemes: 3
OAuth flows:
API key in: header, query
Security Schemes
Basic_Authentication_Token http
scheme: basic
Query_Parameter_Token apiKey
· in: query (api_key)
HMAC_Authentication_Header apiKey
· in: header (Authentication)
Source
Authentication Profile
generated: '2026-08-13'
method: derived
docs: https://developer.spyfu.com/reference
credentials_url: https://www.spyfu.com/account/api
note: >-
Three coexisting schemes, all key-based: HTTP Basic over SPYFU_API_ID:SECRET_KEY,
the same secret as an api_key query parameter, and a timestamped HMAC signature in
an Authentication header. No OAuth, no OIDC, and therefore no scopes — see
conformance/spyfu-conformance.yml. The query-parameter option puts the account
secret into URLs, logs and referrers; SpyFu documents it without a caveat.
source: openapi/spyfu-account-openapi.yml, openapi/spyfu-ad-history-openapi.yml, openapi/spyfu-competitors-openapi.yml,
openapi/spyfu-domain-stats-openapi.yml, openapi/spyfu-keyword-related-openapi.yml, openapi/spyfu-kombat-openapi.yml,
openapi/spyfu-ppc-keyword-openapi.yml, openapi/spyfu-ppc-research-serp-openapi.yml, openapi/spyfu-ranking-history-openapi.yml,
openapi/spyfu-seo-research-serp-openapi.yml
summary:
types:
- apiKey
- http
api_key_in:
- header
- query
schemes:
- name: Basic_Authentication_Token
type: http
scheme: basic
description: <a href="https://en.wikipedia.org/wiki/Basic_access_authentication#Client_side"
target="_blank">Basic Authentication</a> is a standard that involves encoding your <code>SPYFU_API_ID:SECRET_KEY</code>
into a Base64 string. Your <b>SpyFu API ID</b> and <b>Secret Key</b> can both be found under
the <b><a href="https://www.spyfu.com/account/api" target="_blank">Account Settings -> API
Usage</a></b> pa
sources:
- openapi/spyfu-account-openapi.yml
- openapi/spyfu-ad-history-openapi.yml
- openapi/spyfu-competitors-openapi.yml
- openapi/spyfu-domain-stats-openapi.yml
- openapi/spyfu-keyword-related-openapi.yml
- openapi/spyfu-kombat-openapi.yml
- openapi/spyfu-ppc-keyword-openapi.yml
- openapi/spyfu-ppc-research-serp-openapi.yml
- openapi/spyfu-ranking-history-openapi.yml
- openapi/spyfu-seo-research-serp-openapi.yml
- name: Query_Parameter_Token
type: apiKey
in: query
parameter: api_key
description: An API key can be added as a query parameter. Your API key is listed as "Secret
Key" found under the <b><a href="https://www.spyfu.com/account/api" target="_blank">Account
Settings -> API Usage</a></b> page<br>For example, to authorize with the API key <code>AB12WXY</code><br><pre><code>/apis/example_api/GetExample?domain=spyfu.com<span
class="token keyword">&api_key=AB12WXYZ</span></code></pre>
sources:
- openapi/spyfu-account-openapi.yml
- openapi/spyfu-ad-history-openapi.yml
- openapi/spyfu-competitors-openapi.yml
- openapi/spyfu-domain-stats-openapi.yml
- openapi/spyfu-keyword-related-openapi.yml
- openapi/spyfu-kombat-openapi.yml
- openapi/spyfu-ppc-keyword-openapi.yml
- openapi/spyfu-ppc-research-serp-openapi.yml
- openapi/spyfu-ranking-history-openapi.yml
- openapi/spyfu-seo-research-serp-openapi.yml
- name: HMAC_Authentication_Header
type: apiKey
in: header
parameter: Authentication
description: For even more security, each request can be individually authenticated with a
timestamped <a href="https://en.wikipedia.org/wiki/HMAC" target="_blank"><b>HMAC</b></a>
<em>(Hash Message Authentication Code)</em> signature. Composed of your secret key, a valid
timestamp, the API request path, and all request parameters. <h3>Creating the signature:</h3><br>Combine
the pieces that will be converted in
sources:
- openapi/spyfu-account-openapi.yml
- openapi/spyfu-ad-history-openapi.yml
- openapi/spyfu-competitors-openapi.yml
- openapi/spyfu-domain-stats-openapi.yml
- openapi/spyfu-keyword-related-openapi.yml
- openapi/spyfu-kombat-openapi.yml
- openapi/spyfu-ppc-keyword-openapi.yml
- openapi/spyfu-ppc-research-serp-openapi.yml
- openapi/spyfu-ranking-history-openapi.yml
- openapi/spyfu-seo-research-serp-openapi.yml
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/spyfu-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.