CFPB Consumer Complaints - Company Complaint Profiles

Look up how many consumer complaints a US bank, card issuer, lender, debt collector or credit bureau has received, what they are about, how the company answered and how the volume moves month by month. Data comes straight from the official CFPB Consumer Complaint Database open-data API. No scraping, no API key.

Two modes:

• summary - one profile per company (counts, top products and issues, company response types, timely-response rate, top states, submission channels, monthly trend).
• complaints - the individual complaints, newest first (product, issue, dates, state, 3-digit ZIP prefix, company response, link to the CFPB page).

Input

{
  "companies": ["Wells Fargo", "Capital One"],
  "mode": "summary",
  "products": ["Mortgage"],
  "states": ["CA", "TX"],
  "dateFrom": "2025-01-01",
  "dateTo": "2025-12-31",
  "maxResults": 5
}

All fields are optional; with an empty input the Actor summarizes an example company (Wells Fargo) over the last 12 months.

• companies - partial names, at least 3 characters. The text is matched against the company names CFPB uses (for example "wells fargo" finds WELLS FARGO & COMPANY; "chase" finds JPMORGAN CHASE & CO.). Names that contain your whole text come first. matchType tells you whether the match was the whole text (phrase) or all words (words).
• products - CFPB product names, case does not matter (a unique part of a name is enough). Use Product•Sub-product for a sub-product. Unknown names are rejected with the list of valid ones.
• states - the consumer's state, two letters.
• dateFrom / dateTo - the date CFPB received the complaint, both days included. If both are empty the last 12 calendar months (including the current one) are used and period.defaultedToLast12Months is true. If only dateTo is given there is no start limit (the monthly trend covers the last 60 months).
• maxResults - per company name. Summary mode: how many matching companies are summarized (1-25, default 5, most complaints first). Complaints mode: how many complaints are returned (1-10000, default 100, newest first).

Output

Summary row (type: company_summary)

company, complaintCount, period, filters, timelyResponse (yes, no, ratePct), responseTypes[], monetaryReliefPct, anyReliefPct (monetary or non-monetary relief), topProducts[], topIssues[], topStates[] (top 10 each, with count and pct), submittedVia[], monthlyTrend[] (month, count, partialMonth when the period starts or ends mid-month), dataAsOf, source, license, disclaimer.

Notes on the numbers:

• ratePct is the share of complaints with a timely company response among those where CFPB records the answer. Complaints still In progress appear in responseTypes and in complaintCount.
• When you filter by product or state, the distribution of that dimension is counted value by value, because CFPB's own breakdown ignores its own filter (verified; a naive read would show all products).
• The monthly trend needs one request per month, so a 12-month summary takes about 15 requests.

Complaint row (type: complaint)

complaintId, complaintUrl, company, dateReceived, dateSentToCompany, product, subProduct, issue, subIssue, state, zip3, tags (for example Older American, Servicemember), submittedVia, companyResponse, companyPublicResponse, timelyResponse, dataAsOf, source, license, disclaimer.

No silent failures

• A name that matches nothing is returned as found: false with a reason (not charged).
• If the CFPB API cannot be reached the row has found: null, an error, and says that this does not mean the company has no complaints (not charged).
• If only the monthly trend fails, the summary is still returned, monthlyTrend is null and sectionErrors explains why. If monthly counts do not add up to the total (data changed during the run) that is reported in sectionErrors too.

Privacy warning

The database contains no consumer names or street addresses, and this Actor outputs only the state and the first three digits of the ZIP code. The CFPB database can also publish consumers' free-text narratives (CFPB removes personal information before publishing). The public API currently returns no narrative field at all, so this Actor outputs none. If CFPB adds narratives, they will appear as narrative exactly as published; free text can still contain personal identifiers that the scrubbing missed, so do not try to identify or contact complainants, and treat any narrative as sensitive data.

Important: what the numbers mean

Complaints are consumer assertions, not verified facts or findings against the company. CFPB states: "This database is not a statistical sample of consumers' experiences in the marketplace and these complaints are not necessarily representative of all consumers' experiences with a financial product or company." and "When looking at complaint volume about a company or product, consider company size and/or market share." Complaints referred to other regulators (for example about depository institutions with less than $10 billion in assets) are not published. A low count does not mean low harm. Do not use this data alone to make lending, hiring or legal decisions.

Data source

CFPB Consumer Complaint Database search API (https://www.consumerfinance.gov/data-research/consumer-complaints/search/api/v1/). The API metadata and OpenAPI description state the license: Creative Commons CC0. The database is updated about daily; dataAsOf is the API's last_updated value. This Actor is not affiliated with or endorsed by the CFPB.

Pricing

Pay-per-event, event name cfpb-record (one company summary or one complaint returned). Names that are not found and error rows are not charged. The Actor respects your maximum cost per run.

Limits

• Maximum 10 company names per run; 60 months of monthly trend; 10000 complaints per name.
• The CFPB site sits behind a firewall that blocks unknown client identifiers; if CFPB blocks the platform's network the rows come back with found: null and a clear error.