CatalogWise

Article

API keys and developer usage

Scale and Agency users can automate scans, reports and usage reads through API keys.

Key lifecycle

Name the key, create it, copy the secret once, then use only masked rows afterward. Revoked keys must fail.

Scopes and limits

Use scoped keys for scan, report and usage workflows. Rate limits and credit costs are documented on the developer page.

Security

Never place keys in client-side code, docs, screenshots, support tickets or browser-exposed environment variables.

FAQ

Where should I go next?

Follow the in-product CTA on the relevant dashboard or public route. If the state is locked or requires configuration, the page should explain the plan or provider requirement.

Related resources

Turn this into a catalog readiness result.

Run a public scan, review visible gaps and unlock the premium report when you need SKU-level diagnostics and a remediation roadmap.

Open CatalogWise
API keys and developer usage | CatalogWise Help | CatalogWise