Parameters & Response

GET /validate

Validate all schemas on a public URL. Pass parameters as query strings — no request body needed.

curl "https://schemacheck.dev/api/v1/validate?url=https://apple.com&access_key=YOUR_KEY"

Query parameters

POST /validate

Accepts either a URL or raw JSON-LD in the request body. Use the x-api-key header for server-side calls.

Request body — URL input

curl -X POST https://schemacheck.dev/api/v1/validate \
  -H "x-api-key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com"}'

Request body — JSON-LD input

curl -X POST https://schemacheck.dev/api/v1/validate \
  -H "x-api-key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonld": {
      "@context": "https://schema.org",
      "@type": "Article",
      "headline": "My Article",
      "author": { "@type": "Person", "name": "Jane Doe" },
      "datePublished": "2026-03-18",
      "image": "https://example.com/photo.jpg"
    }
  }'

Body fields

Headers

Success response (200)

All successful responses share this shape. Fields marked optional are only present when applicable.

Top-level

Schema object

Issue object (errors and warnings)

RichResult object

Summary object

Meta object

POST /validate/batch

Validate up to 50 URLs in a single API call. All URLs are processed concurrently and partial failures are tolerated — results for successful URLs are always returned even if some URLs time out or are unreachable. The entire batch counts as one API request against your rate limit; credits are charged only for URLs that validate successfully (1 credit per successful URL, 0 for cached or failed URLs).

curl -X POST https://schemacheck.dev/api/v1/validate/batch \
  -H "x-api-key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "urls": [
      "https://example.com/page1",
      "https://example.com/page2",
      "https://example.com/page3"
    ]
  }'

Request body

Headers

Batch response (200)

The response always has HTTP 200 as long as the request itself was valid (auth passed, body was parseable, URL count was within limit). Per-URL failures are reported inside results, not as HTTP error codes.

{
  "success": true,
  "results": [
    {
      "url": "https://example.com/page1",
      "success": true,
      "schemas_found": 2,
      "schemas": [ /* ... Schema objects ... */ ],
      "summary": {
        "score": 87,
        "total_schemas": 2,
        "valid_schemas": 2,
        "invalid_schemas": 0,
        "total_errors": 0,
        "total_warnings": 3,
        "rich_result_eligible": 1
      }
    },
    {
      "url": "https://example.com/bad-page",
      "success": false,
      "error": "Timeout after 10s"
    }
  ],
  "meta": {
    "total_urls": 2,
    "successful": 1,
    "failed": 1,
    "credits_used": 1,
    "credits_remaining": 248,
    "total_response_time_ms": 4200
  }
}

Result item — success

Result item — failure

Batch meta object

Batch limits and behaviour

Supported schema types

35 schema types validated against Google's current structured data requirements. Types are organised into tiers that determine validation depth.

Caching

Rate limits

Limits are per API key, per minute (sliding window). Exceeded requests return rate_limit_exceeded (HTTP 429). Note that the batch endpoint counts as one request against this limit regardless of how many URLs are in the batch.