# Troubleshoot Unexpected Usage

If usage is higher than expected, these tips might help identify the cause:

Be sure to familiarize yourself with usage quota costs of API calls. This will depend on the endpoint being called. Details and examples can be found in the "Usage Quota Costs" section of relevant endpoints in the docs.
If an unexpected increase in usage corresponds with recent code changes, check if a bug was recently added to your code.
Consider if you have any automated scripts running which may have been forgotten.
Your API key may have been obtained by an unauthorized user. This can happen if the API key was committed to a public repository, or if it was used on the frontend of a public-facing website. An API key can be regenerated in the accounts dashboard (opens new window).
If your code sends queries for all in-season sports, consider if more sports have recently gone in-season. The same applies if your code queries all games for a sport - consider if more games were recently scheduled.

# Tracking Usage

Usage can be tracked in the following ways:

The response headers of each API call contain information on credits used and remaining. See the documentation for details.
The accounts dashboard (opens new window) shows monthly usage for each subscription.

To access your account, you will need to create a new account (opens new window) if you have not already done so. Any existing subscriptions will automatically be linked if you use the same email address.