POST /v1/sites/{siteId}/application-access/reveal

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}/application-access/reveal \
  -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

Returns the administrator password of the one-click application on this site. The password is derived, never stored (engine.hosting.site_secrets, the same design as GET /v1/sites/{siteId}/wp-credentials), and the response is no-store. A POST deliberately, despite reading: revealing a credential must not be something a page load, a prefetch or a cache can trigger. Each reveal is audit-logged as site.application_credentials_viewed with the real actor — and nothing else writes that row, so it answers "who looked at this password" truthfully. Requires sites.view and sites.panel_access in the site's organisation. 409 when can_reveal is false (the customer set the password, or none can be shown); no audit row is written then.

Parameters

Response

Errors this endpoint can return

401 · 403 · 404 · 409 · 429