Admin management

The admin workspace requires a user JWT with the administrator role. Project API keys cannot access /v1/admin endpoints. Users and projects are the primary entry points: open an account, browse its owned and joined projects, then manage the project's domains, routing, endpoints, API keys, team, billing and reputation.

Administrators can create, edit and delete operational resources, and edit/delete users. Stored messages, delivery events, execution logs, reputation history and audit records remain read-only. Newly generated keys and webhook secrets appear once; copy them after creation or rotation.

Local billing overrides persist until cleared and are separate from Polar's subscription status. They change effective Hisend access, not provider charges. Automatic reputation processing can recalculate an adjusted score or relock a project when later events arrive. Sending continues to enforce approval, sender verification, suppression and recipient quotas.

Deletion previews show affected resources and require confirmation for accounts and projects. Historical records remain inspectable in archived projects. Provider domain configuration is retained for a separate cleanup action; deleting a local project does not cancel Polar subscriptions. Cleanup failures remain visible and retryable, and active domains cannot be removed by cleanup.

Domain renames register a replacement identity and reset verification. Replace address-rule destinations explicitly, or explicitly choose to preserve their local parts on the new domain. Verification comes from SES status or DNS checks.

Admin child collections use page and limit (maximum 100), with a named resource array and total. Reputation supports 7, 30 and 90 days, all time, or UTC date bounds. Rates are unavailable when no sent denominator exists. Admin-only methods and request contracts are described in the checked-in OpenAPI schema.