Integration logs
Every inbound request — success or failure — is recorded.
Open Settings → Integrations → Partners → {partner} → Logs in the dashboard.
What a log entry captures
| Field | What's in it |
|---|---|
| Timestamp | When the platform received the request |
| Partner | The linked integration partner (empty for pass-through keys) |
| API key | The calling key's name (always set) |
| Resource + action | order/create, inventory/create, product/read, … |
| Identifier | The URL identifier (if any) |
| HTTP method/path | The exact request line |
| Raw payload | What you sent, untouched |
| Mapped payload | After field mapping — what validation saw |
| Response | What the platform returned |
| Status | success, validation_error, mapping_error, service_error, not_found |
| Error message | For non-success statuses |
| Internal ID | UUID of the created/updated record |
When to use logs
- Before contacting support. The raw vs. mapped payload pair answers most mapping questions on the spot.
- Verifying a rotation. After swapping keys, check that the latest entries use the new key's name.
- Diagnosing a 400. The mapped payload shows what the validator actually saw — usually the mapping is at fault, not the external system.
- Diff testing a mapping change. Disable the old mapping, enable the new one, resend, compare.
Retention
Logs are retained for 90 days. If you need longer retention for compliance, contact your account owner.
What logs do not contain
- The API key string. Only the key's name is recorded.
- Authentication-layer rejections (
401,403) — those happen before the request reaches the integration engine. For those, check the dashboard's Security → API key activity view.