Understand every aspect of your API and its 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.
- Traffic: Track number of requests over time, per endpoint and per consumer
- Errors: Monitor client & server errors, understand impact and root cause
- Performance: Analyze the response times of each endpoint, identify bottlenecks
- Consumers: Understand how individual consumers are using your API
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.
Request logging is optional and works independently of our metrics & insights features.
Know about API problems the moment they happen
Get notified immediately if something isn't right, so you can address it before it impacts consumers. Whether it's downtime, traffic spikes, errors or performance issues, Apitally has you covered.
- 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.
- Health checks: Get notified when your API stops responding to HTTP GET requests that we send to a specified endpoint in regular 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 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 (500k 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.
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 metrics & insights 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 analyzed using our metrics & insights features, which work on aggregated data.
However, there are limits on the number of logged API requests, as outlined in the pricing table above.
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.
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.
I use Apitally myself every day and derive huge value from it. I hope you'll enjoy using it as much as I do.