QuotaWatch for Jira : API Activity
The API Activity page helps you understand who is consuming your Jira Cloud API quota and what activities are contributing to API usage.
While the Overview page tells you that API usage is increasing, the API Activity page helps you determine why.
Use this page to identify heavy API consumers, distinguish between user-driven activity and automated traffic, and understand which projects or actions are generating the most API requests.
This page is especially useful when API usage increases unexpectedly or when you receive API usage alerts from QuotaWatch.
Why Use This Page?
Every API request made to Jira Cloud contributes towards your available API quota.
These requests can come from various sources, including:
Jira users working in the application
Automation rules
Marketplace apps
Custom integrations
External scripts using API tokens
Understanding where API traffic originates helps you:
Identify unnecessary API usage.
Detect automation loops.
Troubleshoot integrations.
Plan capacity for future growth.
Reduce the risk of API throttling.
Understanding the API Activity Dashboard
The dashboard provides a real-time summary of API activity for the current monitoring window.
It answers questions such as:
Who is generating the most API traffic?
Which projects are the busiest?
Are automation rules consuming more API quota than users?
Which Jira activities contribute the most to API usage?
The page is divided into several sections.
Activity Summary
Traffic Breakdown
Top Consumers
Activity Insights
Activity Summary
The Activity Summary provides a high-level overview of API activity during the current monitoring period.
It displays:
Total API activity recorded during the current hour.
Average hourly activity.
Time remaining until the monitoring window resets.
Current monitoring status.
This section helps determine whether current activity is typical or unusually high.
Refresh Activity
Use the Refresh button whenever you want to retrieve the latest activity information without waiting for the next automatic update.
Refreshing the page updates:
Activity totals
Traffic distribution
Top consumer lists
Insights
Traffic Breakdown
The Traffic Breakdown shows where API usage is coming from.
Instead of looking at total API consumption, this section categorises activity by source.
User Session Traffic
Represents activity generated directly by users working in Jira.
Typical examples include:
Creating issues
Editing issues
Transitioning workflows
Adding comments
Logging work
Viewing issue details
High User Session traffic usually indicates active project teams.
This is generally expected during business hours.
Automation & Marketplace Apps
Represents API activity generated automatically by applications.
Examples include:
Jira Automation rules
Marketplace applications
Scheduled synchronisation jobs
Background processing
Higher values are normal for organisations with extensive automation.
However, sudden increases should be investigated to ensure automation rules are operating as expected.
API Token Traffic
Represents requests made using personal API tokens or service accounts.
Examples include:
Custom scripts
CI/CD pipelines
Reporting tools
External integrations
Unexpected increases may indicate:
New integrations
Inefficient scripts
Repeated API polling
Misconfigured applications
Administrators should review integrations if API Token traffic becomes the dominant source of API usage.
Top Consumers
The Top Consumers section helps identify exactly where API activity is concentrated.
Rather than reviewing thousands of API requests individually, QuotaWatch groups activity into meaningful categories.
Top Projects
Displays the Jira projects generating the highest API activity.
High activity within a project is often expected during:
Large releases
Active development sprints
Data migration projects
If one project consistently dominates API usage, consider reviewing:
Automation rules
Integrations
Bulk operations
Top Users
Lists the users responsible for the highest amount of API activity.
This does not necessarily indicate excessive usage.
Users performing activities such as:
Project administration
Bulk editing
Large imports
may naturally generate higher API activity.
Unexpected activity should be investigated to ensure accounts are not being used by automated processes.
Apps & Automation
Shows Marketplace apps, automation rules and integrations contributing to API traffic.
This view is particularly useful when investigating:
Unexpected API spikes
Performance issues
API throttling
If a single application consumes a large percentage of API capacity, review its configuration before increasing alert thresholds.
Activity Types
Displays which Jira operations occur most frequently.
Examples include:
Issue Created
Issue Updated
Workflow Transition
Comment Added
Work Logged
Understanding which activities occur most frequently helps identify business processes generating the greatest API demand.
Activity Insights
QuotaWatch automatically analyses current activity and highlights patterns that may require attention.
Insights appear only when significant activity is detected.
Examples include:
Traffic spikes
Automation-heavy workloads
Concentrated activity within a single project
Large increases compared to historical averages
These insights are intended to help administrators identify unusual behaviour without manually reviewing every metric.
When Should I Investigate?
Consider investigating API activity when:
API Health changes to Warning or Critical.
One project consistently generates significantly more activity than others.
Automation accounts consume most API traffic.
API Token usage increases unexpectedly.
Activity spikes occur outside normal business hours.
API usage increases without a corresponding increase in user activity.
Best Practices
✔ Review API Activity whenever you receive an API alert.
✔ Monitor automation usage after deploying new Marketplace apps.
✔ Review API Token activity periodically to identify unused integrations.
✔ Investigate recurring spikes rather than isolated events.
✔ Compare activity trends before and after introducing new automation rules.
✔ Use this page together with the Overview dashboard for a complete picture of API health.
Example Investigation Workflow
Suppose your Overview page reports Warning – API Usage 87%.
A typical investigation would be:
Open API Activity.
Review the Traffic Breakdown.
Determine whether activity is primarily generated by users, automation or API tokens.
Open the Top Consumers section.
Identify the project, user or application responsible for the increase.
Review recent changes to automation rules or integrations.
Continue monitoring until API usage returns to normal.
This workflow helps identify the source of increased API usage before it reaches critical levels.
Frequently Asked Questions
Does high API activity always indicate a problem?
No.
Periods of high activity are expected during:
Software releases
Data imports
Sprint planning
Bulk issue updates
Migration activities
The goal is to identify unexpected or sustained increases rather than temporary spikes.
Why is automation using more API quota than users?
Automation rules often perform multiple operations in response to a single event.
For example, one issue transition may trigger:
Issue updates
Comments
Notifications
Additional workflow transitions
As a result, automation traffic may naturally exceed user-generated traffic.
Can Marketplace apps generate API activity?
Yes.
Most Marketplace apps interact with Jira using REST APIs.
The Apps & Automation section helps identify which applications contribute to API usage.
Should I reduce automation if API usage is high?
Not necessarily.
First determine whether the activity is expected.
If automation is performing valuable business processes efficiently, no action may be required.
If unnecessary or duplicated automation is identified, consider consolidating or optimising those rules, tenant is not affected with the native Jira automation API consumption but the custom script comes under radar of the API rate limiting, if the custom script having OAuth are contributing more then you need to review the automation.
Why don't the percentages always add up exactly to 100%?
Percentages are rounded for display purposes.
Small rounding differences may occur but do not affect the underlying activity measurements.
Related Pages
For a complete understanding of your Jira environment, continue with the following pages:
Data Limits Governance – Monitor Jira configuration growth and platform limits.
History – Review historical API activity and previous incidents.
Settings – Configure alert thresholds and monitoring preferences.