Keep your own record of a page instead of a link to someone else's
A link rots, a screenshot in a ticket loses its context. Capture the page as a file that carries when it was taken, what the server answered and where it came from.
curl -G https://api.pagecapture.dev/v1/take \
-H "X-Access-Key: $PAGECAPTURE_KEY" \
--data-urlencode "url=https://example.com/terms" \
-d "format=pdf" \
-d "full_page=true" \
-d "pdf_print_background=true" \
-d "metadata_page_title=true" \
-d "metadata_http_response_status_code=true" \
-d "response_type=json" \
-o record.jsonObjects for slower mornings.
Thoughtful essentials, made in small batches from natural materials.
- Artifact
- PNG · 1440×900
- Billing
- 1 credit
- Engine
- stable
The record carries its context
Page title, final URL and the response status code come back with the artifact, so the file is not a picture with no provenance.
Four shapes of the same record
PDF and image keep what it looked like; HTML and Markdown keep what it said. The visual formats survive the origin going away, which the text ones do not.
Written to your bucket
Storage is where a record becomes an archive: our own retention is short by design, and `store` puts the artifact in a bucket whose lifecycle you own.
The same request, later
A capture is a request you can keep and re-issue on a schedule, and the same parameters always describe the same capture.
One credit per successful capture. Failures and cache hits are free.