Automate Web Evidence Capture with the Snapoena API

One HTTP POST, One Complete Evidence Package

The Snapoena API reduces web evidence capture to a single API call. Send an HTTP POST with a URL, and Snapoena returns a complete evidence package - the same court-ready bundle you get from the web app, generated programmatically.

Here is a basic capture request using curl:

curl -X POST https://snapoena.com/api/capture \
  -H "Authorization: Bearer snap_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com"}'

And the same request in JavaScript using Node.js:

const response = await fetch("https://snapoena.com/api/capture", {
  method: "POST",
  headers: {
    "Authorization": "Bearer snap_your_api_key",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ url: "https://example.com" }),
});

const evidence = await response.json();
console.log(evidence.screenshotUrl);
console.log(evidence.sha256);
console.log(evidence.timestampStatus);

That is it. No browser to manage, no Puppeteer scripts to maintain, no infrastructure to operate. Snapoena handles the headless browser capture, hash computation, and RFC 3161 timestamping on its servers.

What the API Returns

Every successful capture returns a JSON response with everything you need to retrieve and verify the evidence:

• Screenshot URL - A full-page screenshot with a metadata bar showing the captured URL, timestamp, and SHA-256 hash.
• HTML source - The complete page source code at the moment of capture, preserved exactly as the server rendered it.
• SHA-256 hash - A cryptographic fingerprint of the captured content. Any modification to the evidence will produce a different hash.
• RFC 3161 timestamp status - Confirmation that an independent Time Stamp Authority has certified the capture time. This is what makes the evidence verifiable by a third party.

The API also provides download endpoints for the complete evidence bundle ZIP, the professional PDF report, and individual files like the screenshot image or HTML source. You can integrate these directly into your document management system or case file workflow.

Use Cases for Automated Capture

The API unlocks evidence capture at a scale that manual workflows cannot match:

• Trademark monitoring scripts - Run a nightly script that checks a list of known infringing domains and captures fresh evidence automatically. When a new trademark infringement appears, your evidence is already documented.
• DMCA evidence pipelines - Feed a queue of infringing URLs into a capture pipeline and generate DMCA-ready evidence for each one. Attach the evidence bundles directly to your takedown notices.
• Compliance archiving - Capture regulated web content on a recurring schedule to maintain an auditable archive. Financial services, healthcare, and government agencies use this to satisfy record-keeping requirements.
• Brand protection at scale - Monitor marketplaces, social media, and ad networks for unauthorized use of your brand. Capture evidence across hundreds of listings and generate reports for your legal team.

Built for Integration

The API uses standard REST conventions with JSON request and response bodies. Authentication is handled via API keys with Bearer token headers. Rate limits are generous enough for batch operations, and every response includes standard HTTP status codes so your error handling is straightforward.

If you are already using scripts or tools to identify infringing content, adding evidence capture is a matter of adding one API call to your existing workflow. There is no SDK to install and no library dependency to manage - any language that can make an HTTP request can use the Snapoena API.

Full endpoint documentation, response schemas, and additional code examples are available on the API documentation page.