Request logging for REST APIs
with privacy built-in.
Find and inspect any API request by drilling down from analytics dashboards or through powerful filtering options. Configure exactly what is logged to meet your requirements.
Discover & investigate: Drill down from API metrics to individual logged requests
Apitally bridges the gap between aggregated API metrics and request-level debugging. If you spot anomalies in your metrics, you can drill down to the relevant requests and understand exactly what happened.
The request log includes the full URL, headers and payloads of requests and responses (subject to configuration), helping you investigate and resolve issues faster.
Search & filter: Find and inspect any logged API request with ease
Pinpoint exactly what you're looking for with comprehensive search and filtering options, including by consumer, endpoint, status code, response times and more.
An interactive timeline graph allows you to easily zoom into specific periods during incident investigations.
Performance & privacy: Built for production with complete privacy control
Our client libraries handle logging asynchronously with negligible impact on the performance of your API. Log data is compressed and buffered to disk before being sent to Apitally in the background.
Flexible configuration options let you control exactly what gets logged. Mask sensitive data, exclude specific paths, and implement custom rules. All aspects of logging are opt-in by default.
Other benefits: Made for developers and product owners
Pricing: Choose the right plan for you
You can sign up without a credit card using our free plan and then upgrade at any time without commitment.
- 1 app
- 1 dashboard user
- 3 active app instances
- 10 API consumers
- 1 custom alert
- Request log
- Health checks
- Slack & Teams integration
- 3 apps
- 3 dashboard users
- 10 active app instances
- 100 API consumers
- 10 custom alerts
- Request log (1m req/mo)
- Health checks
- Slack & Teams integration
- 10 apps
- Unlimited dashboard users
- 50 active app instances
- Unlimited API consumers
- Unlimited custom alerts
- Request log (5m req/mo)
- Health checks
- Slack & Teams integration
Prices in USD, excluding tax. Cancel anytime.
Easy setup: Get started in 3 simple steps
from fastapi import FastAPIfrom apitally.fastapi import ApitallyMiddlewareapp = FastAPI()app.add_middleware(ApitallyMiddleware,client_id="your-client-id",env="prod", # or "dev")
Frequently asked questions: Learn more before you dive in
Can't find the answer you're looking for? Reach out via email or on Slack and we'll get back to you as soon as we can.
For our API analytics and monitoring features, the Apitally client libraries only collect non-sensitive metadata about your endpoints, requests and responses. This includes HTTP methods, paths, response status codes, timing and the size of the request and response bodies. Data is aggregated on the client-side before being sent to the Apitally servers.
For API request logging, our client libraries allow you to configure every aspect of what is being logged and also make it easy to mask sensitive fields.
There is no limit on the number of API requests that can be processed for our API monitoring and analytics features, which work on aggregated data.
However, there are limits on the number of logged API requests, as outlined in the pricing table.
We retain aggregated API metrics for 1 year, allowing you to analyze long-term trends in API usage, errors and performance in Apitally.
Logged requests are retained for 15 days.
Apitally currently supports the following web frameworks for Python and Node.js:
- FastAPI (Python)
- Flask (Python)
- Django Ninja (Python)
- Django REST Framework (Python)
- Starlette (Python)
- Litestar (Python)
- Express (Node.js)
- NestJS (Node.js)
- Fastify (Node.js)
- Koa (Node.js)
- Hono (Node.js / Bun)
Support for more frameworks may be added based on feedback from the community. Please let us know if you're interested in using Apitally with a framework that is currently not supported.
No, Apitally currently doesn't work in event-driven serverless deployments, such as on AWS Lambda or Cloudflare Workers. This is because the Apitally client libraries require a long-running process to aggregate and send data to the Apitally servers in the background.