Your WooCommerce API logs are the single source of truth for every request AnyAPI sends. Whenever an order triggers an integration, AnyAPI records the outcome — success or failure — so you never have to guess whether your data actually arrived. In this guide, you will learn how to read your WooCommerce API logs and fix the most common errors.
What Your WooCommerce API Logs Capture
First, it helps to understand what AnyAPI records every time an integration fires. Specifically, each log entry stores:
- First, Time — When the request fired.
- Second, Method — The HTTP method used (GET, POST, PUT, PATCH, or DELETE).
- Third, Endpoint — The full URL AnyAPI sent the request to.
- Fourth, Status — The HTTP response code, shown as a color-coded badge (2xx, 4xx, or 5xx).
- Also, Latency — How long the external API took to respond, in milliseconds.
- Finally, Response — The first 2KB of the raw response body from the receiving API.
As a result, you can diagnose most problems without leaving your WordPress dashboard.
Starter vs. Lite: What You Can See
On the Starter (free) plan, the API Log page shows a static table of your most recent 10 calls. This gives you a quick snapshot, but you cannot search, filter, or paginate through older entries.
In contrast, the Lite plan and above unlocks the full log experience:
- First, stats cards — Total calls, plus a live breakdown of 2xx, 4xx, and 5xx responses.
- Second, search — Look up a specific order ID or endpoint.
- Third, status filters — Narrow the table to only successes or only failures.
- Fourth, pagination — Browse your complete call history, not just the last 10.
- Finally, Clear All Logs — Reset the table when you are done testing.
Therefore, if you are actively debugging an integration, upgrading unlocks the tools you need to isolate the problem faster. For a full breakdown of what each plan includes, see the Feature Comparison.
Reading the Response Column
Once a request completes, AnyAPI stores the first 2KB of whatever the receiving API sent back. This is often the fastest way to understand why a call failed, because most APIs return a descriptive error message in the response body.
For example, a Slack webhook that rejects your payload might return no_text, telling you the required text field was missing. Similarly, a custom endpoint might return a validation error naming the exact field it did not recognize.
Note: AnyAPI escapes the response content before displaying it, so even if the receiving API returns raw HTML or a script tag, it renders as plain text in your dashboard — never executed.
Troubleshooting Common WooCommerce API Log Errors
If your WooCommerce order API integration is not behaving as expected, check the table below against what you see in the log.
| Symptom | Likely Cause | Solution |
|---|---|---|
| No log entry appears | Trigger does not match the order status change | Verify you selected the correct trigger for the status transition in Order API Integration |
| HTTP 401 or 403 | Invalid or missing API credentials | Check your API key in API Key Management |
| HTTP 400 | Malformed payload or missing required fields | Switch to Advanced or Expert filter mode to send only the fields your API expects — see JSON Filter Mode |
| HTTP 404 | Wrong endpoint URL | Double-check the URL for typos or trailing slashes |
| HTTP 500 | Server error on the receiving end | Contact the external service — this is not an AnyAPI issue |
| “Monthly call limit reached” | Starter plan 500 calls/month cap | Upgrade to Lite for unlimited calls, or wait until next month |
| Latency shows but Status is blank | Request timed out before a response arrived | Check whether the receiving endpoint is slow or unreachable; consider increasing your endpoint’s response speed |
Step-by-Step: Diagnosing a Failed Call
Rather than guessing, follow this sequence whenever a WooCommerce order API integration fails:
- First, open the API Log page and find the failed entry.
- Then, check the Status badge to identify whether it is a 4xx (your side) or 5xx (their side) error.
- Next, read the Response column for the exact error message the receiving API returned.
- After that, cross-reference the message against the troubleshooting table above.
- Finally, make the fix and place a fresh test order to confirm the new log entry shows a 2xx status.
In particular, if you are setting up a new integration for the first time, the Quick Start: Webhook Test guide walks through testing with webhook.site, a free tool that captures every request so you can see the raw payload before connecting a real endpoint.
Next Steps
Now that you know how to read your WooCommerce API logs, these related resources can help you go further:
- Order API Integration — Set up triggers and filters from scratch.
- API Key Management — Create and manage Basic Auth and Bearer Token credentials.
- JSON Filter Mode — Build a custom payload with Expert mode.
- For a full reference on standard HTTP status codes, see the MDN HTTP response status codes documentation.