HumDay

Automate Archive Wayback

HumDay reads Archive Wayback’s own published API description and derives 2 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

Automate Archive Wayback

What Archive Wayback is

API for Internet Archive's Wayback Machine

API host: api.archive.org

What HumDay can do in Archive Wayback

1 documented operations change something in Archive Wayback.

  • POSTUpdate available/wayback/v1/available

What HumDay can read from Archive Wayback

These are the operations a schedule or a trigger can watch.

  • GETRead available/wayback/v1/available

How automating Archive Wayback works

  1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
  2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
  3. See it proven. The program runs and shows you the result before it is allowed near your live Archive Wayback account.
  4. Grant access, then go live. You approve the specific Archive Wayback operations it may use — and only those.

Automate Archive Wayback with these

Categories

Questions about Archive Wayback automation

Can HumDay connect to Archive Wayback?
Yes. HumDay reads Archive Wayback's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 2 operations are documented.
Do I need to write code to automate Archive Wayback?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Archive Wayback account.
What can HumDay do in Archive Wayback?
1 of the 2 documented operations change something in Archive Wayback, and 1 read from it. HumDay only ever uses the specific operations your approved contract needs.
Is my Archive Wayback account safe?
Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Archive Wayback is held behind that approval.

Where this came from

The operations above are read from a published API description for Archive Wayback at raw.githubusercontent.com/ArchiveLabs/api.archive.org/master/swagger/wayback.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.