Error Codes
All error codes listed in this page belong to the core functionalities of this framework. There are two basic categories within which the errors can be classified: Generic or Security errors. Generic errors might occur when attempting to send an incorrectly formatted soap envelope, or including invalid parameters in the request, etc. Within the security category we can find general security errors, app client or user specific errors.
Fault description
The faults are sent in compliance with the SOAP 1.1 protocol specification. Below you can see an example of how the faults are sent by Infojobs:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>WS.102</faultcode>
<faultstring>Client credentials not valid</faultstring>
<detail>
<timestamp>2012-05-14T11:35:35.000462+0200</timestamp>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
For each Fault, the following fields are returned:
| Name | Description |
|---|---|
|
faultcode |
String code that identifies the fault. |
|
faultstring |
Human readable description of the fault. |
|
detail |
Specific information about the fault. This information is used for troubleshooting. |
|
faultactor |
Optional field that provides information about who caused the fault to happen within the message path. |
| Name | Description |
|---|---|
|
timestamp |
When the exception has taken place. |
|
requestid |
Optional field that identifies the request causing the fault. This field will only be sent in case of an unexpected exception. |
The value returned in the requestid field is important for Infojobs to determine the precise cause of any error you might encounter. If you have to troubleshoot a problem with your request, we suggest that you capture the value of the requestid so you can report it to Infojobs along with the faultcode and timestamp fields.
Generic error codes
| Code | Description |
|---|---|
|
WS.INTERNAL |
WS call error. This error will be returned in case of unexpected error. If you need assistance please contact the web Service support team. |
|
WS.1 |
The requested operation does not exist. |
|
WS.118 |
WS client {CLIENT-NAME} is not linked to the company. |
|
WS.401 |
The given request protocol is not valid. Only https is supported. |
|
WS.405 |
The SOAP envelope could not be parsed. Please check whether the XML structure is correct. |
|
WS.406 |
Undeclared namespace within the given SOAP envelope. |
|
WS.407 |
Unexpected character within the given SOAP envelope. |
|
WS.413 |
Unexpected exception processing the response. Could not write attachments. |
|
WS.414 |
Unexpected exception processing the response. Response was of unexpected text/html ContentType. |
|
WS.431 |
Generic unmarshalling error. |
|
WS.432 |
Error unmarshalling unexpected element |
|
WS.433 |
Error unmarshalling a number. The paramter is not a valid number. |
|
WS.1000 |
This user lacks required products. |
|
WS.1001 |
This user lacks required products: {PRODUCT-NAME}. |
Security error codes
| Code | Description |
|---|---|
|
WS.104 |
Invalid o missing security header |
|
WS.105 |
Invalid o missing security token |
|
WS.106 |
Unsupported security token |
|
WS.110 |
Security token unavailable. |
|
WS.111 |
Message expired |
|
WS.119 |
Invalid security timestamp format. The valid format is yyyy-MM-dd'T'HH:mm:ss.SSS'Z' |
|
WS.201 |
Part of the message could not be recognized |
|
WS.202 |
Missing operation element |
|
WS.203 |
Wrong order on parameters given |
|
WS.211 |
Invalid envelope version. Only versión 1.1 is supported. |
|
WS.212 |
Invalid envelope format. |
| Code | Description |
|---|---|
|
WS.102 |
App client credentials not valid. |
|
WS.115 |
App Client not specified. |
|
WS.117 |
App Client not recognized as valid Web Service client. |
|
WS.130 |
The App Client have reached the max number of failed login attempts. You can try again the operation in few minutes |
| Code | Description |
|---|---|
|
WS.114 |
User email is not valid. |
|
WS.114 |
The user has not authorized any operation to the App Client. |
|
WS.150 |
Expried access token |
|
WS.151 |
Access token is empty |
|
WS.152 |
Access token is required |
|
WS.153 |
The user has not authorized this operation to the App client. |
|
WS.154 |
The access token is not valid. |
|
WS.155 |
The access token is not valid. |
|
WS.156 |
Wrong access token. |
