ActiveCampaign Most Recent Count History API

The Most Recent Count History API from ActiveCampaign — 1 operation(s) for most recent count history.

Operations 1

GET /api/3/segmentsV2/count-history Retrieve the most recent result count for the given segments that were ran without an AdditionalCriteria #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/activecampaign-most-recent-count-history-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

activecampaign-most-recent-count-history-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Segments Most Recent Count History API
  description: API for managing segments in your ActiveCampaign instance
  version: 2.0.0
  contact:
    name: ActiveCampaign Support
    url: https://www.activecampaign.com
servers:
- url: https://{yourAccountName}.api-us1.com
  description: US-based Users
  variables:
    yourAccountName:
      default: yourAccountName
security:
- Api_Key: []
tags:
- name: Most Recent Count History
paths:
  /api/3/segmentsV2/count-history:
    get:
      operationId: get_recent_count_history
      tags:
      - Most Recent Count History
      summary: Retrieve the most recent result count for the given segments that were ran without an AdditionalCriteria
      description: One result per segment will be returned. Pagination not supported. Maximum 100 segmentIds per request. SegmentIds in the request that doesn't exist, will simply be ignored
      parameters:
      - name: segmentIds
        in: query
        description: 'A comma separated list of segmentId''s. Example: id1,id2,id24,uuid-string,id5454'
        required: true
        schema:
          type: string
      responses:
        '200':
          description: An array of segment count history results
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SegmentCountHistoryResponseRootDO'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponseRootDO'
        '401':
          description: Unauthorized
        '403':
          description: Forbidden
components:
  schemas:
    ErrorSourceDO:
      title: ErrorSourceDO
      type: object
      properties:
        pointer:
          type: string
    SegmentCountHistoryResponseRootDO:
      title: SegmentCountHistoryResponseRootDO
      type: object
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/SegmentCountHistoryDataDO'
        errors:
          type: array
          items:
            $ref: '#/components/schemas/ErrorDetailDO'
    SegmentCountHistoryDataDO:
      title: SegmentCountHistoryDataDO
      type: object
      properties:
        attributes:
          $ref: '#/components/schemas/SegmentCountHistoryAttributeDO'
        id:
          type: string
          description: Epoch timestamp the count was recorded at
        type:
          type: string
          enum:
          - SegmentCountHistory
    SegmentCountHistoryAttributeDO:
      title: SegmentCountHistoryAttributeDO
      required:
      - timestamp
      - segment_id
      - segment_hash
      - run_id
      - result_count
      type: object
      properties:
        timestamp:
          type: string
          description: ISO 8601 datetime representing when the when the result count wos recorded
          format: date-time
          example: '2020-04-12T23:20:50.523Z'
        segment_id:
          type: string
        segment_hash:
          type: string
          description: A hash of the segment's logic. A changes in the hash over time indicate when the segment was modified
          format: string
          example: 97f75f368e9908fd88f4543a9c61a2812915b62e70bf3a7edef01acdeb81b4c5
        run_id:
          type: string
          description: A unique value that identifies a segment's evaluation request
          example: 52701258-d47e-4e5a-81e5-cff878c69bf8
        result_count:
          type: number
          description: The number of matches found for this segment's evaluation request
        active_result_count:
          type: number
          description: The number of matches found for this segment's evaluation request AND are subscribed to at least one list
        count_updating_with_runid:
          type: string
          description: if the current count is being updated, this is the runid that update is waiting on
          example: 52701258-d47e-4e5a-81e5-cff878c69bf8
      description: Object that summarises the results of a segment's evaluation request
    ErrorDetailDO:
      title: ErrorDetailDO
      type: object
      properties:
        code:
          type: string
        detail:
          type: string
        source:
          $ref: '#/components/schemas/ErrorSourceDO'
        status:
          type: string
        title:
          type: string
    ErrorResponseRootDO:
      title: ErrorResponseRootDO
      type: object
      properties:
        errors:
          type: array
          items:
            $ref: '#/components/schemas/ErrorDetailDO'