How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SnapAPI Screenshot API

Screenshot, PDF, and batch capture

SnapAPI Screenshot API is one of 13 APIs that SnapAPI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Screenshot. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.snapapi.pics.

5 operations 4 paths 5 schemas 3 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.snapapi.pics
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

SnapAPI Screenshot API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • ApiKeyAuth — Your SnapAPI API key
  • BearerAuth — JWT access token obtained from /auth/login or /auth/refresh

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 3 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Screenshot 5

Screenshot, PDF, and batch capture

POST
/v1/screenshot
Take Screenshot
takeScreenshot body → 200202400401403429
GET
/v1/screenshot
Take Screenshot (GET)
takeScreenshotGet 11 params → 200400401
POST
/v1/screenshot/batch
Batch Screenshots
batchScreenshots body → 202429
GET
/v1/screenshot/batch/{jobId}
Get Batch Job Status
getBatchStatus 1 param → 200404
GET
/v1/screenshot/async/{jobId}
Get Async Screenshot Status
getAsyncStatus 2 params → 200404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ScreenshotRequest (58 properties), BatchRequest (10 properties), ScreenshotJsonResponse (10 properties), AsyncJobResponse (5 properties). Each schema is shown below with its type and property counts.

ScreenshotRequest
object
58 properties
ScreenshotJsonResponse
object
10 properties
BatchRequest
object
10 properties 1 required
AsyncJobResponse
object
5 properties
Error
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

snapapi-pics-screenshot-api-openapi.yml Raw ↑

Other APIs SnapAPI publishes across the network.

SnapAPI Analyze API
SnapAPI Auth API
SnapAPI Dashboard API
SnapAPI Extract API
SnapAPI Health API
SnapAPI PDF API
SnapAPI Scrape API
SnapAPI Storage API
SnapAPI Usage API
SnapAPI Utilities API
SnapAPI Video API
SnapAPI Webhooks API
Where this information came from

This is an independent, third-party profile of SnapAPI Screenshot API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.