Skip to Content
GrowSocialelion API

Authentication and scopes

API keys, the X-GSE-Brand header, and the scopes that decide what a key may do.

API keys

Every call carries one header: Authorization: Bearer gse_mcp_.... Create keys under Account > API keys. A key belongs to one workspace. Only an owner or an admin can create or revoke one. The secret is shown once; we store a hash, never the key.

These are the same keys MCP clients use. Keys made before the rename (they were called MCP keys) keep working, with no change.

curl https://growsocialelion.com/api/v1/get_overview \
  -H "Authorization: Bearer gse_mcp_YOUR_KEY" \
  -H "X-GSE-Brand: YOUR_BRAND_ID"

Which brand

X-GSE-Brand names the brand a call acts for. Get the ids from list_brands. Leave the header out to act for the key's first brand. A brand id from another workspace, or one the key is not bound to, is refused with 403 and nothing runs.

Scopes

A key holds a set of scopes. Each endpoint needs one scope, and an endpoint that costs credits also needs spend. A call without the scope is refused with 403 and "code": "scope", and nothing runs. A key can also be bound to some brands and some networks only.

ScopeWhat it allowsOn a new key
readRead your own brand data: posts, metrics, runs, the audit trail, the plan, stored mentions and trends. Free, unless you ask a billed network for a fresh read.You choose
draftsSave drafts, articles and series proposals to the Inbox, and withdraw your own drafts. Nothing publishes.You choose
researchScan a network for reply targets and propose a voice profile. These read networks and can cost credits.You choose
spendAllow calls that cost credits. Without it, a call that would spend is refused and nothing is spent.You choose
actionsNot grantable to a key on the hosted service.Not available
scheduleSet the schedule of a series a person already approved in the app.You choose
posts:approveApprove a pending Inbox draft and schedule it, with the same checks as the Inbox's Schedule button. A separate scope: never on by default, and only allowlisted workspaces can grant it.Allowlisted workspaces only, never on by default

No scope publishes

No scope lets a key publish a post now. Approval is a person in the Inbox, in their own signed-in session, with one exception: posts:approve. It is a separate scope that is never on by default and that only allowlisted workspaces can grant. A key with it can approve a pending draft and schedule it, with the same checks as the Inbox's Schedule button. That is the same for MCP and REST.

Keep keys safe

  • Use one key per app or machine, and give it a clear label. The label is what the Inbox, the log and Usage show.
  • Give each key only the scopes it needs. Leave out spend unless the app must run paid reads.
  • Revoke a key on Account > API keys. It stops at once, for MCP and REST.
  • Never put a key in browser code. Call the API from a server.