The following shows the processing result codes that are returned when a Resource is accessed by the Resource API.
*Note that these codes differ from the codes of Authentication and Authorization Error.
Code | Details | Common causes | Actions |
---|---|---|---|
0 | The processing is successful. | ー | ー |
5 | The user ID is invalid. | The status of the user ID is before use or completion of use. | Check the usage of the user ID. |
6 | The user who is currently accessing the data has no privilege. | ー | ー |
7 | The specified Resource does not exist. | ー | ー |
8 | An internal system error occurred. | A control code is included in the registered data. | Remove the control code and try again. |
Multiple IDs are specified for the Condition via “and” condition. | Change the condition to “or” and try again. | ||
9 | The system is temporarily suspended. | The HRBC and API are under maintenance. | Wait for the maintenance to be completed. |
100 | The specified parameter is invalid. | The parameter is incorrectly written, for example, with a missing character. | Check the description of the parameter. |
The item that was in use has been deleted on HRBC. | Check with the system administrator of HRBC about the problem and consider how to take measures, such as the relevant item will not be specified for the parameter. | ||
The “itemstate” is specified with “delete” or “all” and, the “condition” is specified other than {Resource}.P_Id, {Resource}.P_UpdateDate, or {Resource}.P_UpdatedBy. |
Review the value of the “itemstate” or the value of “condition.” | ||
101 | The necessary parameter is not provided. | The acquired Access Token is not correctly reflected. | Review the program so that the Access Token is correctly reflected. |
In the case of the Post Method, the Content Type and charset are not specified. | Check the HTTP Header and specify the Content Type and charset. | ||
The parameter that is required for each Resource API is not specified. | Check the parameter required for the each Resource API page. | ||
102 | Too many parameters are specified. | ー | ー |
103 | The value of the specified parameter is invalid. | The Content Type to be specified for the Header is incorrectly set. | Check the HTTP Header and specify the Content Type and charset. |
The acquired Access Token is not correctly reflected. | Review the program so that the Access Token is correctly reflected. | ||
The format of the Date Time specified for the parameter is incorrect. | Check the Field Type & Data Type List and specify the item in the correct format. | ||
The Option is incorrectly specified. | Check the XML Format - Write API > Field Type:Option, and review how to specify the Option. | ||
The specification for referring to an upper-level Resource item is incorrect. | Check the Parameter > Read - Field and review how to specify the item. | ||
The User ID that was used for development is specified for a Request for the actual environment. | The user differs between the development environment and the actual environment. Check the correct User ID. |
||
The item that was in use has been deleted on HRBC. | Check with the system administrator of HRBC about the problem and consider how to take measures, such as the relevant item will not be specified for the parameter. | ||
When performing a Phase Write API on a resource that already has a Phase registered, the Phase date is blank, or the Phase date contains a date that is older than the current latest Phase date. |
The Phase date should be set to a date newer than the current most recent Phase. |
||
104 | An invalid character code is included. | ー |
ー |
105 | An unsupported Encoding is specified. | ー | ー |
106 | An invalid format is specified for the specified value. | ー | ー |
107 | The specified value cannot be recognized as the format of integer values. | ー | ー |
108 | The specified value cannot be recognized as the format of real numbers. | ー | ー |
109 | The specified value does not match the type of the parameter. | ー | ー |
110 | The specified value is invalid as the format of the date. | ー | ー |
111 | The specified value is invalid as the format of the date and time. | ー | ー |
112 | The specified value is invalid as the format of the age. | ー | ー |
113 | The specified value exceeds the range. | ー | ー |
114 | The specified value is too small. | ー | ー |
115 | The specified value is too large. | ー | ー |
116 | No value is specified. | ー | ー |
124 | The specified value exceeds the range. | The “itemstate” is specified with “delete” or “all” and, the {Resource}.P_UpdateDate is specified with a date earlier than 91 days ago for the “condition.” |
Review the value of the “itemstate” or the value of “condition.” |
126 | Cannot be set as the latest phase. | The phase date is earlier than the registered date and time. | Check the Phase Update and specify this item so that the conditions are met. |
127 | The latest phase is not set. | Even though no phase is specified, the phase date or phase memo is specified. | When the phase date or phase memo needs to be registered, the phase must also be specified. If unnecessary, remove the specification of the phase date or phase memo. |
133 | The value of the specified itemstate is invalid. | The itemstate is specified with a value other than “deleted,” “all,” or “existing.” | Correct the value of the “itemstate.” |
301 | The target data already exists. | Process already exists in the combination of the same Job and Resume. | Process in the combination of the same Job and Resume cannot be registered. Update the existing record or change the combination before registering the Process. |
302 | The data update failed due to an error with the transaction. | A temporary error may have occurred. | Try the Request again. |
303 | The data have child elements. | ー | ー |
304 | The data is referred to by another element. | ー | ー |
400 | There is no or insufficient access right to the data. | ー | ー |
401 | The Access Token is expired. | ー | ー |
402 | The Access Token is invalid. | The acquired Access Token is not correctly reflected. | Review the program so that the Access Token is correctly reflected. |
403 | There is no access right to the data. | The procedure for granting access to the Company DB has not been performed. | Check the necessary Scope and perform the procedure for Granting Access to Company DB. |
The necessary Scope was insufficient for performing the procedure for granting access to the Company DB. | Check the necessary Scope and perform the procedure for Granting Access to Company DB. | ||
404 | The partition does not exist or is outside the usage period. | HRBC has not started being used. | Try again after starting to use HRBC. |
HRBC is canceled. | The API access is unavailable. | ||
The Partition ID is incorrect. | Specify the correct Partition ID. | ||
The request_type of the Partition API is specified with “0” even though HRBC is not logged in. | Specify Request_type with “1” or try again with HRBC logged in. | ||
The request_type is specified with “1” even though the procedure for granting access to the Company DB has not been performed. | Check the necessary Scope and perform the procedure for Granting Access to Company DB. | ||
No accessible partition exists because the Access Token is expired. | Acquire an Access Token or Refresh the Access Token. | ||
406 | You do not have access permission | IP address restriction is active and the specified IP address is out of the permissible range or the IP address could not be read correctly. | Please use the designated application from to apply to add the specified IP address to the permissible range. |
500 | The maximum number of registration records is exceeded. | No restriction plan applies to the current contract, so this error basically does not occur. | |
601 | There is no app privilege for processing the Request. | A request is made beyond the processing privilege that was set when registering the app. | Contact our help desk, and PORTERS will check the request and registration details. |
1000 | The processing failed. | ー | ー |