Checking Error Logs

With the /api/calls endpoint, you can filter by the status codes of the calls you want to see, which can help you review the calls and the cause of the error.

Here are a couple examples of getting API calls that weren't successful.

/api/calls?code=[not]200
/api/calls?code=[gt]400

You can also view call history and errors in your ItemPath logs. Logs keep track of all activity that uses the ItemPath API, either via the interface or API calls.

Logs location Logs overview

Try filtering your log results with any of these four fields:

  1. Status Code: Choose a HTTP code from the list to return only messages with that code.
  2. User: Select an ItemPath user to filter activity from that login.
  3. Search: Enter your text to search error responses.
  4. Date Range: Set the start and end date and time of the range you wish to search.
Logs filter 1 Logs filter 2

There is an option to "Clear Logs" in the top-right of the Logs page if needed, but we generally recommend keeping log history. Logs are stored in ItemPath Cloud for one month.

If you have an error that you've looked into and are unable to resolve, please contact our support team at support@itempath.com.

Congratulations, you've completed the ItemPath API course!
100%