API Reference
Authentication
Most Developer API routes authenticate with a ShareViral API access token. Token management endpoints use your Firebase session instead.
Generate tokens in Settings → Developer API. Prefer the dashboard for day-to-day key rotation; the regenerate/revoke HTTP endpoints are for programmatic management.
Bearer token
Publishing and scheduling endpoints require an API access token in the Authorization header. Tokens are prefixed with sv_.
Header
Authorization: Bearer sv_your_api_tokenUsed by:
- Make Post
- Scheduled posts (create, list, update, delete)
Firebase ID token
Regenerate and Revoke do not accept the sv_ developer token. They require a Firebase Auth ID token from a signed-in user:
Header
Authorization: Bearer <firebase_id_token>Obtain the ID token from the Firebase client SDK after login (for example user.getIdToken()).
Plans
Developer API access requires an active Viral Pro or Viral Business subscription. Video posts via Make Post / scheduled posts also require a plan that allows video publishing.