SALEMARKET: Market
The SALEMARKET entity: A target market definition in the sales methodology, linking to buyer roles involved in that market segment.
SALEMARKET definition shipped with DemandFlow. Administrators can add, remove, rename, or re-type fields, change which ones are required, and alter the layout from the Definitions screen in Settings. Your tenant's current schema may differ from what is shown here. To read the current definition at any time, GET the DEFINITION object whose id matches SALEMARKET.Entity properties
| Property | Value |
|---|---|
| Entity code | SALEMARKET |
| Display name | Market |
| Plural | Markets |
| Level | 30000 |
Use cases
SALEMARKET defines a target market segment within the sales methodology framework. Markets are the top-level organising concept: each market has associated buyer roles (SALEROLE) linked via a multi-link relationship (SALESMARKET to SALEROLE). This hierarchy enables sales teams to define market-specific playbooks: for a given market, which buyer roles exist, what pains do those roles experience, and what talking points should reps use.
The relatedlist panel showing SALEROLE records with add-new and click-through capabilities allows sales leaders to build out the role map directly from the market record. The description field captures market characteristics, size, and targeting criteria. Products weighted against this market are shown via SALEPRODMKT junction entity queried on comboKey2.
Fields
Basics
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Market name |
description | text (multi-line) | Yes | Description |
Relationships
- Related lists:
SALEROLE(formatlink),SALEPRODMKT(formatSUB|SALEMARKET).
Creating a Market via the API
POST /v1/objects
Authorization: Bearer <your-pat>
Content-Type: application/json
{
"entity": "SALEMARKET",
"level": 30000,
"comboKey": "SUB:|ENT:",
"name": "Example name",
"description": "Example Description"
} Listing Markets records
GET /v1/entities/SALEMARKET/SUB