MySocials

API authentication

Scoped keys, Bearer tokens, and the 9 real scopes.

API authentication

The public API uses scoped API keys. Create them under Developer → API Keys (Creator and up).

Using a key

Send the key as a Bearer token:

bash
curl -H "Authorization: Bearer sk_live_..." https://www.mysocials.in/api/public/v1/me

Keys authenticate as you: every call draws from your plan's credit window and is bound to the scopes you granted the key.

Scopes

A key only holds the permissions you selected at creation:

  • posts:read, posts:write — inspect and create posts
  • accounts:read, accounts:write — list and manage connected accounts
  • analytics:read — summary metrics
  • syncs:read, syncs:write — sync routes
  • webhooks:read, webhooks:write — webhook endpoints

Least privilege is enforced server-side per endpoint — a posts:read key can never create a post.

Limits

Up to 5 active keys per user. Each key is limited to 60 requests per minute; responses carry X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers. Revoking is instant; the last-used timestamp of every key is visible on the API Usage page.