What it does today: the Public API (/v1), scopes granted per application, outgoing webhooks.
The self-service developer portal is a shell today: ServerWorks registers applications for you.
Text version of this diagram
- Your system → SocialWorks Public API /v1 (OAuth token)
- SocialWorks event → Webhook
- Webhook → Your system
Who it's for
- Developers connecting their systems to SocialWorks modules
- Companies automating with webhooks
- Partners building on SocialWorks
Questions
Is there documentation?
Yes, for the public API and webhooks; ServerWorks helps you register your application.
How is access controlled?
With OAuth scopes granted per application, so each one gets only what it needs.