hosting

POST /v1/wordpress/sets

Save a new WordPress plugin/theme set.

All hosting endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

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.

Where your organisation id goes

This endpoint takes org_id as a field in the JSON body.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

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/wordpress/sets \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

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

⛔ A slug is refused, never sanitised: letters, digits, hyphens and underscores, never a leading hyphen (a wp-cli flag). Slugs are lower-cased and de-duplicated in order. A set holds at most 50 plugins, an org at most 100 sets, names are unique per org, and a set must hold at least one plugin or a theme. The org is the one the request names (org_id body field or X-Zinn-Org), else the caller's only org. Requires sites.view and sites.panel_access.

Request body

NameTypeRequiredWhat it is
org_idstringNo—
namestringNo—
pluginsstring[]No—
themestringNo—

Response

NameTypeRequiredWhat it is
idstringYes—
org_idstringYes—
namestringYes—
pluginsstring[]YesWordPress.org plugin directory names, in the order saved.
themestringYesA WordPress.org theme directory name, or empty for a plugins-only set.
created_atstringYes—
updated_atstringYes—

Errors this endpoint can return

401 · 403 · 422 · 429