Suspects

Entity›Relationship›CommercialRelationship.Suspect

A Suspect is the earliest stage of the sales funnel — an unqualified contact that may or may not become a customer. Use Suspects to capture raw lead-generation output (form fills, list imports, scraped contacts) before the data is verified or qualified into a Lead.

The TribeCRM commercial funnel is: Suspect → Lead → HotProspect → Prospect → Customer.

Two variants

• Organisation Suspect — Relationship_Organization_CommercialRelationship_Suspect — when the suspect is a company.
• Person Suspect — Relationship_Person_CommercialRelationship_Suspect — when the suspect is an individual (B2C).

Both share the same fields and lifecycle; the only difference is which Relation subtype is linked (Organization vs Person).

Endpoints

List Suspects

Retrieve a paginated list of suspects.

Organisation (B2B)

GET/v1/odata/Relationship_Organization_CommercialRelationship_Suspect

Person (B2C)

GET/v1/odata/Relationship_Person_CommercialRelationship_Suspect

Single Suspect

Retrieve a single suspect by its ID.

Organisation (B2B)

GET/v1/odata/Relationship_Organization_CommercialRelationship_Suspect({id})

Person (B2C)

GET/v1/odata/Relationship_Person_CommercialRelationship_Suspect({id})

Create Suspect with a New Relation

Create a suspect relationship and its underlying Organisation or Person in one call.

Organisation (B2B)

POST/v1/odata/Relationship_Organization_CommercialRelationship_Suspect

Person (B2C)

POST/v1/odata/Relationship_Person_CommercialRelationship_Suspect

• Relation.ID — The parent Relation (typically your own organisation).
• Organization / Person — The child Relation fields (created automatically). For Person, LastName is mandatory.

Create Suspect from an Existing Relation

Link an existing Organisation or Person as a suspect.

Organisation (B2B)

POST/v1/odata/Relationship_Organization_CommercialRelationship_Suspect

Person (B2C)

POST/v1/odata/Relationship_Person_CommercialRelationship_Suspect

Update Suspect

Update an existing suspect relationship. Provide only the fields to update.

Organisation (B2B)

PUT/v1/odata/Relationship_Organization_CommercialRelationship_Suspect({id})

Person (B2C)

PUT/v1/odata/Relationship_Person_CommercialRelationship_Suspect({id})

Convert Suspect to next funnel stage

Promote a Suspect to a Lead, HotProspect, Prospect, or Customer by changing its _Type. All linked activities, notes, and history are preserved.

Organisation (B2B)

POST/v1/odata/Relationship_Organization_CommercialRelationship_Suspect

Person (B2C)

POST/v1/odata/Relationship_Person_CommercialRelationship_Suspect

Use the Relationship ID, not any of the Relation IDs.

note

Type conversion only works within the same Relation type: an Organisation Suspect can become an Organisation Lead/Prospect/Customer, a Person Suspect can become a Person Lead/Prospect/Customer. You cannot cross-convert between Organisation and Person variants.

Delete Suspect

Delete a suspect relationship by ID. This removes the suspect role but does not delete the underlying Organisation or Person.

Organisation (B2B)

DELETE/v1/odata/Relationship_Organization_CommercialRelationship_Suspect({id})

Person (B2C)

DELETE/v1/odata/Relationship_Person_CommercialRelationship_Suspect({id})

Fields

Standard Fields (all entities)

Field	Type	Description
ID	Guid	Primary key (UUID)
_Type	String	Entity type discriminator (Relationship.Organization.CommercialRelationship.Suspect or Relationship.Person.CommercialRelationship.Suspect)
_Name	String	Computed display name
SortIndex	Double	Sorting order
CreationDate	DateTimeOffset	Date the record was created
LastMutationDate	DateTimeOffset	Date of the last modification
IsActive	Boolean	Whether the record is active
IsClosed	Boolean	Whether the record is closed

Suspect Fields

Field	Type	Description
Name	String	Suspect display name

Relationships

Relationship	Target Entity	Cardinality	Description
Relation	Relation	N:1	Parent relation (your organisation)
Organization	Relation.Organization	N:1	B2B only: the suspect organisation
Person	Relation.Person	N:1	B2C only: the suspect person
Status	Datastore	N:1	Suspect status

Expanding Relationships

GET/v1/odata/Relationship_Organization_CommercialRelationship_Suspect({id})?$expand=Organization

GET/v1/odata/Relationship_Person_CommercialRelationship_Suspect({id})?$expand=Person

Navigating Relationships

GET/v1/odata/Relationship_Organization_CommercialRelationship_Suspect({id})/Relation

Filtering Examples

The same $filter syntax applies to both Organisation and Person variants — substitute the entity URL accordingly.

GET/v1/odata/Relationship_Organization_CommercialRelationship_Suspect?$filter=contains(Name, '{Name}')&$top={top}

GET/v1/odata/Relationship_Person_CommercialRelationship_Suspect?$filter=CreationDate gt {CreationDate}&$top={top}

GET/v1/odata/Relationship_Organization_CommercialRelationship_Suspect?$filter=IsClosed eq {IsClosed}&$top={top}

Custom Query

Build your own OData query against Relationship_Organization_CommercialRelationship_Suspect. Open Run and edit the whole request inline — swap the entity set, change the $filter, or add $expand, $select, $orderby, $top, $skip. Type $ for suggestions; use ↺ Reset to restore this example.

GET/v1/odata/Relationship_Organization_CommercialRelationship_Suspect?$top=10