Welcome to ApiTraffic

ApiTraffic records every API request with its payload, latency breakdown and firewall verdict. Start here to install the SDK, explore and connect agents.

This page as Markdown

ApiTraffic records every request your API serves as one record: the request and response with their headers and bodies, how long it took and where the time went, the outbound calls it made, and the firewall’s verdict on it. One middleware in your Node application does all of it, and everything it records is searchable in seconds.

What you get

  • Request logging. Every inbound request and every outbound call your app makes while serving it, with headers and bodies, searchable by any field.
  • Performance monitoring (APM). The database queries, cache calls, queue operations and outbound requests inside each request, on a waterfall that names the line of code behind the slow query.
  • A firewall inside your app. Each request is screened in your own process and carries its verdict, so you can see what was blocked and why, and start in Monitor mode before you block anything.
  • Change and drift tracking. Deploy and incident markers on your charts, and alerts when an endpoint’s response shape, status codes or latency drift from their baseline.
  • Data controls. Redaction that runs inside your process before anything is sent, and exclusions that keep whole routes out.
  • Answers for AI agents. An MCP server lets Claude, Cursor and other agents search your real traffic, read a failing request and the code that ran, and propose a fix.

ApiTraffic is built for teams that run APIs on Node.js (Express, Fastify, Koa, hapi or Strapi): the engineers who debug them, the people on call for them, and the security and platform teams responsible for what they expose.

Start here

  • Quickstart: Sign up, install @apitraffic/node and see your own requests in about five minutes.

  • Explore the sample data: Click through every feature on a live demo API before you install anything.

  • How ApiTraffic works: Buckets, environments, requests, spans, verdicts, redaction and tokens.

Explore the docs

How the docs are organized

The Guides tab follows the order most teams adopt ApiTraffic in:

  1. Get started: this page, the Quickstart, core concepts and the sample data.
  2. Connect your app: one guide per framework, plus every SDK option.
  3. Explore traffic, Performance and Security and data controls: using the product day to day.
  4. Collaborate and automate and AI and integrations: sharing, workflows, agents and connected tools.
  5. Account and administration: settings that owners and admins manage.
  6. Reference: troubleshooting, FAQ, metric definitions and SDK behavior in edge cases.

The API reference tab documents the REST API for scripts and integrations.

For AI agents and LLMs

These docs are published in machine-readable forms, so your coding agent can read them directly:

Format Where
Index of every page, with descriptions (llmstxt.org format) /llms.txt
The complete docs in one Markdown file /llms-full.txt
Any single page as Markdown Add .md to its URL, for example /docs/quickstart.md
Search from inside an agent The ApiTraffic MCP server’s search_docs, get_doc_page and list_doc_pages tools

Connect your agent to the MCP server at https://api.apitraffic.io/mcp and it can search these docs alongside your own traffic. See MCP server.

Get help