Mammoth Media · Authentication Profile

Mammoth Media Authentication

Authentication

Mammoth Media secures its APIs with apiKey, http, signed-request, and jwt across 5 declared security schemes, as derived from its OpenAPI definitions.

CompanyConsumerCryptocurrencyTradingCopy TradingFintechWebhookMCPDeveloper ToolsCLI

Methods: apiKey, http, signed-request, jwt Schemes: 5 OAuth flows: API key in: header

Security Schemes

apiKey apiKey

· in: header ()

bearer http

scheme: bearer

signed-request signed-request

scheme: secp256k1

jwt http

scheme: bearer

mcp-service-token apiKey

· in: header ()

Source

Authentication Profile

generated: '2026-07-20'
method: searched
source: https://docs.tokenbot.com/home/api-docs/authentication
docs: https://docs.tokenbot.com/home/api-docs/authentication
summary:
  types: [apiKey, http, signed-request, jwt]
  api_key_in: [header]
  api_key_headers: [X-API-Key, Authorization]
  notes: >-
    REST API accepts an API key via X-API-Key or Authorization: Bearer (the
    bearer value is treated as an API key, not a verified JWT). The tokenbot CLI
    uses a secp256k1 signed-request fast-path. The GraphQL API accepts a JWT
    bearer token (from login) or the CLI signed request.
schemes:
- name: apiKey
  type: apiKey
  in: header
  parameter_name: X-API-Key
  applies_to: REST API
  key_format:
    production: tb_live_<...>
    test: tb_test_<...>
  permissions: [ADMIN required for /v1/api-keys management]
- name: bearer
  type: http
  scheme: bearer
  applies_to: REST API
  note: Authorization Bearer value is interpreted as an API key (no standalone JWT verification on REST).
- name: signed-request
  type: signed-request
  scheme: secp256k1
  applies_to: REST API + GraphQL (CLI fast-path)
  headers:
  - x-tb-pubkey
  - x-tb-timestamp
  - x-tb-nonce
  - x-tb-sig
  canonical_string: "${METHOD}\\n${path}\\n${timestamp}\\n${nonce}\\n${sha256(body)}"
  replay_protection:
    clock_skew: "+/-60 seconds"
    nonce_window: 10 minutes
  implemented_by: "@tokenbot-org/cli-core"
- name: jwt
  type: http
  scheme: bearer
  bearer_format: JWT
  applies_to: GraphQL API
  note: JWT obtained from the login mutation.
- name: mcp-service-token
  type: apiKey
  in: header
  parameter_name: X-Service-Token
  applies_to: MCP server -> GraphQL backend
  companion_header: X-User-Id
public_endpoints:
- GET /v1/health
- GET /v1/health/detailed
- GET /v1/version
- GET /v1/auth/cli-challenge

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/mammoth-media-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.