Skip to content

Platform API Logs ​


Table of Contents ​


Section 1: Use Cases ​

Quick Links: Find out why orders didn't come in | Find out why label generation failed

Scenario 1: A platform's orders seem to be missing and you suspect an integration error ​

Situation: Customer service reports a Shopee order that can't be found in the system, or platform stock figures don't match the system. You suspect a fetch or stock push didn't succeed, but aren't sure which one or what went wrong.

How to Do It: Under "Platform" → "Platform API Logs", filter by date range plus "EC Integration" to narrow to that account's calls, then check the "Status" column for the failed one (see Expand to View Request & Response).

Result: You can pinpoint exactly which fetch or push failed and what the platform reported, judging whether it's an expired credential, a platform-side error, or a product-mapping issue, then go back to the account to fix it.


Scenario 2: A shipping label keeps failing and you want to see what the carrier said ​

Situation: A shipment's tracking number isn't generating, and the label status shows failed. You need to know whether it's an address issue, a contract credential issue, or a carrier-side error at the moment.

How to Do It: Filter by "Shipping Integration" to narrow to that account's calls, find the failed label-generation record, and expand it to see the error the carrier returned.

Result: You see the carrier's specific error message directly, skipping guesswork, and can quickly judge whether to add an address, change credentials, or retry later.


Section 2: Features ​

Platform API Logs record every integration call the system makes on your behalf to e-commerce and logistics platforms — order fetching, stock push, product mapping sync, label generation, tracking lookups, platform-initiated notifications (webhooks), and more. Each entry keeps the request and response content, the response status, and the processing time. Apart from reprocessing platform webhooks, this is a read-only audit log, and when orders or stock look wrong, it's the first stop for figuring out "whether the integration failed, and where".

Platform API Logs - Page Overview

Quick Jump: Search & Filter | List Columns | Expand to View Request & Response | Reprocess Platform Webhooks

The volume is large, so use filters to locate things fast:

FilterPurpose
Created AtThe expanded-by-default date range; first narrow to the period in question
ActionShow only a specific action (e.g. only fetching or only stock push)
EC IntegrationShow only one EC account's calls
Shipping IntegrationShow only one shipping account's calls

2.2 List Columns ​

ColumnDescription
Created AtWhen this call occurred; click it to open that entry's detail page
ActionWhat this call did (fetch, stock push, label generation, tracking, etc.)
MethodThe request method
SourceThe object this call relates to (EC account, order, merchant, shipment, etc.)
PathThe request path
StatusThe response status: green for success, orange for a bad request, red for a platform-side error
DurationHow long this call took

To judge success or failure, the fastest check is the color of "Status": green is success, while orange or red are the ones to expand and inspect.

2.3 Expand to View Request & Response ​

Click any entry to expand the full "Request Body" and "Response Body" content of that call. For failed calls, the platform's error reason is right there in the response — the most critical information for pinpointing the root cause of a failure.

2.4 Reprocess Platform Webhooks ​

Platform API Logs - Reprocess on the webhook log detail page

The system first stores each notification a platform sends (action "Webhook") and then processes it in the background. For an entry whose processing keeps failing, or that was received but not processed, you can click "Reprocess" on its detail page to have the system process the notification again from its original content — for example, syncing an order cancellation, re-fetching an order, or updating a shipment's status. Clicking the entry's "Created At" in the list, or clicking a "webhook processing failed" notification, takes you to that entry's detail page.

ItemDetails
Who can click itUsers with edit permission on EC accounts; users with view-only permission see the button locked, and hovering over it shows the missing permission
Which entries have the buttonEntries that still failed after all automatic retries (response shows inbox_status: failed) and entries received but not processed (response shows a reason); entries being processed, being retried, or already succeeded don't, and neither do entries whose EC account was disconnected (ec_account_disconnected)
After you clickOnce confirmed, the entry is queued again and the button disappears; refresh in a moment to see the result. Success turns it green; if it errors again, it is retried automatically 6 times as usual
Audit logEvery reprocess records who reprocessed which webhook and when, under the action "Reprocess platform webhook"

For an entry that was received but not processed, the cause is usually in the notification itself (for example, a missing order number), so clicking right away usually gives the same result. It's meant for after the platform or the system has been fixed, to bring back events that only arrive through webhooks (such as a completed return). Logs are cleared after about 2 months, after which an entry can no longer be reprocessed.


Section 3: FAQ ​

Quick Jump: FAQ | Notes

3.1 FAQ ​

▪ What integration actions are recorded here? ​

Both e-commerce and logistics: on the e-commerce side, fetching orders, fetching store settings, product mapping sync, stock push, etc.; on the logistics side, generating tracking labels, querying delivery status, reporting shipping status, etc.; plus platform-initiated notifications.


