Overview

The V4MOS.AI Exact Sales API gives you the raw records synced from the Exact Sales accounts connected to your organization: leads, sales, losses, stage and qualification history, lead UTMs, funnels, stages, sources, industries, discard reasons and users. Rows come as they were synced, with the warehouse column names (snake_case), so you can load them straight into your BI. All endpoints use the /v1/exact-sales prefix and the same authentication, pagination and response format.

Getting startedCopy Anchor Link

Base URL: https://data.v4mos.ai. Every call requires your API credentials and the organizationId — see Authentication.

1. Connect Exact Sales in app.v4mos.ai (Connected accounts) and wait for the first sync.
2. Call any endpoint below with your organizationId, for example GET /v1/exact-sales/leads?organizationId=….
3. Every row carries integration_id and integration_name: the connected account it came from. To read a single account, pass that value as integrationId.

Available endpointsCopy Anchor Link

• getLeads/v1/exact-sales/leadsOne row per lead: stage, funnel, closing forecast, source, sub-source, industry, SDR and sales rep.
• getSales/v1/exact-sales/salesOne row per sale closed from a lead: date, stage, cycle, total value and number of products.
• getLosses/v1/exact-sales/lossesOne row per lead marked as lost: when, at which stage and funnel, and why.
• getLead stage history/v1/exact-sales/lead-stage-historyOne row per stage move of a lead: origin and destination stage and funnel, cycle and discard data.
• getQualification history/v1/exact-sales/qualification-historyOne row per lead qualification: stage, cycle, score, meeting date and user action.
• getLead UTMs/v1/exact-sales/lead-utmsOne row per UTM parameter captured on a lead (key and value).
• getFunnels/v1/exact-sales/funnelsOne row per funnel, with an active flag.
• getStages/v1/exact-sales/stagesOne row per funnel stage: position, gate type and active flag.
• getSources/v1/exact-sales/sourcesOne row per lead source, with its type and sub-sources (JSON).
• getIndustries/v1/exact-sales/industriesOne row per industry leads can be classified in.
• getDiscard reasons/v1/exact-sales/discard-reasonsOne row per lead discard reason.
• getUsers/v1/exact-sales/usersOne row per user of the account: role and active flag.

ResourcesCopy Anchor Link

Pagination and filtersCopy Anchor Link

• page (default 1) and limit (default 500, max 5000). meta.hasNextPage says whether another page exists; rows come in a stable order, so walk the pages until it is false.
• dateFrom / dateTo (YYYY-MM-DD, inclusive) filter by the date column shown in the table above. Resources without one reject them.
• integrationId keeps the rows of one connected account.
• Answers are cached for 30 minutes and the data is synced once a day — see Data sync.

Response formatCopy Anchor Link

{
  "data": [{ "...": "one object per row, with the columns listed on each endpoint" }],
  "meta": {
    "page": 1,
    "limit": 500,
    "hasNextPage": true,
    "hasPreviousPage": false
  }
}

Amounts and large counters (fields with format: decimal or format: int64 in each endpoint schema) come as strings, e.g. "125.50", so no precision is lost. Convert them to a decimal type on your side.