Sharing

Public sharing

Every PDF starts private — only your signed-in session can view it. The Share button on the dashboard card (or POST /api/screenshots/:id/share) mints a token that turns the PDF public on a stable URL.

https://deepsyte.com/shared/screenshots/<token>

That URL is unguessable (32 random characters) but anyone who has it can view the PDF without signing in. Tokens never expire automatically; you keep one unless you explicitly revoke it.

Mint via REST

curl -X POST https://api.deepsyte.com/api/screenshots/<id>/share \
  -H "Authorization: Bearer $DEEPSYTE_KEY"

Response:

{
  "shareToken": "shotshare_aB...XZ",
  "shareUrl": "https://deepsyte.com/shared/screenshots/shotshare_aB...XZ"
}

Revoke a share

curl -X DELETE https://api.deepsyte.com/api/screenshots/<id>/share \
  -H "Authorization: Bearer $DEEPSYTE_KEY"

Revoking deletes the share token. Any iframe embed using the old token will 404 from that point onward.

What viewers see

The public viewer at /shared/screenshots/<token> shows:

• The PDF thumbnail (or inline PDF for older captures).
• The source URL the page was captured from.
• The capture timestamp.
• A "Made with PDFShot" footer that links back to pdfshot.deepsyte.com.

Viewers never see your email, account, or any other capture in your library.

What viewers don't see

• The original page's interactive state — they only get the rendered PDF.
• Any captures other than the one tied to that specific token.
• Webhooks, dashboard, API keys, billing, or account settings.

Related

• Embedding — drop the PDF inline on another site.
• Watermark — the free-tier footer that lives in the PDF itself.