Screenshot API Usage Logs

Usage logs for the Screenshot API are incredibly useful for several reasons. First and foremost, they help with diagnosing any issues that may arise when using the API. By reviewing the logs, you can pinpoint where any errors or discrepancies occurred and address them accordingly.

In addition to troubleshooting, usage logs provide valuable visibility into how your account is being used. You can see the volume of requests being made, which websites are being captured, and other important metrics that can help with optimization and resource allocation.

Finally, usage logs also allow you to track where your screenshots were uploaded to. This is particularly helpful if you are using the API to capture screenshots of your own website, as it can help you monitor changes and ensure that updates are being properly implemented.

Overall, having access to usage logs is a powerful tool for anyone using the Screenshot API. It provides valuable insights into the performance and usage of the API, which can help you optimize your workflows and troubleshoot any issues that may arise.

Usage logs on the Add Screenshots portal

Usage logs are available when taking website screenshots with Add Screenshots. You can access the latest logs on the Usage Logs page.

Information available in the usage logs may include the following, depending on the type and status of the request:

  • Date - when the screenshot was taken
  • Request URL - the requested website URL (e.g.
  • Website URL - the final website URL of the website after redirection (e.g.
  • Status Code - HTTP status of the web response such as 200 (OK) or 201 (CREATED)
  • IP Address - The IP address of the client who made the screenshot request
  • Country Code - The country code of the client who made the screenshot request
  • Referrer - The website where the request came from
  • Region - The Screenshot API region where the screenshot was taken from
  • Job ID - the unique identifier to correlate multi or bulk screenshot requests
  • Error - debug information retuned by the site such as invalid storage credentials was specified
  • Storage - the name of the storage provider such as S3 or Azure
  • Image - the URL to the screenshot image
  • Image Old - the URL to the track changes archived image
  • Image Diff - the URL to the track changes diff image comparison

An example of the usage log entries:

Screenshot Usage Logs