Viewing API logs in the eWMS Frontend

You can use your API credentials to sign in to the eWMS Frontend (UI). When you do, you gain access to an API log that shows requests made using those credentials through the WMS. For every logged call you can inspect both the request payload and the response.

What’s included

All endpoints are logged except the logs and webhooks endpoints themselves. In other words, calls to /logs and webhook deliveries are not included in this view.

What you’ll see

Each log entry contains:

  • Requested at: timestamp of the call processed by the WMS
  • Target: the resource path (e.g. orders, shipments, variants/…)
  • Method: HTTP verb used (GET, POST, etc.)
  • Status: HTTP status code returned by the API
  • Request time: server-side processing time in milliseconds
  • Payload: the JSON request body (for non-GET requests)
  • Response: the JSON response body (including any validation errors)

Sign in using API credentials

  1. Open the eWMS Frontend URL provided to you by eWarehousing Solutions.
  2. On the sign-in screen, select the API login option.
  3. Enter your API credentials:
    • Client ID / Username: your API key
    • Secret / Password: your API secret
  4. Submit to sign in. You’ll be authenticated as the API client and taken into the UI.

If you don’t have API credentials yet, follow the steps in the Authentication guide or contact support.

Finding the API logs

  1. Once signed in, open the navigation and go to “eWMS logs” or “API logs”.
  2. Use the filters at the top to narrow by date range, HTTP status, or limit the number of results.
  3. Click a row to expand it and view the full request payload and response.

Notes and limitations

  • Scope: The log only shows calls executed with the credentials of the signed-in API client.
  • Exclusions: Calls to the logs endpoint itself and webhook deliveries are not shown.
  • Privacy: Payloads and responses may contain sensitive data. Handle exported information with care and restrict access to authorized users only.
  • Troubleshooting: Validation errors are visible in the Response panel. Use these to correct your payloads and retry.

Tips

  • Use the Status filter to quickly find failing calls (e.g. 4xx/5xx).
  • Expand the Response to copy error messages and paths when creating support tickets.
  • For bulk traffic, increase the Limit to fetch the latest N calls within your selected date range.

If anything is unclear or you cannot access the logs, reach out via the Support link in the sidebar.