Solved API/Webhooks/Microservices

[Gummibeer]

I already had some ideas which could/should be solved in a Microservice. So how about some kind of API to retrieve posts and send one.

Usecases could be the thread social image or the introduction welcome bot.

These services could be developed OpenSource, run on separated machines and provide features without forcing @Adam to code them.
For sure these integrations should get some kind of review if they access all data/categories/threads and not only the ones of a single (authorized) user.

 

[Adam]

Nice idea! I was thinking along the same lines as you as I have some repos going already:

adamgreenough/webwide-hello

👋 Landing page for Webwide.io community. Contribute to adamgreenough/webwide-hello development by creating an account on GitHub.

github.com

webwideio/webwide-social-images

💬 Twitter card and OpenGraph cover photo generator for Webwide discussions using PHP GD - webwideio/webwide-social-images

github.com

webwide-io/webwide-badges

🎫 Embeddable profile badges for Webwide.io members - webwide-io/webwide-badges

github.com

I can generate API keys either with guest permissions (preferable) or that have the same privileges as the user themselves.

API details here: XF 2.1 API endpoints

 

[Gummibeer]

Or the API is limited to public data and only to post a bot account is needed (should have the bot role).
The bot role could limit to replies only instead of new threads.

This way everyone can create integrations like a slack slash command, auto Twitter post or whatever.

For my cases I would need GET endpoints for categories and hreads - optional users. Also POST endpoint for thread reply.
And a webhook to get notified if something is posted.

 

[Adam]

Or the API is limited to public data and only to post a bot account is needed (should have the bot role).
The bot role could limit to replies only instead of new threads.

This way everyone can create integrations like a slack slash command, auto Twitter post or whatever.

For my cases I would need GET endpoints for categories and hreads - optional users. Also POST endpoint for thread reply.
And a webhook to get notified if something is posted.

Seems like a solid plan! I can provide API keys for a bot account and also a test forum for certain approved people that would like to experiment.

Any keys other than guest would have to be guarded of course but simple with a gitignore and a config file!

I also set up a few public endpoints as you can see from the profile api challenge and thread api on the landing page so could do those for read-only usecases as well.