Plugin API endpoints


#1

A lot of plugins expose an API that is mostly used by their own config pages (eg. re-authorize or refresh metadata). In Riot we had a small discussion about it and hawken proposed the following format for API endpoints that we can possibly enforce with https://github.com/ServiceStack/ServiceStack/wiki/Routing#customizing-defined-routes.

Prefix: /plugin/<plugin_short_name>/

Thoughts?


#2

:+1:

Only backside I can see is that a plugin renaming itself means that any clients supporting that plugin will need updating (Any client could implement support for a plugin by just checking if the API endpoint is present). So better make this plugin_short_name something that the plugin defines itself and that can survive a plugin rebranding. So typically the last part of the plugin name (after the last dot) since it will be fairly independent of branding