JSON-LD from live webpages

Schema Markup Extraction API

Read machine-readable entities embedded in a webpage without mixing them into navigation, styling, and unrelated HTML. Choose raw mode to preserve source blocks or normalized mode to flatten graphs and remove duplicate entities before further validation.

Get an API key Read documentation

Web pages passing through a processing grid and becoming structured data cards

Endpoint

POST /v1/schema

A working request

Set your key once in a server-side environment variable, then send a JSON request.

cURL

curl --request POST \
  --url "https://api.tooltrace.io/v1/schema" \
  --header "X-ToolTrace-Key: ${TOOLTRACE_KEY}" \
  --header "Content-Type: application/json" \
  --data '{
  "url": "https://example.com"
}'

Response scope

What the API returns

The response is structured for software, with source evidence kept beside the extracted or inspected data.

JSON-LD objects and arrays
Detected schema types
Structured page entities
Source and final URL evidence
Parse warnings when data is incomplete

Practical uses

Catalog enrichment

Collect declared product, article, organization, event, or business fields from permitted public sources.

Publishing QA

Confirm that structured data is present after a template or content deployment.

Search research

Study which entities and properties a page declares before running deeper validation.

Implementation guidance

Use the result with context.

Extraction is different from validation

The API reports parseable structured data found on the page. Presence does not mean Schema.org considers every property valid or that Google considers the page eligible for a rich result.

Validate vocabulary against Schema.org, test supported search features with Google's Rich Results Test, and compare every declared fact with visible page content.

Expect more than one entity

A page can contain an article, author, publisher, breadcrumbs, website, and organization in one graph. Preserve identifiers and relationships instead of flattening every object into one record.

Authentication, limits, and errors

Send your key through the X-ToolTrace-Key header from server-side code. Read credit and rate-limit headers after every request. Validation, blocked destination, authentication, plan, and upstream fetch errors use structured responses that applications should handle by code rather than message text.

Use a dedicated key for each environment. Review current fields in the interactive API reference and compare usage limits on the pricing page.