partner

GET /v1/partner/own-plugin-builds

Every published build of our WordPress plugins, by tree digest.

All partner endpoints

All developer docs →

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/partner/own-plugin-builds \
  -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

For a partner platform (V1) that exempts our own plugins from its customers' file and disk allowances (owner ruling 2026-10-01): a plugin folder is exempt only when its tree digest equals the digest of a build we published (our release channel, Freemius free and premium builds, WordPress.org). The digest is SHA-256 over every directory, every file's path and size, and the content of each top-level .php file, prefixed with digest_version. want names folder versions the partner saw on its own sites that this list lacks (dir@version, comma-separated, at most 200). They are queued and looked up at our sources by our hourly sweep, never during this request; queued counts the new ones. Requires a partner key holding partner.plugins. Rate-limited.

Parameters

NameTypeRequiredWhat it is
want (query)stringNoComma-separated dir@version pairs to look up.

Response

NameTypeRequiredWhat it is
digest_versionstringYes—
queuedintegerYesHow many want pairs were newly queued for a lookup.
buildsobject[]Yes—

Errors this endpoint can return

401 · 403 · 429