About Apitally: Frequently asked questions

Apitally is an API monitoring and analytics tool built for small engineering teams. It gives you API metrics, request logs, traces and alerts in simple, ready-made dashboards.

With Apitally, you can track API traffic, errors and response times, understand how individual consumers use your API, inspect individual requests and responses, and get notified when your API is down or a metric crosses a threshold.

You add Apitally to your application with an open-source SDK and a few lines of code, without any infrastructure changes. It supports popular web frameworks for Python, JavaScript, Go and .NET.

Apitally offers a CLI and agent skill that give AI agents like Claude Code, Cursor, and Codex full access to your API metrics and request logs. We chose this approach over MCP because it's more token-efficient and reliable, while giving agents richer investigation capabilities.

Read more about it in our blog post.

Yes. The Apitally API lets you access request logs and traffic metrics for your apps programmatically, for example to export data for analysis or to integrate Apitally with your own systems. It's available on all plans, and you can manage API keys under Settings > API keys in the dashboard.

The API also powers the Apitally CLI, which you can use from your terminal or give to coding agents.

Apitally sends alert notifications by email, and can also send them to Slack or Microsoft Teams on the Starter and Premium plans. On the Premium plan, you can connect incident.io for on-call escalation and incident response. You can set up integrations under Settings > Integrations in the dashboard.

If your application uses Sentry, Apitally links server errors to the corresponding Sentry issues, so you can quickly find the root cause.

Apitally currently supports the following web frameworks:

• AdonisJS (Node.js)
• ASP.NET Core (C#)
• BlackSheep (Python)
• Chi (Go)
• Django Ninja (Python)
• Django REST Framework (Python)
• Echo (Go)
• Elysia (Bun)
• Express (Node.js)
• FastAPI (Python)
• Fastify (Node.js)
• Fiber (Go)
• Flask (Python)
• Gin (Go)
• H3 (Node.js / Deno / Bun)
• hapi (Node.js)
• Hono (Node.js / Bun)
• Koa (Node.js)
• Litestar (Python)
• NestJS (Node.js)
• Starlette (Python)

Please let us know if you're interested in using Apitally with a framework that is currently not supported.

Apitally supports Cloudflare Workers via a Logpush integration and our Serverless SDKs. These currently support Hono and FastAPI.

You can find more details in our setup guide for Cloudflare Workers.

Support for other serverless platforms may be added in the future based on user demand.

Yes. The Apitally SDKs for Python, JavaScript, Go and .NET are built on OpenTelemetry and send metrics, logs and traces to Apitally using OTLP, without requiring a separate collector or agent. If your application already uses OpenTelemetry, the SDK works alongside your existing setup, and you can use standard OpenTelemetry instrumentation libraries to add spans to your traces.

Apitally's dashboards rely on data that only the Apitally SDKs send, such as the endpoints discovered in your application and request metrics aggregated by endpoint, status code and consumer. Sending data to Apitally from other OpenTelemetry SDKs or an OpenTelemetry Collector is therefore not supported.

The SDKs are designed to keep overhead low. In our benchmarks, they added less than 1 ms to response times on average, even with request and response bodies captured.

The SDKs aggregate request metrics in memory and send collected data to Apitally in the background, separately from request handling, normally about once a minute.

For API metrics, the Apitally SDKs record the method, path, status code, response time and payload sizes of each request, and combine them into counts and histograms within your application before sending them to Apitally. Aggregated metrics are retained for 13 months.

Request logs capture the details of individual requests, such as the URL, client IP address, user agent, response headers and response time, along with related application logs and traces. Request headers and request and response bodies are only captured if you enable them. Request logs, application logs and traces are retained for 15 days, with longer retention available on request.

Read more about data collection and retention in our docs.

The Apitally SDKs mask sensitive query parameters, headers and body fields, such as passwords, tokens and API keys, by default. You can add your own masking rules and exclude requests from logging. Masking and filtering happen within your application, before any data is sent to Apitally.

Request headers and request and response bodies are only captured if you enable them. Because the SDKs are open-source, you can verify exactly what data they collect.

Data is sent to Apitally over HTTPS and is encrypted at rest. Read more about our privacy controls in our docs.

Apitally currently doesn't hold certifications like SOC 2 or ISO 27001, and is not HIPAA compliant. Our privacy policy includes disclosures for the GDPR and UK GDPR.

Please reach out if you need help documenting Apitally as a vendor for your own compliance requirements.

Apitally stores data in a ClickHouse database hosted on DigitalOcean in the US. The underlying storage is encrypted at rest.

Database backups are created hourly, stored in an encrypted private storage bucket and kept for 7 days.

Apitally is currently only available as a cloud service, hosted and maintained by us. If you're interested in a self-hosted version, please get in touch.

You can try Apitally free for 14 days, and no credit card is required at sign up. After the trial, you can choose one of our paid plans to keep using Apitally. There's no free plan.

Prices are in US dollars (USD) by default, with local pricing in euros (EUR) for Europe, British pounds (GBP) for the UK and Indian rupees (INR) for India. Our pricing page shows prices in your local currency automatically, and you can switch currencies there.

Prices exclude tax, which is calculated at checkout based on your location.

An API consumer is a unique consumer identifier that your API has handled requests for, such as a user ID, email address or API key name. The API consumer limit of each plan is based on the number of unique consumers within a rolling 24-hour window.

This limit only applies if your application identifies consumers for Apitally, which lets you track API usage by individual consumers. The setup guide for your framework explains how to do this.

If you exceed the API consumer limit for your plan, you'll be notified and given a 7-day grace period. During this time, you can either upgrade to a higher plan or reduce usage to stay within limits. If you're still over the limit after the grace period, Apitally will stop ingesting data from your apps. Your dashboard and historical data remain accessible.

If you exceed your monthly quota for request logs, Apitally will stop ingesting new requests until the quota resets at the start of the next month. This won't affect your API metrics. The same applies to application logs and traces.

On the Starter and Premium plans, you can enable usage-based billing at any time under Settings > Billing in the dashboard. It's off by default. If enabled, ingestion continues beyond your monthly quotas, and you're charged for the extra usage at the overage rates shown on our pricing page.

Yes. You can upgrade, downgrade or cancel your plan at any time under Settings > Billing in the dashboard. To downgrade, your usage must be within the limits of the lower plan.

If you cancel, your plan stays active until the end of the current billing period. After that, or when your trial ends without a subscription, Apitally stops ingesting data from your apps and the dashboard is no longer accessible.

Your existing data isn't deleted straight away. It expires according to the usual retention periods, and if you subscribe again within that time, you'll have access to it again. You can also delete your apps or team at any time to remove their data immediately.