Organization API access and PDF branding
Mint organization API keys, budget the shared credit balance, and brand partner PDF output.
- Who this is for
- Institution administrators and organization developers
- Before you begin
- Administrator or Developer role, with the institution active in the organization switcher
Who manages what
- Administrators and developers can mint organization API keys and buy credit packs.
- Branding is visible and editable only to administrators.
- A Developer role carries no worksheet seat — it exists purely for API and integration work.
Mint organization API keys
- Open the developer portal with the institution active in the switcher.
- Create a key from the organization surface; keys minted there belong to the organization, not to the person who created them.
- Store the key in your integration's secret manager — it is shown once and cannot be recovered, only replaced.
Credits are shared
Organization API keys draw from the institution's shared prepaid credit balance, whoever created the key or paid for the pack. Budget and purchase rules live in the seats and billing article.
Brand partner PDF output
Administrators can set a brand name and logo URL in the developer portal. Branding is applied to PDF output generated through the partner API.
Success check
Integration keys are organization-owned, credit spending is understood as shared, and API-generated PDFs carry the institution's branding.