API Logs

When something goes wrong between the plugin and a Mirakl operator, this page is the first place to look. Every API call the plugin makes is logged with the operator’s response, the HTTP status, how long it took, and the full payload bodies. If an offer rejects, an order fails to ship-confirm, or a product import never completes, the answer is usually in one of these rows.

Where to find it

From the Dashboard, open the Quick Start card and click the API Logs tile. This opens the API Logs page.

What you see

Columns:

Column	Meaning
Type	Which Mirakl endpoint was called (e.g. OF24 — Create/Update Offers, OR11 — Orders List).
Method	HTTP method (GET, POST, etc.).
URL	The full request URL.
Status	HTTP status code returned by the operator.
Duration (ms)	How long the call took.
Success	Yes / No — whether the call returned a non-error status.
Date	When the call was made.

Per-row action View Detail opens a page showing the full request body and full response body — the raw payload exchanged with the operator.

Filters

The sidebar has:

• Request Type — filter by the specific Mirakl endpoint. The dropdown lists named endpoints like OF24 — Create/Update Offers, OF02 — Offers Import Status, OF61 — Offer States, STO01 — Stock Import, P41 — Products Import, P42 — Products Import Status, PM11 — Product Attributes, H11 — Hierarchies (Categories), OR11 — Orders List.
• Success — show only successful (or only failed) calls.
• Connection — narrow to one Mirakl connection.

When to use this page

Failed offer sync: filter Request Type → OF24 and Success → No to see every failed offer push. The response body explains exactly what the operator rejected.

Stuck order import: filter Request Type → OR11 to verify the plugin is actually reaching the operator’s orders endpoint, and check the response for what it returned.

Performance complaints: sort by Duration descending to find the slow calls — typically heavy imports or operator-side throttling.

Verifying a new connection: the first PM11, H11 and OF61 calls after Connect Mirakl should all show Success → Yes. If any of them failed, the connection settings or API key are wrong.

Retention

API log rows are kept for the duration set by API Log Retention (days) under Mirakl → Settings → Sync Settings. Older rows are deleted by the API log cleanup scheduled task (default: every 24 hours).

Tips & gotchas

Tip

The Date column is the call time, not the response time. When chasing a specific failure, find the row by the timestamp closest to when the user noticed the issue, then open View Detail to see the full operator response.

Caution

API logs contain the full request and response payloads — including operator API keys in headers (the value is partially redacted) and customer data in order responses. Don’t paste these into public bug reports without redacting.

Note

Successful calls are also logged — not just failures. The Success → Yes filter is useful for confirming “did this actually run?” when a feature appears to do nothing.

Related

• Sync logs — higher-level plugin events (less verbose than API logs)
• Troubleshooting — common error patterns and resolutions
• API throttling — operator rate limits visible in API log durations
• Settings — set API Log Retention (days)