Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.summand.com/llms.txt

Use this file to discover all available pages before exploring further.

API keys authenticate requests to the Summand REST API. Each key is tied to your user account and inherits the same access — owned datasets plus anything explicitly shared with you.
Treat API keys like passwords. Don’t commit them to source control or paste them into shared channels. Anyone with your key can read every dataset you can.

​
Create a key

1

Open settings

Sign in at summand.com and open Settings.
Opening Settings in the Summand dashboard
2

Go to the Developer tab

Select the Developer tab in the settings sidebar.
Developer tab in Settings
3

Create a new key

Click New API key, give it a descriptive name (for example, “ETL pipeline” or “Personal scripts”), and confirm.
Creating a new API key
4

Copy and store the key

The full key (starting with sk_summand_) is shown once. Copy it immediately — Summand stores only a hash, so you can’t view the key again later. If you lose it, revoke and create a new one.
Copying the generated key

​
Use the key

Pass the key as a Bearer token on every request to the Summand REST API: 
curl https://api.summand.com/tables \
  -H "Authorization: Bearer sk_summand_your_key_here"
API keys are for direct REST API access. The Summand MCP server uses OAuth instead — there’s no need to copy a key into claude.ai or ChatGPT.

​
Revoke a key

If a key leaks or you no longer need it, revoke it from the same Developer tab. Revocation is immediate — the next request using that key will return 401 Unauthorized.
Revoking an API key

​
Best practices

  • One key per integration. Generate a separate key for each script or service so you can revoke them independently.
  • Rotate periodically. Replace long-lived keys on a schedule that matches your security policy.
  • Use the MCP server for AI clients like claude.ai and ChatGPT. It authenticates via OAuth — no API key required.