Metadata endpoint

Website Metadata Extraction API

Read the metadata that search engines, social platforms, publishing systems, and content catalogs use to understand a page. Get normalized fields without maintaining a separate HTML parser.

Get an API key Read documentation

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

Endpoint

POST /v1/metadata

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/metadata" \
  --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.

Page title and meta description
Canonical URL and language
Open Graph properties
Twitter Card values
Author and publication fields
Fetch status and final URL

Practical uses

Metadata quality checks

Find missing or inconsistent titles, descriptions, canonicals, and social fields across a controlled URL list.

Link preview systems

Build internal previews for bookmarks, research tools, messaging products, or content catalogs.

Content inventories

Attach page identity and provenance fields to records collected from the public web.

Implementation guidance

Use the result with context.

Metadata is a signal, not a promise

Search engines can rewrite titles and descriptions. Social platforms can cache older values or crop images differently. The API reports what the fetched page provides at request time.

Compare metadata with visible content. A complete field can still be misleading, duplicated, or too vague to help a reader.

Use the smallest useful response

Choose this endpoint when you need page identity and social fields but do not need the full article or page body. Smaller responses are easier to store and validate.

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.