portfolio_max_api_keys_exceeded
The portfolio already holds the maximum number of ACTIVE credentials. The cap is counted over the managing company and its active children together, not per company, so onboarding another child to mint its credential will not let you create this one either.
| Code | Type | HTTP | Category |
|---|---|---|---|
portfolio_max_api_keys_exceeded | authorization_error | 422 | Authorization |
Cause
The portfolio already holds the maximum number of ACTIVE credentials. The cap is counted over the managing company and its active children together, not per company, so onboarding another child to mint its credential will not let you create this one either.
What to do
Revoke an active credential you no longer use and try again, or request an increase of the portfolio cap. Unlike a permissions problem, no scope is missing here.
Related
All Authorization error codes
Causes and actions for errors in this category.
Error codes by category
Find an error by the category that emits it.
Full reference table
All codes, HTTP statuses, types and descriptions in one reference.
Error model
Interpret the error envelope and handle errors by code.