CRM

Get a list's sharing state (+ owner display, canManageSharing)

GET
/v1/crm/lists/{id}/shares

Authorization

x-api-key<token>

In: header

Path Parameters

id*string

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/v1/crm/lists/string/shares"
{
  "data": {
    "canManageSharing": true,
    "orgWidePermission": "viewer",
    "owner": {
      "email": "string",
      "image": "string",
      "name": "string",
      "userId": "string"
    },
    "ownerUserId": "string",
    "shares": [
      {
        "createdAt": 0,
        "email": "string",
        "id": "string",
        "image": "string",
        "invitedByName": "string",
        "name": "string",
        "permission": "owner",
        "userId": "string"
      }
    ],
    "visibility": "private"
  }
}
{
  "error": "string"
}
{
  "error": "string"
}
{
  "error": "string"
}
{
  "error": "string"
}
{
  "error": "string",
  "limit": 0,
  "size": 0
}
{
  "error": "string"
}

Find the records in a CRM list that have Market-Insights updates to review POST

Checks a CRM list's members against current Market-Insights data and returns ONLY the records that need attention, each with its proposed updates. Use this instead of calling `getCrmRecordProfile` + `getCrmMiUpdates` for every member: one call covers a page of up to 50 members, and records the user already reviewed (applied or dismissed) with nothing new since are left out. Page with `cursor` until `nextCursor` is null; a page may return no records and still have more to scan. Act on the results with `applyCrmListMiUpdates` (explicit per-record accepted updates) and `dismissCrmListMiUpdates` (snooze the rest). Each scan counts as a check of those records, exactly like `getCrmMiUpdates`.

Compute which Market-Insights fields differ from a record snapshot POST

Next Page