CRM V4

Overview

Overview of V4MOS.AI CRM V4 API

The V4MOS.AI CRM V4 API exposes lead, opportunity, company, contact, and pipeline data synced from the V4 CRM (mars-sales) connected to your organization. Endpoints share the /v1/crm-v4 prefix and use the same authentication, pagination, and metadata envelope as every other V4MOS.AI integration.

Available Endpoints

Authentication

All endpoints require the x-client-id and x-client-secret headers, plus the organizationId query parameter. See Authentication.

Common Parameters

  • organizationId (required) – Organization that owns the CRM V4 integration
  • integrationId – Integration scope
  • page – Page number (default: 1)
  • limit – Records per page (default: 500, max: 5000)

Resource-Specific Filters

Leads (/v1/crm-v4/leads)

  • boardId, columnId, phaseType – Pipeline and stage filters
  • temperature, ownerId
  • createdStart / createdEnd – Creation date range

Opportunities (/v1/crm-v4/opportunities)

  • boardId, columnId, phaseType – Pipeline and stage filters
  • type – Board type (OPPORTUNITY, EXPANSION, ACQUISITION)
  • ownerId
  • createdStart / createdEnd – Creation date range

Companies (/v1/crm-v4/companies)

  • segment, tierType, ownerId
  • lastActivityStart / lastActivityEnd – Last activity range

Contacts (/v1/crm-v4/contacts)

  • companyId, ownerId

Pipelines (/v1/crm-v4/pipelines)

  • boardId
  • boardType – Board type (LEAD, OPPORTUNITY, EXPANSION, ACQUISITION)

Working With Stages

A card's stage is described by column_id + column_title + phase_type. Use phase_type for business logic — it is the stable, language-independent marker, while column_title is free text organizations can rename at any time. Join cards to /v1/crm-v4/pipelines on board_id + column_id to resolve stage ordering (column_order).

Pagination

Responses return meta.page, meta.limit, meta.hasNextPage, and meta.hasPreviousPage. Iterate while hasNextPage is true.

On this page