Error codes

When the Account Center API returns an error, search for its type, code, or message, then narrow the result by the endpoint you called. The table shows the first recommended action; expand a row only when you need more context.

How to use this page

Save the error details

Save the endpoint, HTTP status, complete response body, and request time. Do not include API keys, access tokens, PANs, or other sensitive card data in logs or support requests.

Search the response

Paste the complete type, code, or message into “Search response.” If more than one result remains, filter by operation name, operationId, HTTP method, or path.

Follow the recommended action

Confirm the Endpoint column, then follow the primary action. Expand “View details” for the reason, retry guidance, and conditions for contacting UQPAY.

Error response format

Errors do not always include a type field. Use the HTTP status, code, message, and endpoint together. The same code can represent more than one message or condition, so do not identify an error from a single field alone.

Error code table

The type, code, and message columns preserve the values returned by the API. Endpoint entries include the operation name, operationId, HTTP method, and path. Dynamic messages are represented by a confirmed stable pattern or description.

Before contacting UQPAY, prepare the HTTP method and path, x-response-id, request time, and complete error response. Remove API keys, access tokens, PANs, and other sensitive information. Each row lists only the additional information needed for that error.

HTTP / Type	Code / Message	Endpoint	Recommended action
403 Legacy flat	`403` `Authorization error`	Applies to 10 public endpoints	Refresh authentication Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The authentication details are missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
401 Other envelope	`""` `Invalid authorization header`	Applies to 10 public endpoints	Refresh authentication Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The authentication details are missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`400` `IP not allowed`	Applies to 10 public endpoints	Refresh authentication Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The authentication details are missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
403 Legacy flat	`403` `x-client-id or email cannot be empty`	Applies to 10 public endpoints	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
403 Legacy flat	`1022` `account not found`	Applies to 10 public endpoints	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
403 Legacy flat	`1022` Message pattern `account is not active (account_status={status})`	Applies to 10 public endpoints	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
403 Legacy flat	`1022` Message pattern `API access is not active (api_status={status})`	Applies to 10 public endpoints	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1036` `Idempotency key error`	Applies to 4 public endpoints	Avoid duplicate submission Retry only after the condition identified by the message has been resolved. View details Why this happened: The same request or resource may already exist or still be processing. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 Legacy flat	`1038` `Idempotency endpoint error`	Applies to 4 public endpoints	Avoid duplicate submission Retry only after the condition identified by the message has been resolved. View details Why this happened: The same request or resource may already exist or still be processing. Retry: Retry only when the returned condition has been resolved and the operation permits it.
400 Legacy flat	`200` `Request is processing, please try again later.`	Applies to 4 public endpoints	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1018` `An internal error occurred, please try again later`	Applies to 4 public endpoints	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
404 Legacy flat	`1007` `sub-account associated with the on-behalf-of not found or deactivated`	Applies to 5 public endpoints	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
401 Legacy flat	`1027` `Invalid client id`	Access Token `POST /v1/connect/token` operationId: `access-token`	Refresh authentication Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The authentication details are missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
401 Legacy flat	`1028` `Invalid api key`	Access Token `POST /v1/connect/token` operationId: `access-token`	Refresh authentication Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The authentication details are missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1043` `Query date error`	Access Token `POST /v1/connect/token` operationId: `access-token`	Refresh authentication Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The authentication details are missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
401 Legacy flat	`1029` `Api key expired`	Access Token `POST /v1/connect/token` operationId: `access-token`	Refresh authentication Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The authentication details are missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
401 Legacy flat	`1031` `IP not allowed`	Access Token `POST /v1/connect/token` operationId: `access-token`	Refresh authentication Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The authentication details are missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1046` `Entity status not active`	Access Token `POST /v1/connect/token` operationId: `access-token`	Refresh authentication Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The authentication details are missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1045` `Api trading status error`	Access Token `POST /v1/connect/token` operationId: `access-token`	Refresh authentication Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The authentication details are missing, expired, or invalid. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1030` `Create access token error`	Access Token `POST /v1/connect/token` operationId: `access-token`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
500 Legacy flat	`1018` `An internal error occurred, please try again later`	Access Token `POST /v1/connect/token` operationId: `access-token`	Retry later Stop frequent retries. Wait briefly, then retry with exponential backoff. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry with exponential backoff; stop and contact UQPAY if the error persists. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries.
400 Legacy flat	`1006` Dynamic message Request body parsing or validation error returned by the request binder.	Create Account `POST /v1/accounts` operationId: `create-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Dynamic message Request body parsing or validation error returned by the request binder.	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `nickname is required`	Create Account `POST /v1/accounts` operationId: `create-account` Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
403 Legacy flat	`1022` `Sub-account creation is temporarily closed. Please wait for our notification.`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `inherit must be 1 or -1 for COMPANY sub-account`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `inherit must be 0 or omitted for INDIVIDUAL sub-account`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
404 Legacy flat	`1032` `Entity not exist`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `sub-accounts cannot create further sub-accounts`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `same-entity sub-account requires a company master`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `cross-entity sub-accounts are not enabled`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `individual sub-accounts are not enabled`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `master account is not approved`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `master account is not active`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `on-behalf operations are not enabled for this master account`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `same-entity sub-accounts are not enabled`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `business sub-accounts are not enabled`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `same-entity sub-account limit reached`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `{section}.{field} is required`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `{section}.{field} must be one of {allowed_values}`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `{section}.{field} {character_requirement}`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `{section}.{field} must be E.164 format`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `{section}.{field} must be a valid email`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `{section}.{field} must be YYYY-MM-DD`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `{section}.{field} must be ISO 3166-1 alpha-2`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `ownership_details is required`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `ownership_details.representatives is required`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `ownership_details.representatives[{index}] must be an object`	Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1043` `Query date error`	Create Account `POST /v1/accounts` operationId: `create-account` Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
500 Legacy flat	`1034` `Create data error`	Create Account `POST /v1/accounts` operationId: `create-account` Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`1003` `This company registration number is already registered. Please check the number, or contact support if you believe this is a mistake.`	Create Account `POST /v1/accounts` operationId: `create-account` Create SubAccount `POST /v1/accounts/create_accounts` operationId: `create-sub-account`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1043` `Query date error`	List Connected Accounts `GET /v1/accounts` operationId: `list-connected-accounts`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
404 Legacy flat	`1032` `Entity not exist`	Retrieve Account `GET /v1/accounts/{id}` operationId: `retrieve-account`	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1043` `Query date error`	Retrieve Account `GET /v1/accounts/{id}` operationId: `retrieve-account`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`1006` `invalid status`	List RFIs `GET /v1/rfis` operationId: `list-rfis`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1043` `Query date error`	List RFIs `GET /v1/rfis` operationId: `list-rfis`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
404 Legacy flat	`1007` `rfi not found`	Retrieve RFI `GET /v1/rfis/{id}` operationId: `retrieve-rfi`	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1043` `Query date error`	Retrieve RFI `GET /v1/rfis/{id}` operationId: `retrieve-rfi`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`1006` Dynamic message Request body parsing or validation error returned by the request binder.	Answer RFI `POST /v1/rfis/answer` operationId: `answer-rfi`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
404 Legacy flat	`1007` `rfi not found`	Answer RFI `POST /v1/rfis/answer` operationId: `answer-rfi`	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1043` `Query date error`	Answer RFI `POST /v1/rfis/answer` operationId: `answer-rfi`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`1006` `rfi is not awaiting response`	Answer RFI `POST /v1/rfis/answer` operationId: `answer-rfi`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `this rfi has no outstanding questions`	Answer RFI `POST /v1/rfis/answer` operationId: `answer-rfi`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `must answer all questions: missing {field_key}`	Answer RFI `POST /v1/rfis/answer` operationId: `answer-rfi`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `answer type mismatch for {field_key}: want {expected_type}, got {received_type}`	Answer RFI `POST /v1/rfis/answer` operationId: `answer-rfi`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `attachments required for {field_key}`	Answer RFI `POST /v1/rfis/answer` operationId: `answer-rfi`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `file not found or not owned: {file_id}`	Answer RFI `POST /v1/rfis/answer` operationId: `answer-rfi`	Verify the resource Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The resource is missing, unavailable, or does not belong to the current account. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` Message pattern `text required for {field_key}`	Answer RFI `POST /v1/rfis/answer` operationId: `answer-rfi`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `rfi is no longer awaiting response`	Answer RFI `POST /v1/rfis/answer` operationId: `answer-rfi`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1035` `update date error`	Answer RFI `POST /v1/rfis/answer` operationId: `answer-rfi`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`1006` `notes max length 50`	Upload A File `POST /v1/files/upload` operationId: `upload-file`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `missing file form field: {binder_error}`	Upload A File `POST /v1/files/upload` operationId: `upload-file`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1041` `s3 client not initialized`	Upload A File `POST /v1/files/upload` operationId: `upload-file`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`1040` `File size error`	Upload A File `POST /v1/files/upload` operationId: `upload-file`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`1039` Message pattern `file type .{extension} not allowed`	Upload A File `POST /v1/files/upload` operationId: `upload-file`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1041` `open uploaded file: {storage_error}`	Upload A File `POST /v1/files/upload` operationId: `upload-file`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
500 Legacy flat	`1041` `s3 upload: {storage_error}`	Upload A File `POST /v1/files/upload` operationId: `upload-file`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
500 Legacy flat	`1034` `Create data error`	Upload A File `POST /v1/files/upload` operationId: `upload-file`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
400 Legacy flat	`1006` Dynamic message Request body parsing or validation error returned by the request binder.	Get File Download Links `POST /v1/files/download_links` operationId: `download-links`	Check the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: A request parameter, resource state, or account setting does not allow this operation. Retry: Retry after correcting the request or resource state.
400 Legacy flat	`1006` `file_ids is required`	Get File Download Links `POST /v1/files/download_links` operationId: `download-links`	Correct the request Correct the request or resource identified by the message and API Reference, then retry. View details Why this happened: The request does not meet an endpoint parameter or business rule. Retry: Retry after correcting the request or resource state.
500 Legacy flat	`1043` `s3 client not initialized`	Get File Download Links `POST /v1/files/download_links` operationId: `download-links`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
500 Legacy flat	`1043` `Query date error`	Get File Download Links `POST /v1/files/download_links` operationId: `download-links`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.
500 Legacy flat	`1043` `presign: {storage_error}`	Get File Download Links `POST /v1/files/download_links` operationId: `download-links`	Retry later Retry only after the condition identified by the message has been resolved. View details Why this happened: The request could not be completed and changing request parameters alone may not resolve it. Retry: Retry only when the returned condition has been resolved and the operation permits it. When to contact UQPAY: Contact UQPAY if the same error persists after the recommended action and limited retries. Also provide: x-response-id, request time, HTTP method and path, complete error response.

Getting Started

Authentication

Account Management

Webhooks

Reference

How to use this page

Error response format

Error code table

​How to use this page

​Error response format

​Error code table

​Related documentation

How to use this page

Error response format

Error code table

Related documentation