getPluginAutomation
GET
/api/v1/plugins/{pluginId}/automation
const url = 'https://example.com/api/v1/plugins/example/automation';const options = {method: 'GET', headers: {cookie: 'tilecast_session=<tilecast_session>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/plugins/example/automation \ --cookie tilecast_session=<tilecast_session>A known, installed plugin’s resolved automation document. Readable by any signed-in account. Operator clients dispatch generic commands on it without naming the plugin. Unknown plugins answer plugin_not_found, known-but-uninstalled ones plugin_not_installed, and plugins with no automation mapping plugin_automation_not_found.
Authorizations
Section titled “Authorizations”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters”pluginId
required
string
Registry identifier such as countdown_bar.
Responses
Section titled “ Responses ”Resolved automation document
Media typeapplication/json
object
data
required
object
apiVersion
required
integer
plugin
required
string
operations
required
Array<object>
object
operationId
required
string
method
required
string
path
required
string
risk
required
string
cliPath
required
Array<string>
mcpAction
required
string
input
string
description
string
exclusions
required
Array<object>
object
operationId
required
string
reason
required
string
Example
{ "data": { "apiVersion": 1, "operations": [ { "method": "get", "risk": "read", "input": "fields" } ] }}Dashboard authentication required
Plugin_not_found — the release does not define this plugin — or plugin_automation_not_found — it maps no operations into automation
Plugin_not_installed