Reported Number Check
How often a number was reported to the FTC in the last 12 months, and for what.
curl -X POST https://api.1lookup.dev/v1/reported-number-check \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"phone_number":"+15125550142"}'{
"success": true,
"data": {
"phone_number": "+15125550142",
"reported": true,
"reports_12m": 37,
"robocall_reports_12m": 29,
"categories": [
{
"category": "debt_reduction",
"reports": 16
},
{
"category": "imposter",
"reports": 9
},
{
"category": "warranties_and_protection_plans",
"reports": 7
},
{
"category": "other",
"reports": 5
}
],
"first_report_date": "2026-01-14",
"most_recent_report_date": "2026-10-28",
"window": {
"from": "2025-11-19",
"to": "2026-11-19"
},
"source": "FTC Do Not Call complaint data"
},
"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.
phone_numberstring<E.164>requiredPhone number. Example: +15125550142
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.reportedbooleantrue when at least one FTC complaint names the number inside the 12-month window.
data.reports_12mnumberHow many complaints were filed about the number in the last 12 months.
data.robocall_reports_12mnumberHow many of those complaints described a prerecorded message.
data.categoriesarrayComplaint subjects with a count for each, such as debt reduction, imposter or warranty calls.
data.first_report_datestringThe earliest complaint inside the window.
data.most_recent_report_datestringThe latest complaint on record, which shows whether the activity is ongoing.
data.window.fromstringThe first day the 12-month count covers. window.to holds the last day.
data.sourcestringThe public dataset the record came from, for citing in a case file.
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. 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