Question 1

What data does PeekAPI collect?

Accepted Answer

HTTP metadata only: method, path, status code, response time, request/response size, and a consumer identifier. We never capture request or response bodies, query parameters (unless you opt in), or raw headers.

Question 2

How do you handle credentials?

Accepted Answer

Authorization headers (Bearer tokens, Basic auth) are SHA-256 hashed inside the SDK before leaving your server. We never see or store actual credentials. API keys used as consumer IDs are stored as-is since they're the consumer's own public identifier.

Question 3

Does it affect my API performance?

Accepted Answer

No. The middleware captures timing and metadata synchronously (microseconds), then buffers the event in memory. The HTTP call to our ingest endpoint happens asynchronously in a background thread. Your API response time is not affected.

Question 4

What happens if your service goes down?

Accepted Answer

Your API continues to work normally. The SDK buffers events in memory, retries with exponential backoff, and persists undelivered events to disk on shutdown. On next startup, events are recovered and retried. No data is lost.

Question 5

Why zero dependencies?

Accepted Answer

Supply chain security. Every dependency is an attack surface. Our SDKs use only the standard library of each language — no transitive dependency tree, no risk of a compromised package, minimal binary size, and no version conflicts.

Question 6

Can I use this with serverless?

Accepted Answer

Yes, with a small adjustment. Serverless functions (Lambda, Cloud Functions, edge handlers) can't run background timers, so you need to call flush() at the end of each invocation to send buffered events before the function freezes. Set batchSize to 1 for per-request flushing if latency allows. For Cloudflare Workers, a Logpush-based integration is on the roadmap that avoids any in-request overhead entirely.

Question 7

What happens when I hit my plan limit?

Accepted Answer

When your monthly event quota is reached, new events are rejected at the ingest layer — your API keeps working normally, you just stop collecting new analytics data until the next billing cycle. You'll see a usage warning in the dashboard before hitting the limit. Upgrade anytime to increase your quota.

Question 8

How long do you retain my data?

Accepted Answer

It depends on your plan: Free retains 14 days, Pro 30 days, Business 90 days, and Enterprise up to 365 days. Aggregated stats (request counts, error rates, response times) are kept for the full retention window. When data ages out, it's permanently deleted.

Question 9

Which languages and frameworks do you support?

Accepted Answer

We have official SDKs for Node.js (Express, Fastify, Koa, Hapi, NestJS), Python (FastAPI, Django, Flask), Go (net/http, Gin, Echo, Fiber, Chi), Ruby (Rails, Sinatra), Rust (Actix Web, Axum, Rocket), PHP (Laravel, Slim), Java (Spring Boot, Servlet), and Dart (Shelf). All SDKs are open source with zero dependencies.

API analytics that just work

What you get

Real-time Analytics

Multi-SDK Support

Zero Dependencies

Smart Alerts

Consumer Tracking

Secure by Default

Add analytics in one line of code

Pricing

Frequently asked questions