Search Trends
Interest over time for up to five keywords, with regional breakdown.
curl -X POST https://api.1lookup.dev/v1/search-trends \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"keywords":"skip tracing, reverse phone lookup","timeframe":"12m"}'{
"success": true,
"data": {
"keywords": [
"skip tracing",
"reverse phone lookup"
],
"timeframe": "12m",
"interval": "week",
"averages": {
"skip tracing": 34,
"reverse phone lookup": 71
},
"interest_over_time": [
{
"date": "2026-11-01",
"values": {
"skip tracing": 31,
"reverse phone lookup": 68
}
},
{
"date": "2026-11-08",
"values": {
"skip tracing": 33,
"reverse phone lookup": 72
}
},
{
"date": "2026-11-15",
"values": {
"skip tracing": 36,
"reverse phone lookup": 70
}
}
],
"by_region": [
{
"region": "United States",
"code": "US",
"values": {
"skip tracing": 41,
"reverse phone lookup": 100
}
},
{
"region": "Canada",
"code": "CA",
"values": {
"skip tracing": 18,
"reverse phone lookup": 64
}
}
],
"rising_queries": [
{
"keyword": "skip tracing",
"query": "skip tracing for real estate investors",
"growth_pct": 180
},
{
"keyword": "reverse phone lookup",
"query": "reverse phone lookup api",
"growth_pct": 90
}
]
},
"meta": {
"credits_used": 2,
"credits_remaining": 999,
"cached": false,
"request_id": "req_8f3a2c1e9b7d"
}
}Authorization
Authorizationstring<bearer>requiredYour API key as a Bearer token. Live keys start with 1lk_live_. Test keys start with 1lk_test_ and return this endpoint's sample response without spending credits. See authentication.
Body
Send the fields as a JSON object with Content-Type: application/json.
keywordsstringrequiredKeywords (comma separated). Example: skip tracing, reverse phone lookup
timeframeenum<string>requiredTimeframe. One of: 12m, 2y, 4y. Example: 12m
freshbooleanSkip the 7-day cache and run a new lookup. Charged as a normal lookup.
referencestringYour own identifier, echoed back in meta and shown in lookup history.
Response
A 200 response carries the result in data and the cost of the call in meta. These are the fields most integrations read.
successbooleantrue when the lookup ran.
data.interest_over_timearrayOne point per interval, with a 0 to 100 value for each keyword in the request.
data.averagesobjectThe mean index value per keyword across the timeframe, for a quick ranking.
data.by_regionarrayIndex values per keyword for each region, showing where interest is concentrated.
data.rising_queries[].queryvalueRelated searches that are growing, tied to the keyword they relate to.
data.rising_queries[].growth_pctvalueHow much interest in the rising query has grown over the timeframe, in percent.
data.intervalstringWhether the points are daily, weekly or monthly, which depends on the timeframe.
data.timeframestringThe window the index covers: 30 days, 3 months, 12 months or 5 years.
meta.credits_usednumberCredits charged for this call.
meta.credits_remainingnumberYour balance after the call.
meta.cachedbooleantrue when the result came from the 7-day cache.
meta.request_idstringQuote this when you contact support.
Errors
A failed request returns success: false with an error object, and is never charged. The full list is on the errors page.
| HTTP | Code | Meaning |
|---|---|---|
| 401 | unauthorized | The key is missing, malformed or revoked. |
| 402 | insufficient_credits | Your credits are used up and pay as you go is off or at its limit. |
| 422 | invalid_input | A field is missing or malformed. The field property names it. |
| 429 | rate_limited | Too many requests for this key. Wait for the Retry-After interval. |
| 500 | internal_error | Something failed on our side. Safe to retry. |
| 503 | source_unavailable | An upstream source did not answer in time. Safe to retry. |
Billing
2 credits / search. Charged when the lookup runs and returns a result. Errors are never charged, and repeating the same input within 7 days is served from cache at no charge.
Product overview and use cases