Authentication
Send an API key as a bearer token. This endpoint does not state a specific permission in the specification, so give your key the least it needs and check the response rather than assuming.
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 GET https://api.zinndigital.com/v1/wordpress/cli-commands \
-H "Authorization: Bearer zdk_live_…"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
The allow-list, served rather than copied into each client. ⛔ A client-side copy is a second authority that starts identical and drifts: the day a command is added, a stale client keeps refusing it while the engine runs it happily, and the day one is removed the client offers a command that answers `422`. Platform-wide and identical for every customer; names no site. Requires authentication only.
Response
| Name | Type | Required | What it is |
|---|---|---|---|
data | string[] | Yes | Permitted commands, space-joined, sorted. |
Errors this endpoint can return
401 · 429