Query subuser informationSignature required
Use this API to obtain information about WorldFirst primary account and subaccount.
Structure
A message consists of a header and body. For details, see the following sections.
Request header
Request parameters
pageSize Integer REQUIRED
The number of items on each page.
pageNumber Integer REQUIRED
The page index that contains statement information.
Format: 1, 2, 3,...
Response parameters
result Result REQUIRED
The result of the API call.
primaryUserInformation User REQUIRED
The information of the primary account.
Note: This parameter is returned on demand only when result.resultStatus =
S.
userInformations Array<User> REQUIRED
The information of the subaccount.
Note: This parameter is returned on demand only when result.resultStatus = S.
totalCount Integer REQUIRED
The total number of items in the query.
Note: This parameter is returned on demand only when result.resultStatus = S.
More information:
- Maximum length: 8 characters
totalPageNumber Integer REQUIRED
The total number of pages.
Note: This parameter is returned on demand only when result.resultStatus = S.
More information:
- Maximum length: 8 characters
currentPageNumber Integer REQUIRED
The currency page index number.
Note: This parameter is returned on demand only when result.resultStatus = S.
More information:
- Maximum length: 8 characters
Request
Response
Result processing logic
After calling the API, a response is returned. The possible responses for result.resultStatus are:
Result/Error codes
| Code | Value | Message | Further action |
|---|---|---|---|
| SUCCESS | S | Success | |
| PROCESS_FAIL | F | A general business failure occurred. Do not retry. | Human intervention is usually needed. It is recommended that you contact our Technical Support Team to resolve the issue. |
| PARAM_ILLEGAL | F | Illegal parameters exist. For example, a non-numeric input, or an invalid date. | Check and verify whether the request fields, including the header fields and body fields, are correct and valid. For details on the fields of each API, see the specific API Structure section. |
| KEY_NOT_FOUND | F | The key is not found. | Contact our Technical Support Team to resolve the issue. |
| ACCESS_DENIED | F | The access is denied. | Contact our Technical Support Team to resolve the issue. |
| REQUEST_TRAFFIC_EXCEED_LIMIT | U | The request traffic exceeds the limit. | Call the interface again to resolve the issue. If the issue persists, contact our Technical Support Team. |
| INVALID_API | F | The called API is invalid or not active. | Check whether the correct API is being called. |
| INVALID_CLIENT | F | The client is invalid. | The client ID does not exist or is invalid. |
| INVALID_SIGNATURE | F | The signature is invalid. | Make sure the request is properly signed with a valid signature. |
| METHOD_NOT_SUPPORTED | F | The server does not implement the requested HTTP method. | Ensure the HTTP method is |
| UNKNOWN_EXCEPTION | U | API failed due to unknown reason. | The service might be down, retry later. If the issue persists, contact our Technical Support Team. |
| UN_SUPPORT_BUSINESS | F | Unsupported business. | Invalid parameter. Retry with the correct parameters. |
| ACCESS_TOKEN_EXPIRED | F | The access token has expired. | Refresh token to get a new access token or contact out Technical Support Team to address it. |
| USER_ACCOUNT_NOT_PRIMARY | F | The use account is not primary. | Use the primary account to query the interface. |
| AUTHORIZATION_NOT_EXIST | F | OAUTH does not exist. | Make sure that the input is correct. If the issue persists, contact our Technical Support Team to verify the authorization status. |