> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pathors.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List outbound campaigns

> A project's outbound campaigns, newest created first — use it to find the campaign to pull dispatches for. `limit` defaults to 20, max 100; for just the latest campaign, pass `limit=1`. Ordered by creation time rather than last update: the scheduler rewrites a campaign throughout a run, so an older campaign still dialing would otherwise outrank one created today. The contact counts let a client decide whether a campaign is worth pulling dispatches for without fetching them first.



## OpenAPI

````yaml https://api.pathors.com/openapi.json get /v1/campaigns
openapi: 3.1.0
info:
  title: Pathors API
  description: >-
    Public developer API for the Pathors platform. Authenticate with a developer
    key (`Authorization: Bearer dk_...`) created from the dashboard. See
    [docs.pathors.com](https://docs.pathors.com) for guides.
  version: 1.0.0
  contact:
    name: Pathors Support
    url: https://app.pathors.com/support
servers:
  - url: https://api.pathors.com
    description: Production
  - url: http://localhost:8080
    description: Local development
security:
  - developerKey: []
tags:
  - name: Projects
    description: CRUD for projects owned by the authenticated developer
  - name: Agent Config
    description: Read and update a project's agent configuration and versions
  - name: Pathway
    description: Manage a project's pathway graph — nodes and decision edges
  - name: Chat
    description: OpenAI-compatible chat completions for a project agent
  - name: Sessions
    description: Create, search, terminate, and inspect agent sessions
  - name: Session History
    description: Browse and inspect persisted session history
  - name: Tools
    description: Manage a project's tools and inspect available tool types
  - name: Knowledgebases
    description: Manage knowledgebases and query them for relevant chunks
  - name: Datasets
    description: Upload and manage source files embedded into a knowledgebase
  - name: Test Cases
    description: CRUD for agent test cases
  - name: Test Suites
    description: Group test cases, run them, and read results
  - name: Webhooks
    description: Manage webhook subscriptions for project events
  - name: Calls
    description: Place outbound voice calls from a project agent
  - name: Campaigns
    description: Create and activate outbound campaigns that dial a call list
paths:
  /v1/campaigns:
    get:
      tags:
        - Campaigns
      summary: List outbound campaigns
      description: >-
        A project's outbound campaigns, newest created first — use it to find
        the campaign to pull dispatches for. `limit` defaults to 20, max 100;
        for just the latest campaign, pass `limit=1`. Ordered by creation time
        rather than last update: the scheduler rewrites a campaign throughout a
        run, so an older campaign still dialing would otherwise outrank one
        created today. The contact counts let a client decide whether a campaign
        is worth pulling dispatches for without fetching them first.
      operationId: getV1Campaigns
      responses:
        '200':
          description: Campaigns, newest first
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: array
                    items:
                      type: object
                      properties:
                        campaign_id:
                          type: string
                        name:
                          type: string
                        status:
                          type: string
                          enum:
                            - draft
                            - active
                            - completed
                        stopped_reason:
                          anyOf:
                            - type: string
                            - type: 'null'
                        created_at:
                          type: string
                        updated_at:
                          type: string
                        total_contacts:
                          type: number
                        dispatched_contacts:
                          type: number
                        completed_contacts:
                          type: number
                        connected_contacts:
                          type: number
                      required:
                        - campaign_id
                        - name
                        - status
                        - stopped_reason
                        - created_at
                        - updated_at
                        - total_contacts
                        - dispatched_contacts
                        - completed_contacts
                        - connected_contacts
                required:
                  - data
        '400':
          description: Missing `project_id`, or bad `status` / `limit`
          content:
            application/json:
              schema:
                anyOf:
                  - type: object
                    properties:
                      error:
                        type: string
                    required:
                      - error
                  - type: object
                    properties:
                      error:
                        type: object
                        properties:
                          message:
                            type: string
                          code:
                            type: string
                          details:
                            type: object
                            propertyNames:
                              type: string
                            additionalProperties: {}
                        required:
                          - message
                    required:
                      - error
        '401':
          description: Error response
          content:
            application/json:
              schema:
                anyOf:
                  - type: object
                    properties:
                      error:
                        type: string
                    required:
                      - error
                  - type: object
                    properties:
                      error:
                        type: object
                        properties:
                          message:
                            type: string
                          code:
                            type: string
                          details:
                            type: object
                            propertyNames:
                              type: string
                            additionalProperties: {}
                        required:
                          - message
                    required:
                      - error
        '403':
          description: No access to the project
          content:
            application/json:
              schema:
                anyOf:
                  - type: object
                    properties:
                      error:
                        type: string
                    required:
                      - error
                  - type: object
                    properties:
                      error:
                        type: object
                        properties:
                          message:
                            type: string
                          code:
                            type: string
                          details:
                            type: object
                            propertyNames:
                              type: string
                            additionalProperties: {}
                        required:
                          - message
                    required:
                      - error
        '500':
          description: Error response
          content:
            application/json:
              schema:
                anyOf:
                  - type: object
                    properties:
                      error:
                        type: string
                    required:
                      - error
                  - type: object
                    properties:
                      error:
                        type: object
                        properties:
                          message:
                            type: string
                          code:
                            type: string
                          details:
                            type: object
                            propertyNames:
                              type: string
                            additionalProperties: {}
                        required:
                          - message
                    required:
                      - error
components:
  securitySchemes:
    developerKey:
      type: http
      scheme: bearer
      bearerFormat: Developer key (dk_...)
      description: Developer key created from the dashboard (Settings → Developer Keys)

````