access_key
. The API will return the usage statistics for your account.
Requests to this endpoint are not counted against your usage quota, but they are still subject to rate limiting. This ensures fair use and stability of the platform. If you exceed the rate limit, your requests may be temporarily blocked.
Getting started
REST
The Usage API, like all of ScreenshotMAX’s APIs, is organized around REST. It is designed to use predictable, resource-oriented URL’s and to use HTTP status codes to indicate errors.HTTPS
The Usage API requires all communications to be secured TLS 1.2 or greater.API Versions
All of ScreenshotMAX’s APIs are versioned. The Usage API is currently on Version 1.Your Access Key
Your access key is your unique authentication key to be used to access ScreenshotMAX APIs. To authenticate your requests, you will need to append your access key to the base URL as a query parameter for GET requests. For POST requests, you can include your access key in the request body as a JSON object. You can also use theX-Access-Key
header to pass your access key.
You can find your access key in your account dashboard.
Base URL
Validation endpoint
ScreenshotMAX’s Usage API simply requires your unique access key. The API will return usage statistics for your account.Request parameters
Your unique access key. You can find your access key in your account dashboard.
Response parameters
The API response is returned in a universal and lightweight JSON format.Usage statistics for your account.
Usage statistics for your account.
Error Codes
Whenever you make a request that fails for some reason, an error is returned also in the JSON format. The errors include an error code and description, which you can find in detail below.Code | Type | Details |
---|---|---|
200 | OK | The request was successful. |
401 | Unauthorized | The request was rejected due to an invalid access key. |
500 | Internal server error | The request failed due to an internal server error. |