Skip to main content
actions runs up to 50 steps in order before the page is read. Use it to load more results, open a tab, fill a search box or capture the page at the right moment. It needs an API key. Without one the call returns 401 apiKeyRequired. This request scrolls, clicks “More”, waits a second, takes a screenshot, then reads the page it ends on:
The formats describe the page after the last step. Captures from the middle come back under data.actions, in the order the steps ran. metadata.sourceURL is the URL you sent and metadata.url is where the page ended up.

Steps

Failures and limits

  • When a step fails, the later steps do not run. You still get the page as it stood, with a warning that names the step and says why. Always read warning when you send actions. To find the right selector, try it in an Interact session.
  • A step that does not fit the table returns 400 invalidRequest and names the step.
  • screenshot and pdf steps with zeroDataRetention return 400 invalidRequest, because they are kept as files.
  • A read with actions is always live. Waits count toward timeout.
  • The actions add no fee. See Pricing.