Reporting API and integrations

Administration → Integrations hosts the Reporting API — “Manage API tokens for connecting BI tools (Power BI, Excel, Metabase) to your workspace data.” The tokens are read-only and scoped to reporting data: an integration can read, never write.

SaaS tiers: the Reporting API is “Available on Professional and Enterprise plans.” In Community it is simply available.

Creating a token

New token opens Create Reporting Token — “This token grants read-only access to reporting data for this workspace. It will be shown once — copy it before closing.”

• Name — name it after the consumer, e.g. Power BI Dashboard, so revocation stays easy.
• Expiration — presets of 7/30/60/90 days, a Custom date, or No expiration. Prefer an expiry; rotating tokens beats immortal ones.

After Create token: “Copy this token now. It will not be shown again.” and the warning worth repeating — “Store this token securely. Anyone with it can read your workspace’s reporting data.” Orkyo stores only a hash; the list shows each token’s Prefix, Status (Active / Expired / Revoked), Created, Last used, and Expires.

Revoking

Revoke is immediate: “It will stop working immediately. Any integration using it will lose access.” Use it on any token whose consumer is retired — Last used tells you which ones those are.

Connecting Power BI

The page’s own quick-start:

1. “Create a token above and copy it.”
2. “In Power BI Desktop: Get Data → Web → Advanced.”
3. “Set URL to an endpoint” and authenticate with the token.

The API supports incremental refresh via updatedSince, so scheduled refreshes stay cheap. The full walkthrough is Connect Power BI to the Reporting API.

Practices that age well

• One token per consumer — never share a token between tools; revocation should have a blast radius of one.
• Expiry over trust — 90 days with rotation beats “No expiration”.
• Watch Last used — a token that stopped being used is a token to revoke.
• Token lifecycle events appear in the Audit log.