hosting

POST `/v1/bulk-jobs/installed-plugins`

What is already installed across a bulk selection.

تصدیق‌هویت

یو API کی د بیئرر ټوکن (bearer token) په توګه ولیکئ. کی باید د sites.view اجازه ولري؛ له دې اجازې پرته کی د 404 پرځای د 403 په واسطه رد کیږي.

دا پای نقطه د سازمان هېڅ آی ډي نه اخلي. ستاسو کیلي مخکې تر مخکې هغه سازمان په ګوته کوي چې پورې اړه لري، او ځواب ورته محدود دی.

هڅه وکړئ

د انګلیسي په زاوي پنسونو کې هرڅه د خپلو ارزښتونو سره بدل کړئ، او د کلي ځای لرونکی ستاسو د ډشبورډ د کلي سره.

curl -X POST https://api.zinndigital.com/v1/bulk-jobs/installed-plugins \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "operation": <string<plugin_activate, plugin_deactivate, plugin_remove, plugin_update>>, "selector": <BulkSelector> }'

ننوتي یاست؟ ستاسو په ډشبورډ کې د API کنسول ستاسو د اصلي سازمان ID او ستاسو خپله کیلي ډکوي، او غوښتنه د ژوندی API په وړاندې پرمخ وړي ترڅو تاسو وکولی شئ اصلي ځواب وګورئ. دا پای ټکی (endpoint) د API په کنسول کې پرانیزئ

تفصیلات

The candidate list for plugin_activate, plugin_deactivate, plugin_remove and plugin_update — read from the sites themselves, not from the wordpress.org directory. Installing picks from what could go on; activating picks from what is already there, and those are different questions. POST, and it writes nothing. Same reason as previewBulkJob beside it: an explicit selection of 400 site ids does not survive a query string that proxies, browsers and access logs will truncate or record. No row is written and no job is started. ⛔ This is one network call per site, so it reads a bounded SAMPLE and says so. matched counts the whole selection, eligible counts the ones that could take the operation, and read counts the ones actually listed — three separate numbers, because a blind version of this endpoint would return read: 0, which must never be readable as "nothing is installed". Sites that could not be reached are named in unreadable rather than dropped into a shorter list that looks complete. uniform is false when the read sites do not all carry the same plugins, so the screen can say that plainly instead of silently acting on a subset. Requires sites.view plus the operation's own key — never a cheaper door than the single-site listing.

د غوښتنې بدن

نوم	ډول	اړین	دا څه شی دی
`operation`	`string<plugin_activate, plugin_deactivate, plugin_remove, plugin_update>`	هو	⛔ Only the operations that act on something already installed. Anything else is a `422` — there is nothing to list, and the directory search is the right tool.
`selector`	`BulkSelector`	هو	Which sites a job targets. ⛔ There is no `all`. A job belongs to exactly one organization and `all` would span every tenant on the platform; the fleet-wide act is a staff…
`selector_value`	`string`	نه	The product line, for `selector: product_line`.
`site_ids`	`string[]`	نه	—
`sample`	`integer`	نه	How many sites to read. A latency bound on an interactive read, not a capacity plan: the response reports what it did not reach, and the bulk job that follows covers the whole…

ځواب

نوم	ډول	اړین	دا څه شی دی
`operation`	`string`	هو	—
`matched`	`integer`	هو	Sites the selection resolves to, counted over the whole selection.
`eligible`	`integer`	هو	Of those, how many could take the operation at all.
`read`	`integer`	هو	How many were actually listed. ⛔ The number that makes an empty `data` interpretable: `0` means we looked at nothing, never nothing is installed.
`sampled`	`boolean`	هو	True when the selection is larger than what was read.
`uniform`	`boolean`	هو	False when the read sites do not all carry the same plugins. Computed here rather than by the client, because it decides what the customer is told.
`data`	`BulkInstalledPlugin[]`	هو	—
`unreadable`	`object[]`	هو	Sites in the selection whose plugins could not be listed. ⛔ Reported, never dropped — a shorter list that looks complete is worse than a short list that says so.

تېروتنې چې دا پای ټکی یې بیرته راګرځولی شي

401 · 403 · 422 · 429

POST /v1/bulk-jobs/installed-plugins