Easily understand your API, its usage and consumers
Get actionable usage and performance insights about your API, each endpoint and individual API consumers, allowing you to make informed, data-driven engineering and product decisions. API monitoring was never this easy.
- Traffic: Track number of requests over time, per endpoint and per consumer
- Errors: Monitor client & server errors, understand impact and root causes
- Response times: Understand the performance of each endpoint, identify bottlenecks
- Payload sizes: Keep track of request & response sizes and total data transferred
Log, find and inspect each request and response
Drill down from insights to individual requests or use powerful filtering to understand exactly how consumers have interacted with your API. Take troubleshooting and customer support for your API to the next level.
Our privacy features let you control what is and what isn't being logged so you can keep sensitive data protected with ease.
Be the first to know if there are problems with your API
Set up custom alert rules and benefit from built-in API uptime checks to get notified immediately if there is a problem, so you can address it before it impacts consumers.
- Custom alerts: Configure thresholds for 14 different traffic, error and performance metrics and get notified when they are breached.
- Liveness checks: Get notified when your application stops sending regular heartbeats to our servers in 1-minute intervals.
- Health checks: Get notified when your API stops responding to HTTP GET requests that we send to a specified endpoint in 1-minute intervals.
Made for developers and product owners
Choose the right plan for you
You can start out on the free plan to see if Apitally meets your needs and then upgrade at any time without commitment.
- 1 connected app
- 1 dashboard user
- 3 active app instances
- 10 API consumers
- 1 custom alert
- API health checks
- Slack & Teams integration
- Priority support
- 3 connected apps
- 3 dashboard users
- 10 active app instances
- 50 API consumers
- 10 custom alerts
- API health checks
- Slack & Teams integration
- Priority support
- 10 connected apps
- Unlimited dashboard users
- 50 active app instances
- Unlimited API consumers
- Unlimited custom alerts
- API health checks
- Slack & Teams integration
- Priority support
Prices in USD, excluding tax. Cancel anytime.
Get started in 3 simple steps
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 features, the Apitally client libraries only collect non-sensitive metadata about your API endpoints as well as requests and responses. This includes HTTP methods, paths, response status codes, timing and the size of the request and response bodies. Request and response headers and bodies are not collected.
Once released, our API request log feature will allow you to configure every aspect of what is being logged and will also make it easy to mask sensitive fields.
For our API analytics features there is no limit on the number of API requests, so we don't mind if your API handles millions of requests. This is because these features work on aggregated request data.
However, once released, our API request log feature will have limits.
We retain aggregated API analytics data for 1 year, allowing you to analyze long-term trends in API usage, errors and performance in Apitally.
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)
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.
Hey 👋🏼, I'm Simon Gurcke, a software engineer from Germany, and Apitally is my indie product.
I've been building web apps and APIs for many years, as an individual developer and in small teams.
In the past I've often found myself reinventing the wheel or having to host extra tools for monitoring my APIs. I believe it should be simpler, not get in the way of creating value for users and not break the bank.
That's why I'm building Apitally. I hope you'll enjoy using it as much as I do.