
Browshot API
Browshot API
Generate website screenshots through screenshot/create, screenshot/html, and screenshot/host, then inspect browser and instance metadata.
Exposes screenshot/create, screenshot/html, and screenshot/host directly
Some path names carry historical quirks such as batch/ceate
Begin with an API key and create a screenshot via screenshot/create or screenshot/html. After that, inspect screenshot/info, then expand to batch/info, browser/list, and instance/list for larger workloads.
Uptime · 30-day window
About this API
The main story here is clear: create, inspect, host, and delete screenshot jobs, with supporting browser, batch, instance, and account endpoints around them. Concrete nouns in the spec include "/account/info", "/batch/ceate", "/batch/info", and "/browser/info".
That is enough to support generate website screenshots for review or archiving, run screenshot jobs in batches, and inspect browser instances and account information. The OpenAPI document names security schemes such as "apiKeyQuery".
Some path names carry historical quirks such as batch/ceate Best suited to screenshot workflows rather than broad crawling
What you can build
- 1Generate website screenshots for review or archiving
- 2Run screenshot jobs in batches
- 3Inspect browser instances and account information
Strengths & limitations
Strengths
- Exposes screenshot/create, screenshot/html, and screenshot/host directly
- Includes browser/list and instance/list resources
- Uses a simple apiKeyQuery security scheme
Limitations
- Some path names carry historical quirks such as batch/ceate
- Best suited to screenshot workflows rather than broad crawling
Example request
curl https://browshot.com/contact/<endpoint> \
-H "Authorization: Bearer $API_KEY"
# Some providers use X-Api-Key instead — verify in the docs.Getting started
Begin with an API key and create a screenshot via screenshot/create or screenshot/html. After that, inspect screenshot/info, then expand to batch/info, browser/list, and instance/list for larger workloads.
Technical details
- Auth type
- api_key
- Pricing
- unknown
- Protocols
- REST
- Response time
- 388 ms
- Last health check
- 5/12/2026, 7:37:10 AM