Normalized links from one webpage

Link Extraction API for Developers

Turn the links in a public webpage into structured data without maintaining a separate parser. Each result keeps the destination, anchor text, relationship, and rel attributes together, while fetch evidence shows which page was actually processed.

Get an API key Read documentation

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

Endpoint

POST /v1/links

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

Normalized link destinations
Link text and page context where available
Internal or external classification
rel, nofollow, sponsored, and UGC attributes
Requested and final page URL
Fetch timing, status, and warnings

Practical uses

Internal link inventories

Collect destinations and anchor text before reviewing navigation, contextual links, or orphan-page workflows.

Migration review

Compare normalized destinations before and after URL, template, or navigation changes without parsing each page by hand.

Research and automation

Turn a source page into a structured list for citation review, content research, and controlled downstream queues.

Implementation guidance

Use the result with context.

One page is not a full-site crawl

The endpoint extracts links from the requested page. It does not visit every destination or report whether those destinations are broken. Your application decides which URLs are in scope and whether to request more pages.

Normalization makes results comparable

Relative destinations are resolved against the fetched page so the response can be filtered and deduplicated consistently. Keep the requested URL, final URL, and source-page context with stored results.

Treat link text and rel values as evidence

Anchor text can be empty, generic, or misleading. Values such as nofollow, sponsored, and ugc describe the publisher's relationship with a link, but they do not prove that the destination is safe, live, or indexable.

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.