Authentication
API keys, modes, scopes and rate limits.
Send your key on every request:
Authorization: Bearer sm_live_…Keys are created in the console, shown once, and stored only as a hash. Rotate or revoke them there.
Live and test keys
| Prefix | What happens |
|---|---|
sm_live_ | Real posts, real platform calls, plan usage and credits. |
sm_test_ | Dry runs. Validation, media checks and scheduling all run; nothing is ever sent. |
A key only changes posts of its own mode: a test key can't touch a live post.
Scopes
Keys carry scopes such as posts:read, posts:write, accounts:read, accounts:connect,
media:write and webhooks:write. New keys get every scope except apps:write,
accounts:delete and posts:approve (approving agents' posts). A missing scope is
403 SM_FORBIDDEN. Keys can also be limited to IP ranges.
Rate limits
Every answer carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Over
the limit you get 429 SM_RATE_LIMITED with Retry-After (seconds). Plan limits answer
429 SM_QUOTA_EXCEEDED, and posts that need more credits than you have answer
402 SM_INSUFFICIENT_CREDITS.
Idempotency
Send Idempotency-Key: <your id> on POST /v1/posts (or idempotencyKey in the body). Repeating
the request within 24 hours returns the first answer instead of posting twice.