Learn how SimplifyAccess counts API requests, Jobs, sent emails, reports, and support tickets, how allowances apply across websites, and when monthly usage resets.
SimplifyAccess tracks platform activity so you can understand how much of your subscription’s available capacity you are using. These usage figures measure requests and actions. They do not represent accessibility scores or indicate how accessible your website is.
Your limits depend on your active subscription. Most allowances apply separately to each controller, which represents a website or domain. Support tickets are limited at the account level, across all controllers.
Which limits apply to a controller or account?
| Usage metric | What it measures | Where the limit applies |
|---|---|---|
| API requests | Requests for data from the SimplifyAccess platform | Per controller |
| Jobs | Manually triggered processing tasks | Per controller |
| Sent emails | Accessibility-issue messages sent to an email address assigned to the controller | Per controller |
| Reports | Reports generated during the monthly usage period | Per controller |
| Support tickets | New tickets created in the support area during the monthly usage period | Per account |
Each controller has its own API, Job, email, and report allowances. An overall account usage total does not turn these separate allowances into a shared pool.
Support tickets work differently: all controllers in an account share one monthly ticket allowance. Adding or switching controllers does not provide a separate support-ticket allowance.
Where to view usage
Usage for one website
Open the controller dashboard and select the website you want to review.
The Usage card shows consumption for the selected controller. Always check which controller is active before interpreting the figures, particularly when your account manages several websites.
Usage across your controllers
Open the Controllers page.
The Overall Usage card combines activity across the controllers connected to your account. The controller table below shows usage for individual websites, helping you identify which projects account for most of the activity.
Use the combined view to understand total activity, and review individual controllers when checking their remaining capacity. Support-ticket usage applies to the account as a whole.
What is an API request?
An API request, also called an API call, is counted when a website requests data from the SimplifyAccess platform.
The SimplifyAccess widget retrieves website-specific settings and prepared content when needed. Requests can include:
- Widget settings and configuration
- Simplified or Plain Language content
- Video transcriptions
- Other prepared content associated with the controller
An API request does not necessarily correspond to one visitor or one page view. A visitor may trigger several requests by using different features, while another visit may reuse data already stored in the browser.
How caching affects usage
Widget settings are cached in the visitor’s browser for approximately one hour. During that period, additional page views can reuse those settings instead of requesting them again.
This reduces unnecessary requests, so the API count will not normally increase for every page opened during the same browsing session.
Prepared content, such as a simplification or transcription, may require a separate request when a visitor uses that feature.
What is a Job?
A Job is a manually triggered action that starts a processing task in SimplifyAccess. These tasks can involve crawling a website, analyzing pages, generating content, or processing media.
Examples include:
- Starting a website crawl
- Running or repeating accessibility tests
- Generating a report
- Starting AI-assisted content processing
- Starting a video transcription
- Repeating another complex page-level process
Jobs are generally counted by the number of items processed, rather than simply by the number of buttons clicked.
For example, manually starting accessibility tests for 25 URLs uses 25 Jobs. A single bulk action can therefore consume several Jobs.
Manual and automated Jobs
Only manually triggered actions reduce the controller’s Job allowance.
Automated or scheduled processes started internally by SimplifyAccess do not consume that allowance. The platform can therefore perform its regular monitoring without using the capacity reserved for customer-initiated tasks.
What counts toward the email allowance?
The email allowance counts accessibility-issue messages sent through SimplifyAccess to an address assigned to the controller, such as your developer’s email address.
The pricing page calls these Developer emails. The recipient can be the person responsible for reviewing or resolving accessibility issues for that website.
Usage is measured as messages sent, rather than as the number of accessibility issues included in a message. Each controller has its own monthly email limit.
These emails are separate from support tickets. Sending findings to your developer uses the controller’s email allowance; creating a ticket in the SimplifyAccess support area uses the account’s support-ticket allowance.
What counts toward the report allowance?
The report allowance limits how many reports can be generated for a controller during each monthly usage period.
Each controller has its own report limit. Generating a report for one website uses that website’s allowance.
Report generation is also a manually initiated processing action, as described in the Jobs section. The monthly report cap is an additional limit to consider when planning reporting work.
What counts toward the support-ticket allowance?
The support-ticket allowance limits the number of new tickets that can be created in the SimplifyAccess support area each month.
This limit applies to the entire account, even when the account contains several controllers.
For example, an Agency account has one shared support-ticket allowance for all its websites. Creating tickets concerning different controllers still consumes the same account allowance.
Monthly email, report, and support-ticket limits
The pricing page currently lists the following allowances:
| Monthly allowance | Standard | Pro | Agency |
|---|---|---|---|
| Sent emails, per controller | 5 | 40 | 40 |
| Reports generated, per controller | 1 | 5 | 5 |
| Support tickets created, per account | 2 | 5 | 20 |
For example, an Agency account with three controllers has an allowance of 40 emails and 5 reports for each controller, alongside 20 support tickets shared across the account.
API requests and Jobs also have controller-level limits. The public pricing page does not currently list numerical allowances for these two metrics. Refer to your subscription’s assigned limits when reviewing usage.
Check the pricing page for current plan details, other restrictions, and available features.
When does usage reset?
Usage resets monthly, based on the day of the month when the license was originally activated.
For example, if your license was activated on 12 July, the next resets occur on 12 August, 12 September, and the corresponding day in subsequent months.
Your usage period therefore follows your license activation date, rather than automatically starting on the first day of each calendar month.
This monthly reset applies to API requests, Jobs, sent emails, reports, and support tickets. The scope of each allowance remains the same: the first four apply per controller, while support tickets apply per account.
Why usage differs between controllers
Websites can consume different amounts of capacity even when they have access to the same subscription features.
API usage can be higher when more visitors use widget features or open prepared content. Job usage can increase when your team repeats audits, processes many URLs in bulk, or frequently starts content workflows.
Email and report usage depend on how often your team sends accessibility findings and generates reports for each website.
Reviewing these figures together helps you understand whether usage is driven mainly by visitor activity, processing work, or communication and reporting.
What to do when you approach a limit
Before starting a large batch of work, check the relevant controller’s remaining allowance and the next monthly reset date.
When an allowance is exhausted, actions that require that capacity may become unavailable until the allowance resets or additional capacity is arranged. Email, report, and support-ticket caps limit the corresponding activity.
If limits regularly restrict your workflow, review the available plans and discuss your requirements with SimplifyAccess.
When requesting assistance, include:
- Your current subscription plan
- The affected controller or website, where applicable
- The allowance you are reaching
- The activities responsible for most of the usage
- The additional capacity you expect to need
This helps the team assess your requirements and discuss suitable options.