Indicates the outcome of a bulk operation (e.g., bulk update or delete). Provides a general success message and an errors array listing any entities that could not be processed, along with the reason for failure for each.

The request is refused because of the state of the account. The body is the standard error envelope with code 403, and message tells the two bodies apart.

ACCOUNT_ARCHIVED: the account was archived and its database was dropped. A request for this account is refused when it uses an API key, HMAC-signed or sent as a Bearer API-key token. A request with an OAuth access token for an archived account gets 401 instead. A cookie session is refused when every account the user holds was archived. Changing the subscription of an archived account is refused too. Support restores such an account by hand.

This account has been offboarded and report data access is no longer available.: the account was offboarded, and report data access is refused.

Other 403 refusals, such as a missing permission, use the same envelope with their own message.

The list of accounts the user holds could not be fetched, so the request cannot continue. Only cookie sessions receive this response. The client may retry after the number of seconds in the Retry-After header. The body is the standard error envelope with code 503 and message ACCOUNT_DIRECTORY_UNAVAILABLE.

Indicates an error occurred while processing the request. The code provides an HTTP status code, message offers a human-readable explanation or an array of validation errors, and fields (if present) specifies which input fields were problematic.