Your organization
Returns the organization the API key belongs to. The cheapest way to confirm a key works and to read the currency and timezone the rest of this API reports in.
Any active key, sent as a bearer token. Keys are owner-equivalent, so there are no scopes to grant and nothing to configure per endpoint. See Authentication.
None. There is nothing to put in the path or query.
ISO 4217 code for the money this organization charges. Amounts are integer minor units of it.
The organization's id, a UUIDv7. Opaque: pass it back as a string rather than parsing it.
When the organization was created.
The organization's name, as its own staff and members see it.
The organization's Zenly subscription tier.
IANA timezone name. Timestamps in this API are RFC3339 instants; this is the clock the organization reads them on.
These apply to every endpoint on the API, not just this one. Errors covers the body shape.
No bearer token, or a token that is unknown, revoked or expired. All four answer identically on purpose, so a caller probing tokens learns nothing about which is which.
The organization’s plan does not include the public API. It is available on Pro and above, and the check runs on every request, so a downgrade stops keys that were minted earlier.
The organization is not active.
The key is over its rate limit. Back off and retry.
Something failed on our side. The body carries a short sentence and never an internal error string, so quote your own request timestamp when reporting one.
curl "https://api.zenly.app.br/v1/organization" \ -H "Authorization: Bearer $ZENLY_API_KEY"
{
"id": "019f9a89-62bf-750a-bdc0-375919dea60a",
"name": "Iron District",
"timezone": "America/Sao_Paulo",
"currency": "BRL",
"plan": "Avançado",
"joinedAt": "2026-07-25T20:28:42.815055+02:00"
}