For additional security, you can authenticate GET requests using a signed querystring. This method ensures that the request has not been tampered with and comes from a trusted source.Documentation Index
Fetch the complete documentation index at: https://docs.screenshotmax.com/llms.txt
Use this file to discover all available pages before exploring further.
What is a Signed Request?
A signed request uses your secret key to generate a SHA-256 hash of the querystring. This hash is then included in the request as a signature parameter. When our servers receive the request, they verify the signature using the same secret key.Your Secret Key
- Your
secret_keyis unique to your account. - It is only visible in your dashboard.
- Never share your secret key publicly.
- You can rotate your secret key at any time via the dashboard.
Enforce Signed GET Requests
From your dashboard, you can enforce signature validation for all GET requests by enabling the option: “Accept only signed requests” Once enabled:- Any unsigned GET request will be rejected.
- This setting does not affect POST or other non-GET requests.
- You can toggle this option from the Access Control Management section in your dashboard.
How to Sign a Request
1. Start with your full querystring (everything after the ?)
Example of querystring:2. Do not include the signature parameter (yet)!
3. Compute the SHA-256 HMAC of the querystring using your secret_key
Node.js Example
4. Add the signature parameter to your final querystring
Rotating the Secret Key
Just like theaccess_key, you can rotate your secret_key from your dashboard.
After rotation:
- A new secret key will be generated.
- The old one will become invalid.
- Make sure to update all your signing logic with the new key.
Test Your Signature
We recommend verifying your implementation in a development environment before going live.Why Use Signed Requests?
Signed requests add an extra layer of protection, ensuring:- The request hasn’t been modified in transit.
- The request originates from a trusted client with access to the secret key.
- You can optionally enforce this behavior for all GET calls to your API.

