Skip to main content
GET
A competitor’s customers. Clustr finds them on the competitor’s own website and LinkedIn posts, and keeps the evidence behind each one: the page, the quote and the people found. Each piece of evidence is a signal with a weight: A company named as an investor, partner, integration or technology, the competitor itself, you, or another competitor you track is never a customer, whatever else is found. The score adds the weight of each signal once, capped at 100, and gives the label:
  • confirmed: 80 or more (one strong signal), or confirmed by you.
  • likely: 50 to 79.
  • possible: under 50. Hidden unless you pass include_possible=true.
Each customer also has its signals (each with the page or post that shows it), its contacts (found_via: testimonial, tagged in a post, buying_committee for people who engaged with the competitor’s post about the customer, cs_counterpart for the people its CS reps engage), any renewal_date you set, possible_churn when the evidence was removed from the competitor’s site, and two flags: in_crm when the company is in your CRM, and is_customer_of_ours when it is also your customer. When your CRM has the company (matched on its domain), owner_name, owner_email, cs_owner_name and cs_owner_email name its account owner and CS owner. confidence names the strongest kind of evidence and sources the kinds of evidence seen; renewal_window_start and renewal_window_end are always null. Customers you rejected are left out unless you pass include_rejected=1. To read every competitor’s customers in one list, use List All Competitor Customers. For the people at one customer, and the ones you can reach there, use List Competitor Customer People.

Authorizations

​
Authorization
string
header
required

The API key you created on the API settings page of the Clustr app.

Path Parameters

​
id
string
required

The competitor's Clustr ID (cmp_…), from List Competitors. The id from earlier responses also works.

Query Parameters

​
company
string

Keeps the customers at this company, by its name. Repeat it for several companies (a name may hold a comma, so it is never split).

​
label
string

Keeps the customers with these labels, as a comma-separated list of confirmed, likely and possible. Defaults to confirmed,likely. possible also needs include_possible.

​
include_possible
enum<string>

true also lists possible customers, the ones with only a weak signal.

Available options:
0,
1,
true,
false
​
signal
string

Keeps the customers with at least one of these signals, as a comma-separated list: case_study, testimonial, post_announcement, post_webinar, post_highlight, logo_wall, cs_interaction or product_user_comment.

​
include_rejected
enum<string>

Set to 1 to also list the customers you rejected.

Available options:
0,
1
​
order
enum<string>

standing lists your own customers first, then the companies in your CRM, then the rest in the default order.

Available options:
standing
​
owner
string

Keeps the customers whose CRM account owner or CS owner has this email address. Customers are matched to your CRM on their domain.

​
cs_owner
string

Keeps the customers whose CS owner has this email address: the CS owner set in Clustr, or else the one in your CRM.

​
limit
integer
default:100

The number of customers per page, at most 500.

Required range: x <= 500
​
offset
integer
default:0

The number of customers to skip, for paging.

Response

One page of the competitor's customers

​
success
boolean
required
Example:

true

​
data
object
required