Tavily URL Content Extraction

API docs
https://api.sandbase.ai/v1/api/tavily/extract

Extracts clean text content from specified web pages using their URLs. Supports basic or advanced extraction depth and optional image inclusion.

Price
$0.012USD / call
Method
POST
Response
JSON
Parameters
1 required · 2 optional
100 free calls / dayFirst 100 calls per day free (shared per organization) · Resets at 00:00 UTC. Pay per call after that.

Playground

Input
URLs to extract content from.
Depth of content extraction. Allowed values: basic, advanced.
Include images found on the pages.
OutputExample
Responseoutputs · 420 B · 13 lines
{
  "failed_results": [],
  "request_id": "35001ccb-b475-4057-b008-b5026dc5ac41",
  "response_time": 0,
  "results": [
    {
      "images": [],
      "raw_content": "# Example Domain\n\nThis domain is for use in documentation examples without needing permission. Avoid use in operations.\n\n[Learn more](https://iana.org/domains/example)",
      "title": "Example Domain",
      "url": "https://example.com"
    }
  ]
}

Examples

Select an example to load its inputs and result into the playground.

API README

Tavily URL Content Extraction API

Returns the page title and images for each URL you send, with a list of URLs that could not be extracted. It needs a urls array with one or more web page addresses.

Use cases

  • Pull the title of a list of known pages to check what each URL points to.
  • Collect the images found on specific pages by setting include_images to true.
  • Find which URLs in a batch could not be extracted by reading failed_results.
  • Run a batch of pages from a search or site crawl through one extraction call.

Request

curl -X POST "https://api.sandbase.ai/v1/api/tavily/extract" \
  -H "Authorization: Bearer $SANDBASE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls": ["https://en.wikipedia.org/wiki/Artificial_intelligence"]}'

The result is returned in outputs[0].data.

Parameters

NameTypeRequiredDescription
urlsarrayYesURLs to extract content from.
extract_depthstringNoDepth of content extraction.
include_imagesbooleanNoInclude images found on the pages.

Example response

Real response for the request above, trimmed: lists keep their first item and long strings are cut.

{
  "failed_results": [],
  "request_id": "f594f392-10f6-4a3f-9d7c-ac020a617625",
  "response_time": 0.03,
  "results": [
    {
      "images": [],
      "title": "Artificial intelligence - Wikipedia",
      "url": "https://en.wikipedia.org/wiki/Artificial_intelligence"
    }
  ],
  "usage": {
    "credits": 1
  }
}

Response fields

FieldMeaning
results[]One entry per URL that was extracted successfully.
results[].urlThe page address that was extracted. Use it to match each result to the URL you sent.
results[].titleThe title of the page, for example Artificial intelligence - Wikipedia.
results[].imagesList of images found on the page. It is empty in this response, where include_images was not set.
failed_resultsList of URLs that could not be extracted. It is empty when every URL worked.
request_idUnique ID of the request, as a UUID.
response_timeTime taken for the request. The value is a number such as 0.03.
usage.creditsNumber of credits recorded for the call, such as 1.

Notes

  • Pass several addresses in the urls array to extract them in one call. Check both results and failed_results for each one.
  • Set extract_depth to basic or advanced. Set include_images to true to fill results[].images.
  • To find URLs to extract, call Tavily Search or Tavily Site Map.

Submit URLs without assuming a text field

Send urls as an array of public page addresses. extract_depth accepts basic or advanced; include_images is a boolean. Search takes a query, while this request takes URLs you already selected. The current reference sample shows URL, title and image fields with failed_results; it does not demonstrate raw_content. That absence is not proof that text extraction is impossible, and it is not a guarantee of full-page text either. Check the approved response for your target before writing a text parser or claiming a complete RAG workflow.

To discover candidate URLs first, read the Tavily Search parameters and the Python search guide. Review and select a URL yourself; the examples do not chain or retry requests.

Pricing

$0.012 per successful call. Failed calls are not charged. It is included in the daily free quota of each organization.

Explore more

Related APIs

All APIs
APIPriceResponse
Tavily$0.012 per callJSON
Tavily$0.012 per callJSON
Tavily$0.012 per callJSON

Questions

FAQ

How do I use the Tavily URL Content Extraction API?

Send a POST request to https://api.sandbase.ai/v1/api/tavily/extract with your SandBase API key in the Authorization header (Bearer) and the parameters as a JSON body. You can also try it in the Playground on this page without writing code.

How much does the Tavily URL Content Extraction API cost?

$0.012 per call. Every organization gets 100 free calls per UTC day, shared across eligible SandBase APIs including this one; after that each call is billed at this price from your SandBase balance. There is no subscription.

What parameters does the Tavily URL Content Extraction API accept?

Required: urls (array). Optional: extract_depth (one of basic, advanced) and include_images (boolean). The Parameters table and the Playground on this page list every field.

What does the Tavily URL Content Extraction API return?

A JSON response returned in the same HTTP request (synchronous). The README on this page includes a sample response.

Do I need a Tavily developer account or API key?

No. Tavily URL Content Extraction runs through SandBase, so one SandBase API key covers this endpoint and every other API and model in the catalog. You do not need to apply for Tavily API access separately.

What is the URL input format?

Send urls as an array of public page addresses, not a single string or a search query. extract_depth accepts basic or advanced; include_images is a boolean. Review this endpoint's current schema instead of copying extra upstream options.

Can I assume every extracted result contains raw_content?

No. The current reference sample shows URL, title and image fields with failed_results, but does not demonstrate raw_content. This does not establish that page text is unavailable. Verify an approved response for your target before relying on a text field, full-page coverage or a downstream RAG workflow.

Does a completed request prove every URL was extracted?

No. The documented envelope is outputs[0].data, and the reference describes results and failed_results. A completed run or HTTP success alone is not proof that every URL produced the content you wanted. Review the response and keep missing fields unknown rather than converting them to empty text.