▪ How do I quickly find failed calls? ​

First narrow with the date range, then check the color in the "Status" column — orange or red is abnormal. To target a specific account, add the "EC Integration" or "Shipping Integration" filter.


▪ What's the difference between orange and red status? ​

Orange means the request itself had a problem (e.g. wrong credentials, mismatched parameters — usually a setup or data issue); red means a platform-side error occurred (e.g. the platform system was down at the moment). Orange usually requires a fix on your side; red can often just be retried later.


▪ A notification the platform sent us shows 200, so why is it red too? ​

The system stores each notification first, replies 200 to the platform, and then processes it in the background, so a new entry starts out green and only shows the processing result after you refresh a moment later. After that, there are five kinds of red; expand the row and check the response to tell them apart:

ResponseMeaning
reasonReceived but not processed — for example, the notification had no order number or was missing required fields, was an event type the system doesn't handle, wasn't in a readable format, or reported an error from the platform
reason: ec_account_disconnectedThe EC account was disconnected by the time the notification was processed, so it wasn't processed and can't be reprocessed. Reconnect the account first by following the red prompt at the top of its Detail page
reason: fetch_orders_disabled"Fetch Orders" is off for this EC account, so order and return notifications other than cancellations and buyer cancellation requests (new orders, status changes, returns) are not processed; cancellations and cancellation requests are still applied and show green. Order notifications from Shopline, Free Store and Liteshop and cancellation-request notifications from BVSHOP trigger one lookup on the platform when they match an order that has not shipped yet, applying only a cancellation or cancellation request; those show green with no reprocessing, and a failed lookup is retried automatically. After turning order fetching back on, you can reprocess the entries you need; the switch is on the EC account Edit page
inbox_status: retryingProcessing ran into an error and the system is retrying automatically; attempts is the number of tries so far. It turns green once a retry succeeds
inbox_status: failedStill failed after 6 automatic tries (about 10 hours); the system has sent a notification, and you can reprocess it

If the same reason keeps coming back, the platform has usually changed its notification format, or your platform admin is subscribed to events the system doesn't handle; you can send the record's time and response to the warehouse or customer support to help sort it out.


▪ Can I re-trigger a failed call from this page? ​

For notifications the platform sent us, yes: for an entry that failed or was received but not processed, open its detail page and click "Reprocess" — see Reprocess Platform Webhooks. Calls the system made itself can't be resent here: to re-fetch orders, go to the corresponding EC account's Detail page and use "Fetch Orders Now"; to regenerate a label, follow the shipping process.


▪ I got a "webhook processing failed" notification. What should I do? ​

It means a platform notification still wasn't processed after 6 automatic tries. Click the notification to open that entry's detail page and check the error in the response; if it was caused by a temporary platform or network problem, just click "Reprocess". You only get the first such notification per EC account within 6 hours; later failures are still shown in red in the list and can be reprocessed the same way.


▪ What does a "webhook subscription repaired" notification mean? ​

Every early morning the system checks each EC account's notification settings on the platform. This notification means the setting on the platform had been disabled or removed (for example, the platform disabled it automatically after repeated delivery failures), and the system has re-enabled or recreated it automatically, so notifications will arrive as usual from now on. While it was disabled the platform sent no notifications: new orders and cancellations are picked up by scheduled order fetching, but statuses that only update through notifications (such as Shopify full refunds or WooCommerce refunds) are not, so please check that period's orders in the platform admin. A WooCommerce webhook you paused yourself (Paused) in the WooCommerce admin is not switched back automatically.


▪ What if I can't understand the response after expanding? ​

The response is the data the platform returned as-is; focus on the error description within it. If you still can't tell, provide the entry's time, action, and response content to your warehouse or customer service for help.


▪ I can't find a certain action in the options? ​

The "Action" filter only lists actions that are written to the log. A few actions that only appear on failure notifications and aren't persisted won't appear in the options, which is normal.

3.2 Notes ​

⚠️ Important ​

  • Apart from reprocessing platform webhooks, you cannot retry or modify any integration call here
  • The root cause of a failure is the platform's message in the response content — don't conclude from the status color alone

💡 Tip: When troubleshooting, first lock the time with the date range, then narrow by account and action step by step — far faster than scrolling entry by entry.


FeatureDescriptionLink
EC IntegrationsEC accounts' connection status and fetch/push settingsGo
Shipping IntegrationsShipping accounts' contract credentials and enable settingsGo
Shipment ListView tracking numbers and delivery statusGo

Last updated 2026-11-16 19:57