hosting

POST `/v1/sites/{siteId}/wordpress/abilities/run`

Run one of our plugins' abilities on the site.

Authentication

Send an API key as a bearer token. The key must carry the sites.view permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/wordpress/abilities/run \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "ability": <string> }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Runs a Page Builder Sandwich, Tranzly, Zinn® Chat, Zinn® Cache or Zinn® Reseller Toolkit ability (see listSiteWordPressAbilities) as the site's administrator, with the plugin's own permission check, input validation and edition gate (free or Pro). Audited with the ability's name, never its input or result. No charge: AI abilities use the site owner's own AI key. ⛔ Only our plugins' abilities (pbs/…, tranzly/…, zinn-chat/…, zinn-cache/…, zinn-reseller/…); anything else answers 422. The ability name travels in the body. Fleet only. Requires sites.view and sites.panel_access.

Parameters

Name	Type	Required	What it is
`siteId (path)`	`Uuid`	Yes	Site ID (UUIDv7).

Request body

Name	Type	Required	What it is
`ability`	`string`	Yes	—
`input`	`object`	No	The ability's input, matching its input schema.

Response

Name	Type	Required	What it is
`ability`	`string`	Yes	—
`result`	`object`	Yes	What the ability returned (its output schema).

Errors this endpoint can return

401 · 403 · 404 · 422 · 429 · 503

POST /v1/sites/{siteId}/wordpress/abilities/run