Requests thousands of screenshtos at once in Browshot

What this operation does

Requests thousands of screenshtos at once

• POSTChanges data · Batchapi.browshot.com/batch/ceate

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Browshot operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Browshot operations

• Get all browsersGET · reads data
• Get all instancesGET · reads data
• Query screenshot statusGET · reads data
• Get information about screenshotsGET · reads data
• Share a screenshotGET · reads data
• Request a screenshotGET · reads data
• Search for screenshotsGET · reads data
• Get the batch statusGET · reads data

All 17 Browshot operations

Questions

Can HumDay requests thousands of screenshtos at once in Browshot?

Yes. This operation is published in Browshot's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Browshot data?

Yes — this is a POST operation, so it changes something in Browshot. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Browshot account.

Where this came from

Read from a published API description for Browshot at raw.githubusercontent.com/juliensobrier/browshot-api-spec/master/browshot.yaml. The description above is the provider’s own wording, not ours. Last published 2021-06-21.