Simple & Transparent Pricing Plans To Reduce Development Hours
Choose the plan that fits your team's needs, with no hidden fees and all the features you need to succeed.
.svg){kind=icon}
Personal
Great for monitoring and debugging in development or low traffic applications
.svg){kind=icon}
.svg){kind=icon}
Team
Monitor, debug, and integrate production-level applications.
.svg){kind=icon}
Business
Best for higher-volume applications that require many integrations.
Frequently Asked Questions
What is the difference between an API request and a Workflow run?
After adding one of the ApiTraffic SDKs to your API, every request that comes into your system will automatically also be ingested into ApiTraffic. Each of these requests are considered an "API Request". Keep in mind you can exclude requests that don't need to be logged, for example health check requests.
Rules can be setup to trigger a workflow from matching API Requests, each time the workflow is triggered, that is considered a workflow run. Workflows can have multiple steps, branches, and connections - no matter the configuration of the flow each time it is invoked it is only counted as one run.
What is an Environment?
Most engineering teams' SDLC involves multiple environments such as development, staging, quality assurance, and production. ApiTraffic enables API data segmentation by environment, ensuring your data aligns with your API deployments.
What is a Bucket?
Buckets are versatile containers that support additional data segmentation, such as by project, deployment region, or other criteria. There are no strict guidelines for using buckets, allowing each customer to segment their data as needed.
What is a Stream View?
Stream Views return API requests that match a predefined saved search criteria. Any search or filter can be saved as a stream view for convenient access later. Stream Views are also linked to Workflows, ensuring that workflows are triggered only by requests that meet specific criteria.
Do you offer discounts for annual plans?
Yes, when signing up an annual plan option will be available. These plans offer 2-months of free service.
What happens if I reach my plan's request limit?
Don't worry; if you exceed your plan usage limit, your traffic will continue to flow. You will simply be billed for your overage usage during your next bill. All plans bill overages at a rate of $.50 per 1k request batch.
For example, if your usage exceeds your plan limit by 10 requests, you will be charged an extra $.50 on your next bill.
We know you don't like surprises, so we will notify you when you are approaching your plan limit.
How is pricing calculated?
A request includes any ingested, captured, or relayed API request. A workflow includes any triggered workflow regardless if the workflow completes successfully or not. API requests can be excluded/filtered to aid in reducing unnecessary logging and costs.