Authenticate with Twilio account SID and auth token or API key/secret; all Plugins API requests use the same credential model as the Twilio REST API.
Create or update a Plugin resource at /v1/PluginService/Plugins to register the plugin by unique name; each logical plugin has one Plugin resource regardless of how many versions exist.
Upload a new plugin bundle and create a Plugin Version resource at /v1/PluginService/Plugins/{PluginSid}/Versions, supplying the PluginUrl (bundle URL on a publicly accessible host such as Twilio Assets) and the version string.
Create a Plugin Configuration resource at /v1/PluginService/Configurations that groups one or more plugin versions together; a configuration represents a specific set of plugins to be active simultaneously.
Create a Release resource at /v1/PluginService/Releases referencing the configuration SID to activate it in the Flex project; releases are immutable — a rollback requires creating a new Release that references a prior Configuration.
Retrieve the currently active release and its associated configuration by querying GET /v1/PluginService/Releases/Active to audit what is live in production.
Known gotchas
Releases are irreversible — you cannot deactivate a release directly; the only rollback mechanism is creating a new Release that points to an older Configuration SID.
The PluginUrl in a Plugin Version must be a publicly accessible HTTPS URL at the time of the release; if the bundle URL becomes unavailable later, Flex agents will fail to load the plugin.
The Plugins API is distinct from the Flex Plugins CLI, which wraps this API; if your team uses the CLI for deployments, direct API calls that create Configurations or Releases outside the CLI may cause state drift that the CLI does not reconcile.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp