Skip to main content
An authority fines a shop for a false discount and loses in court, because nobody can show what the price page said 3 weeks before. A page changes or goes away. A report, an audit, or a dispute needs what the page showed on one day. A fetch can return 2 things made for that: the bytes exactly as the server sent them, and a picture of the whole page.

Ask for the served bytes with a picture

Add raw_html and screenshot to formats.
Replace SOURCE_URL with the address of the page. The response has both, each with a digest, which is a hash of its bytes. This response is cut to the fields that this page explains, and the 2 files are cut to their facts.
201 Created
Each of the 2 files also has a url, where the file can be downloaded for as long as the record is stored.

Know what each part shows

A record has these parts of proof. These parts have 3 limits.
  • The time is the time of getclean’s own clock, and no outside service signs it. If a dispute can turn on the time, send the digests to a time-stamping service of your choice on the day of the fetch.
  • The picture is taken on a second visit to the page, so a site can show that visit another page than the one whose text was read.
  • A copy from an archive has the bytes as the archive served them, and no picture. A document has neither. Its source.document_digest is the hash of the file itself.

Store the files yourself

A record is stored for 48 hours after its last use and for at most 30 days, and a dispute can come after a year. Download the 2 files while the record is stored, and store them with their digests, the fingerprint, and the time. Anyone can then hash the files again and compare. A fetch that sends retention as none stores nothing. The 2 files then come inside the response, as base64.

Record a page that a person saved

A page behind a sign-in cannot be fetched by its address. A person can open it, save it, and send the file to upload_contents, with the page’s address as captured_url and the time it was saved as captured_at. The record then has both, as you stated them, and the hash of the file. A saved page is read from its bytes alone. Nothing it points to is loaded, so its content can differ from what the person saw, and no picture is made.

Check what proof costs

raw_html adds nothing to the cost of a fetch. A picture costs one screenshot unit. If the picture cannot be made within the time or the spending limit of the call, a notice says so, and the record still comes.