SIGNALS Docs
Exit Reader View
100%
Theme

Reader View

Plugin Callback Routes

Methods, authentication and payload ownership for installed plugin callbacks.

Dispatching a callback

Installed plugins declare callbacks under /api/v1/plugins/{vendor}/{package}/{path}. Core routing accepts GET, POST, PUT, PATCH and DELETE; the plugin manifest must declare the specific method and path or the request returns 404. The path can contain slash-separated segments.

MethodURLSummaryAbilityWeight
GET/api/v1/plugins/{vendor}/{package}/{path}Routes pluginsnone1

Payloads and successful responses belong to the plugin contract. Consult the installed plugin's documentation before sending a request. These callbacks are separate from the in-process Plugin SDK operations.

Authentication and rate limits

The manifest selects public, api or verifier:<name> authentication. Public routes need no token and allow 10 requests per minute per IP. API routes require an active bearer-token user and the declared ability, and allow 60 requests per minute per IP. Verifier routes require the plugin's signature check; after verification their configured limit is scoped by package, method, path and provider. The core document's empty security array does not mean every callback is public.

An optional provider_id selects an active channel provider belonging to the plugin. Invalid provider identifiers return 422; unavailable plugins, providers or undeclared callbacks return 404. See Plugin inbound requests for authoring the manifest and verifier.