Every Snapsnip API request requires an API key. API keys identify your account and determine which captures, downloads, and configured destinations you can access.

​
Send your API key

Use the HTTP bearer authentication scheme:
For example:
The API returns 401 Unauthorized when the header is missing or the key is invalid.

​
Keep API keys private

Snapsnip API keys are intended for server-side use. Never place them in browser bundles, mobile applications, query strings, public repositories, or client-visible logs.
Store API keys in your deployment’s secret manager or environment:
Use separate keys where operational isolation or independent rotation is required. Revoke a key immediately if it may have been exposed.

​
Account-scoped resources

Asynchronous capture status and download URLs are account-scoped. Requests for missing, malformed, or another account’s capture identifier return 404 Not Found. Treat capture and cloud-storage destination identifiers as opaque values.

​
Download authentication

The stable download_url returned for a completed asynchronous capture requires your Snapsnip API key. After authorization, the API redirects to a short-lived URL on downloads.snapsnip.io. Clients must:
  1. Send Authorization only to api.snapsnip.io.
  2. Follow the temporary redirect.
  3. Remove Authorization when the hostname changes.
  4. Request a fresh redirect from the stable API URL when retrying later.
The temporary download URL is a short-lived bearer credential. Do not persist, share, or log it.