Mammoth La Authentication

generated: '2026-10-26'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.tokenbot.com/home/api-docs/authentication.md
sources:
- https://docs.tokenbot.com/home/api-docs/authentication.md
- https://docs.tokenbot.com/home/api-docs/rest-api/api-keys.md
- https://docs.tokenbot.com/home/api-docs/quickstart.md
description: Authentication methods published on the TokenBot documentation pages.
schemes:
- type: apiKey
  name: X-API-Key
  evidence: 'Send your API key via the `X-API-Key` header:'
  location: header
  header: X-API-Key
  how_to_obtain: Create and manage keys with the CLI (`tokenbot apikey create ...`) or via the REST endpoints that require an ADMIN‑permission
    key.
- type: http-bearer
  name: Authorization
  evidence: 'You can also pass the same key as a bearer token — it''s treated identically:'
  location: header
  header: Authorization
  how_to_obtain: Create and manage keys with the CLI (`tokenbot apikey create ...`) or via the REST endpoints that require an ADMIN‑permission
    key.
- type: other
  name: Signed Request (CLI fast‑path)
  evidence: The `tokenbot` CLI authenticates with a **secp256k1 keypair** instead of an API key. Each request carries four headers and a signature;
    no key is transmitted.
  location: header
  how_to_obtain: Generated automatically by the `@tokenbot-org/cli-core` library; the client holds a secp256k1 private key and the CLI adds the
    required `x-tb-pubkey`, `x-tb-timestamp`, `x-tb-nonce`, and `x-tb-sig` headers.
docs: https://docs.tokenbot.com/home/api-docs/authentication.md