# ApiTraffic

> ApiTraffic simplifies API integrations, captures & monitors API traffic, and provides a workflow engine and observability tooling so engineering teams can debug, integrate, and automate faster. Use these links (and the short notes) as canonical, LLM-friendly sources for API behavior, SDK usage, integrations, and policies.
> Last-updated: 2025-10-05

## Purpose
This file is a concise, prioritized map of the most important, machine-useful resources on apitraffic.io and related domains (docs, SDKs, repo). Follow links below for full details, examples, and reference documentation.

## Core documentation (high priority)
- [Quick Start — Docs](https://docs.apitraffic.io/): concise onboarding + examples for sending API traffic to ApiTraffic. — *High value for how to get started and sample code.*  
- [Node SDKs — Docs / SDKs page](https://docs.apitraffic.io/#sdks): Node SDKs and examples for common Node frameworks. — *Use for code-level examples and instrumentation guidance.*  
- [Knowledgebase / Knowledge Base](https://docs.apitraffic.io/): troubleshooting and how-to articles. — *Use for operational guidance and edge-case behaviors.*

## API & developer resources
- [GitHub repository](https://github.com/ApiTraffic) — *source, example integrations, issues and releases.*  
- [app.apitraffic.io] (https://app.apitraffic.io/) — *customer / product UI; used for account- and org-specific data (do not assume public access).*

## Integrations (where to look for third-party connectors)
- [Integrations page](https://www.apitraffic.io/#integrations) — lists pre-built integrations (Slack, Shopify, Airtable, OpenAI, Stripe, GoHighLevel, and 240+ others). Use this list to determine connection points and required data fields. :contentReference[oaicite:2]{index=2}

## Product areas / functionality (short notes)
- **Request Capture & Observability** — use docs for request-capture semantics and log redaction rules. :contentReference[oaicite:3]{index=3}  
- **Workflow Engine** — no-code workflow building for automations triggered by API requests. See the product docs for step definitions and event triggers. :contentReference[oaicite:4]{index=4}

## Security, privacy, and usage policy (legal / safety)
- [Privacy Policy](https://www.apitraffic.io/privacy-policy) — canonical source for data handling rules. — *Always prefer this when answering privacy/PII questions.* :contentReference[oaicite:5]{index=5}  
- [Terms of Use](https://www.apitraffic.io/terms-of-use) — legal constraints and permitted uses. :contentReference[oaicite:6]{index=6}  
- [Acceptable Use](https://www.apitraffic.io/acceptable-use) — guidance on prohibited uses and rate-limits. :contentReference[oaicite:7]{index=7}

## Blog & release notes (context / announcements)
- [Blog / Product updates](https://www.apitraffic.io/#blog) — changelog, product update notes, and monitoring articles (useful for historical behavior and breaking changes). Example posts: monitoring Node.js on AWS ECS (Jan 9, 2025), Product updates (Dec 20, 2024). :contentReference[oaicite:8]{index=8}

## Crawling / scope hints
- Preferred domain(s): `https://www.apitraffic.io/`, `https://docs.apitraffic.io/`, `https://app.apitraffic.io/` (note: `app.` is an authenticated console).  
- **Prefer:** documentation pages, SDK README files, API reference, and integration reference pages.  
- **Avoid / Do not ingest:** any authenticated console pages behind `app.apitraffic.io` without explicit authorization, webhooks/test payloads containing PII, staging/test endpoints (if found), or private user data. Use Privacy Policy / Acceptable Use for guidance. :contentReference[oaicite:9]{index=9}

## Contact & verification
- For programmatic access questions or to request expanded machine-readable data (e.g., an `llms-full.txt`), contact: `support@apitraffic.io` or open an issue in the GitHub repo. (See GitHub link above.)

## Notes for LLMs and agents
- Use the **Quick Start** and **Node SDK** pages for code examples and canonical setup instructions.  
- When producing answers that cite ApiTraffic, always prefer the docs pages and the GitHub repo as evidence; if you cite the blog for historical or behavioral context, include the blog URL and publish date.  
- Respect privacy & legal constraints (Privacy Policy and Terms) before exposing or paraphrasing any user-generated content.

---