Verify result and response codes

1. After confirming all parameters and testing your HTTPGet(), HTTPPost(), or HTTPPut() request, check the Public table for the HTTPResult code, which indicates the success of the transaction.

   • A successful request returns a value of 100 or greater, representing the TCP socket used.

   • A return value of 0 indicates a failure.

   • A return value of -2 means the instruction wasn’t executed because the data source wasn’t ready with new records in time.

2. To find more details, check the HTTPResponse parameter. Below are some common abbreviated response codes to provide additional information. For more details and codes, see the Quick reference for HTTPPost(), HTTPPut(), and HTTPGet() errors section of this document.

   200 – HTTP Request was successful.

   400 Bad Request – The server cannot or will not process the request due to an apparent client error. For example: a malformed request syntax, excessive size, or invalid request message framing.

   401 Unauthorized – You haven't authenticated with the server correctly. It's likely a problem in your header. You may need to specify and engage in the correct authentication type. The error message returned will specify the type of authentication you need to use. Types include Basic, Digest, and Bearer. Alternatively, if using Bearer authentication, this could mean the token or session has expired.

   403 Forbidden – Assuming you are making the request correctly, you might not have permissions.

   404 Not Found – The requested resource could not be found. Check your address to ensure you are using the right one.