Skip to main content
Why it matters When something breaks, you need answers fast. The Developer Console gives engineers searchable logs, message timelines, and safe replay tools — reducing MTTR and support tickets. How it works
  • Search: Find by email, sendId, or provider messageId
  • Timeline: Unified view of send → message → events
  • Webhooks: Inspect delivery to your endpoints and re‑send
  • Replay: Re‑attempt failed sends to test inboxes after fixes
  • Idempotency: Replay maintains idempotent semantics to avoid duplicates
Benefits
  • Diagnose issues in minutes instead of waiting on support
  • Improve developer velocity during integration and QA
  • Lower support burden with self‑service insights
Best practices
  • Use sendId as your primary key when debugging.
  • Inspect provider messageId when correlating with vendor logs.
Success metrics
  • MTTR reduction for send failures
  • % of issues resolved without support intervention
Related APIs
  • Timeline: GET /api/v1/sends/{id}
  • Provider events: managed by Fluxomail (see Provider Events)