## Answer If an error occurs when executing the API, please check the contents of the POST parameters in the "URL", "Method", and "Request". --- ## Overview If an error occurs when executing the API, check the details of the error depending on its content. ## 1. URL If the following error message appears, the API URL (with or without hostname or subdirectory) may be incorrect. ``` The resource you are looking for has been removed, had its name changed, or is temporarily unavailable. ``` ``` HTTP Error 404.0 - Not Found The resource you are looking for has been removed, had its name changed, or is temporarily unavailable. ``` ※Error messages vary depending on the server. The URL to be specified varies depending on the environment. The following examples are URLs of the API for getting items information in each environment. ### Use in on-premise environment http://192.168.1.100/api/items/999/get ※Replace 192.168.1.100 with the IP address of your server. ### Use in cloud - Pleasanter.net https://pleasanter.net/fs/api/items/999/get ### Use in cloud - demo environment https://demo.pleasanter.org/api/items/999/get In an on-premise environment, the URL will differ depending on the path where you placed Pleasanter. The above is the URL when installed according to the user manual, so we do not guarantee that the above URL will work. If it does not work properly, please contact your system administrator. ## 2. HTTP Method Pleasanter's API uses POST as the HTTP method. If you see an error like the one below, the HTTP method may be different. ``` 403 Forbidden ``` ``` "Message": "The requested resource does not support the HTTP method 'GET'." ``` ※Error messages vary depending on the server. ## 3. Request Pleasanter API is written in JSON format. If the syntax is incorrect, the request will not be recognized as correct and the following error will be displayed. ``` {"Id":0,"StatusCode":401,"Message":"Authentication failed."} ``` If the above error occurs, - The JSON syntax is incorrect - The API key is incorrect It is highly likely that one of these is the cause. For more information on JSON syntax, please use a service such as "JSON Syntax Checker".