Tavily

POST /search/tavily, forwarded to POST https://api.tavily.com/search.

Request

curl -X POST "https://api.withgrowl.com/v1/search/tavily" \
  -H "Authorization: Bearer elo_pub_..." \
  -H "Content-Type: application/json" \
  -d '{
    "query": "travel to vietnam",
    "max_results": 5,
    "time_range": "week",
    "include_domains": ["vietnam.travel"],
    "exclude_domains": ["pinterest.com"]
  }'

Common fields are below. The body goes to Tavily as sent, so everything in Tavily’s reference works; that reference is the complete, current schema.

Field	Description
query	The search query.
max_results	Number of results.
search_depth	basic or advanced. Advanced takes longer and costs more credits.
time_range	day, week, month or year.
include_domains	Only these hostnames.
exclude_domains	Never these hostnames.
country	An English country name, not a code.

Response

Results are under results. Each has title, url, content and a relevance score, and may carry published_date.

{
  "query": "travel to vietnam",
  "results": [
    {
      "title": "Visit Vietnam: The Official Tourism Website of Vietnam",
      "url": "https://vietnam.travel/",
      "content": "Discover the highlights of Vietnam through the country's official tourism website.",
      "score": 0.93
    }
  ]
}

Through Elo

• Tavily takes its key as a Bearer token. Keep Authorization: Bearer and put your Elo key in it; Elo sets Tavily’s key itself.
• Tavily also accepts an api_key field in the body. Do not send one: Elo forwards the body as-is, and a Tavily key in it would be yours, not Elo’s.