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

# Return intake report + per-record outcomes for a batch.

> Return intake report + per-record outcomes for a batch.

    Outcomes are recorded by the pusher as it processes each queued record.
    A record may be in one of these terminal states:
      - pushed     : created/updated in Pipedrive (includes person/org/deal ids)
      - deduped    : PD already had a match by LI URL or email; nothing created
      - failed     : pusher saw a hard error and gave up after 3 attempts (DLQ)

    Records not yet processed appear as `pending` with their attempt count.



## OpenAPI

````yaml /openapi/private/specs/mcp/sagescreen.yml post /tools/contact_push_batch_status
openapi: 3.1.0
info:
  title: SageScreen — MCP Tool Catalog
  description: >-
    Agent-callable tools exposed by the SageScreen MCP server at
    `https://mcp.sagescreen.net`.


    These are the same tools served over the Model Context Protocol; this
    reference documents their **REST** surface (`POST /tools/{name}`, body = the
    tool's arguments), which is what the playground below invokes. The live,
    machine-readable catalog is `GET /tools/list`.


    **This page is generated deterministically** from the server's tool registry
    (`apps/docs/scripts/generate_mcp_spec.py`), not hand-written and not
    AI-generated — it cannot drift from the shipped tools.


    All calls authenticate with the `X-Service-Token` header (or `?token=`).
  version: 1.0.0
servers:
  - url: https://mcp.sagescreen.net
    description: Production MCP server
security:
  - serviceToken: []
  - tokenQuery: []
tags:
  - name: Agents
  - name: Contact Push
  - name: Image Generation
  - name: Other
  - name: Productlane
  - name: Reply.io
  - name: Sequences
  - name: Spaces
  - name: WordPress
paths:
  /tools/contact_push_batch_status:
    post:
      tags:
        - Contact Push
      summary: Return intake report + per-record outcomes for a batch.
      description: |-
        Return intake report + per-record outcomes for a batch.

            Outcomes are recorded by the pusher as it processes each queued record.
            A record may be in one of these terminal states:
              - pushed     : created/updated in Pipedrive (includes person/org/deal ids)
              - deduped    : PD already had a match by LI URL or email; nothing created
              - failed     : pusher saw a hard error and gave up after 3 attempts (DLQ)

            Records not yet processed appear as `pending` with their attempt count.
      operationId: contact_push_batch_status
      requestBody:
        required: true
        content:
          application/json:
            schema:
              properties:
                batch_id:
                  title: Batch Id
                  type: string
              required:
                - batch_id
              type: object
      responses:
        '200':
          description: >-
            Tool result. The shape is tool-specific; most tools return a JSON
            object, some a `{"result": ...}` envelope.
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '400':
          description: Bad arguments (unknown kwargs, malformed JSON body).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          description: Unknown tool name.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Tool raised an error during execution.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    ErrorResponse:
      type: object
      properties:
        error:
          type: string
          description: Human-readable error message.
        detail:
          type: string
          description: Optional additional context.
      required:
        - error
  responses:
    Unauthorized:
      description: Missing or invalid service token.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            error: Unauthorized
  securitySchemes:
    serviceToken:
      type: apiKey
      in: header
      name: X-Service-Token
    tokenQuery:
      type: apiKey
      in: query
      name: token

````