TinyFish
GET /search/tinyfish, forwarded to GET https://api.search.tinyfish.ai. TinyFish
takes its request as URL query parameters, not a body.
Request
Section titled “Request”curl "https://api.withgrowl.com/v1/search/tinyfish?query=travel%20to%20vietnam&location=US&language=en" \ -H "Authorization: Bearer elo_pub_..."Common parameters are below. The query string goes to TinyFish as sent, so everything in TinyFish’s reference works; that reference is the complete, current schema.
| Parameter | Description |
|---|---|
query | The search query. |
location | Country code, upper case, for example US. |
language | Language code, lower case, for example en. |
recency_minutes | Only pages newer than this many minutes; 10080 is one week. |
TinyFish has no result-count or domain filter parameters.
Response
Section titled “Response”Results are under results. Each has title, url, snippet and date.
{ "results": [ { "title": "Visit Vietnam: The Official Tourism Website of Vietnam", "url": "https://vietnam.travel/", "snippet": "Discover the highlights of Vietnam through the country's official tourism website.", "date": "2026-02-18" } ]}Through Elo
Section titled “Through Elo”- TinyFish takes its key in
X-API-Key. Keep that header and put your Elo key in it, or useAuthorization: Bearer; Elo sets TinyFish’s key itself. - A
POSTto this path answers405; the request is the query string.