API analytics for AdonisJS
made simple.
Gain real-time visibility into your APIs through intuitive dashboards. Just add two lines of code to your project to get started.
API usage insights: Understand how your APIs are being used in detail
Get actionable usage insights about your API, each endpoint and individual API consumers, allowing you to make informed, data-driven engineering and product decisions.
Drill down to individual requests made by consumers to facilitate customer support, aid in troubleshooting or to simply satisfy your curiousity.
API error tracking: Keep track of client and server errors returned by your API
Know exactly what kind of problems your API consumers are facing and be proactive in addressing them. Not all client errors are problematic, so Apitally helps you focus on the ones that matter.
If you also use Sentry, you can go deep on server errors as Apitally automatically links them to Sentry issues.
API performance insights: Measure user satisfaction with API performance
Use the industry-standard Apdex score to measure user satisfaction with API response times. You can set latency thresholds for the whole API and individual endpoints to account for different expectations.
Drill down to individual slow requests in the request log to help identify the root causes of performance issues.
Other benefits: Made for developers and product owners
Testimonials: What our users are saying
Easy setup: Get started in 3 simple steps
import { defineConfig } from 'apitally/adonisjs'const apitallyConfig = defineConfig({clientId: 'your-client-id',env: 'dev', // or 'prod' etc.})export default apitallyConfig
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
- Data export & API access
- 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
- Data export & API access
- 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
- Data export & API access
Prices in USD, excluding tax. Cancel anytime.
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 SDKs 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 SDKs 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:
- AdonisJS (Node.js)
- ASP.NET Core (C#)
- Django Ninja (Python)
- Django REST Framework (Python)
- Express (Node.js)
- FastAPI (Python)
- Fastify (Node.js)
- Flask (Python)
- Hono (Node.js / Bun)
- Koa (Node.js)
- Litestar (Python)
- NestJS (Node.js)
- Spring Boot (Java)
- Starlette (Python)
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 SDKs require a long-running process to aggregate and send data to the Apitally servers in the background.