Preview which users a proposed credit limit change would block
Preview which users would be blocked by a proposed set of credit limit changes. This is a dry run: no credit limits are created, updated, or deleted.
Returns the users whose AI credit usage this month already meets or exceeds the effective limit they would have after the proposed changes. A user’s effective limit is the maximum of the tenant-wide limit and the limits of every team and organization they belong to.
Proposed creates are checked for field constraints and conflicts with existing limits; a successful preview does not guarantee that the write will succeed.
Notes
- Requires tenant admin permission.
createsare validated with the same rules as the create endpoint.updatesanddeletesmust reference existing credit limits byid.- Users are returned in an unspecified but stable order.
- Results are paginated, with a default
pageSizeof 50: pass the returnednextToken, with the samepageSizeand proposed changes, to get the next page. A page may contain fewer thanpageSizeusers, or none, even when more pages follow.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Headers
Set to true to access beta operations via /api/v3.
Request
Existing credit limits proposed for deletion, identified by id.
Token from a previous response’s nextToken, to continue from where that response ended. The pageSize and proposed changes must match the previous request.
Proposed changes to existing credit limits, identified by id.
Response
Token for retrieving the next page of blocked users, or null if there are no more. Pass it
in the next request as nextToken, with the same pageSize and proposed changes, to continue.
A non-null token may be followed by an empty page.