Automate StatSocial Platform
HumDay reads StatSocial Platform’s own published API description and derives 17 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What StatSocial Platform is
API Reference: The StatSocial API is organized around REST. Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which can be understood by off-the-shelf HTTP clients, and we support cross-origin resource sharing to allow you to interact securely with o
API host: api.statsocial.com
What HumDay can do in StatSocial Platform
8 documented operations change something in StatSocial Platform.
- POSTGet list of generated reports
/reports/status/ - POSTUsed to create tweet reports
/reports/tweet/create/ - POSTStep 3 of executing custom report
/reports/custom/create/ - POSTUsed to create twitter follower report
/reports/twitter/create/ - POSTObtain report output
/reports/ - POSTGet report dates available for a specific report
/reports/dates/ - POSTStep 2 of executing custom report
/reports/custom/insert/ - POSTStep 1 of executing custom report
/reports/custom/generate/
What HumDay can read from StatSocial Platform
These are the operations a schedule or a trigger can watch.
- GETGet list of generated reports
/reports/status/ - GETUsed to create tweet reports
/reports/tweet/create/ - GETStep 3 of executing custom report
/reports/custom/create/ - GETUsed to create twitter follower report
/reports/twitter/create/ - GETObtain report output
/reports/ - GETGet report dates available for a specific report
/reports/dates/ - GETUsed to understand API usage
/applications/status/ - GETStep 2 of executing custom report
/reports/custom/insert/ - GETStep 1 of executing custom report
/reports/custom/generate/
How automating StatSocial Platform works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live StatSocial Platform account.
- Grant access, then go live. You approve the specific StatSocial Platform operations it may use — and only those.
Automate StatSocial Platform with these
- Discord242 operations
- CPY PeerTube185 operations
- Mastodon Specification (https //github.com/mastodon/mastodon)127 operations
- spoonacular99 operations
- Discourse Documentation84 operations
- Twitter80 operations
- Trashnothing trash nothing76 operations
- Contribly44 operations
- Clubhouseapi Clubhouse41 operations
- Semantria41 operations
- DEV Forem40 operations
- Medium32 operations
Categories
Questions about StatSocial Platform automation
- Can HumDay connect to StatSocial Platform?
- Yes. HumDay reads StatSocial Platform's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 17 operations are documented.
- Do I need to write code to automate StatSocial Platform?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your StatSocial Platform account.
- What can HumDay do in StatSocial Platform?
- 8 of the 17 documented operations change something in StatSocial Platform, and 9 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my StatSocial Platform account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to StatSocial Platform is held behind that approval.
Where this came from
The operations above are read from a published API description for StatSocial Platform at docs.statsocial.com/wp-content/themes/twentyfifteen/json/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2023-02-17.