Skip to main content

API Access

Written by Howard Katzenberg

GleanMark provides API access for programmatic integration with your existing tools. Create API keys, manage access, and connect via the Model Context Protocol (MCP).

How to Access

Go to Settings > API Keys (/settings/api).

Creating API Keys

In the Create API Key card:

  1. Enter a label (e.g., “Production Integration”, “Claude Desktop”)

  2. Click Generate Key

  3. Copy the key immediately — it’s shown only once. Keys are prefixed with gm_live_

  4. The key appears in your Active Keys list with its prefix, label, creation date, and last-used date

Key Management

From the API Keys page:

  • View active keys — see label, key prefix, creation date, last used

  • Revoke keys — permanently deactivate a key

  • Track usage — see when each key was last used

Keys are stored as SHA-256 hashes — GleanMark never stores your full key after creation.

What You Can Access

API keys provide access to:

  • Workspace data — portfolios, tracked owners, clients, alerts

  • Analytics — trademark analytics, portfolio metrics, alert summaries

MCP Integration

GleanMark supports the Model Context Protocol (MCP), which means you can connect it to AI assistants like Claude Desktop, ChatGPT, and other MCP-compatible tools. Your AI assistant gets direct access to GleanMark’s trademark search, analysis, and monitoring tools.

If Your Firm Requires Google or Microsoft Sign-In

Some firms on the Max plan require everyone on the firm’s email domain to sign in with the firm’s Google Workspace or Microsoft 365 account. If yours does, API keys do not work for members on that domain. To use GleanMark in ChatGPT or Claude, connect by signing in with your GleanMark account instead. See Require Google or Microsoft Sign-In for Your Firm.

Availability

API keys are managed within an organization. The API Keys page (and the API Keys entry in your profile menu) appears once you’re part of an organization, and every key is scoped to that organization. If you don’t see API Keys, you’re in a personal workspace — switch to or set up an organization first.

Tips

  • Label your keys descriptively — you can’t see the full key after creation, so the label is how you identify which integration uses which key

  • Revoke unused keys — if you’re no longer using an integration, revoke its key for security

  • Signed in with your account instead of a key? An AI app that connected by signing in has no key to revoke. Disconnect it under Connected apps in Account Settings.

  • One key per integration — create separate keys for each tool or service that connects to GleanMark

Related Features

Did this answer your question?