Observability
Two tabs in your dashboard, both fed from the public API:
Request log
Section titled “Request log”GET /v2/logs/requests?limit=50Returns every /v2/* call your partner key made in the last 30 days
(method, path, status code, latency, error code, request_id). Filter
with method, path_prefix, status_min, status_max.
Inspect a single call:
GET /v2/logs/requests/{request_id}The request_id is the value of the swft-request-id response header
on every API call.
Webhook deliveries
Section titled “Webhook deliveries”GET /v2/webhooks/deliveries?status=failed&limit=50Lists every delivery Swft attempted to your endpoint. Inspect bodies and replay individual rows — see the webhooks guide.
Tracing
Section titled “Tracing”Every Swft response carries a W3C traceparent header. If you’re
running OpenTelemetry on your side, ingest that header on inbound
webhooks to correlate spans end-to-end.
Audit log
Section titled “Audit log”Every mutating action — merchant.created, partner_key.revoked,
webhook_delivery.replayed, etc. — is recorded in the workspace audit
log. Today the audit log is exposed only in the dashboard UI; an
unauthenticated read endpoint is planned for a future date version.
Rate limits
Section titled “Rate limits”Every response carries:
X-RateLimit-Limit: 5000X-RateLimit-Remaining: 4998429 responses include meta.retry_after in seconds.