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

# List leads with their source mention

> Leads joined to the mention that produced them, which carries the public post URL.

A platform-scoped credential may call this against another agency’s workspace.



## OpenAPI

````yaml /openapi.json post /api/functions/listLeadsWithMentions
openapi: 3.1.0
info:
  title: Reputably API
  version: 1.0.0
  description: >-
    The HTTP surface an agent credential can reach. It is read plus safe writes:
    you can read your reputation data, generate drafts, queue reports and run
    first-time tracking setup. You cannot send anything to an external platform,
    trigger syncs, touch billing or manage credentials.


    The same endpoints back the MCP server, so anything documented here is
    reachable both ways.
servers:
  - url: https://app.reputably.net
    description: Reputably
  - url: https://your-domain.example
    description: Your own verified white-label domain
security:
  - agentKey: []
tags:
  - name: Businesses
    description: The locations you track, their plan usage and AI-generated insights.
  - name: Reviews
    description: Google and Facebook reviews, including which still need a reply.
  - name: Brand mentions
    description: Mentions across X, Reddit, YouTube, Facebook communities and the open web.
  - name: Brand tracking
    description: The trackers that find mentions, and competitor share of voice.
  - name: Leads
    description: Buying signals detected in mentions, with the public post to reply to.
  - name: AI Visibility
    description: >-
      Whether AI assistants recommend the business, what they cite, and how it
      moves.
  - name: AI Traffic
    description: Which AI crawlers read the website, and who arrives from an AI answer.
  - name: Posts
    description: Google Business Profile posts and drafts.
  - name: Reports
    description: Queued report renders and their CSV output.
  - name: Setup
    description: First-time tracking configuration.
  - name: Account
    description: Workspaces, notifications, sync status and prospect audits.
paths:
  /api/functions/listLeadsWithMentions:
    post:
      tags:
        - Leads
      summary: List leads with their source mention
      description: >-
        Leads joined to the mention that produced them, which carries the public
        post URL.


        A platform-scoped credential may call this against another agency’s
        workspace.
      operationId: listLeadsWithMentions
      parameters:
        - name: X-Workspace-Id
          in: header
          required: false
          schema:
            type: string
          description: >-
            Which workspace to read. Omit it and you get the account’s home
            workspace, which on an agency account is often not where the live
            businesses are. A workspace this credential cannot read is refused
            with 403 rather than quietly answered from the default.
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                stage:
                  type: string
                  description: Lead stage to filter to, for example new.
                location_id:
                  type: string
                  description: Business id to filter to.
                include_archived:
                  type: boolean
                  description: Include archived leads.
                limit:
                  type: integer
                  description: Maximum rows to return.
                sort:
                  type: string
                  description: Sort axis.
                skip:
                  type: integer
                  description: Rows to skip, for paging.
                days:
                  type: integer
                  description: Only leads detected within this many days.
      responses:
        '200':
          description: Success.
          content:
            application/json:
              schema:
                type: object
        '401':
          description: Missing or invalid credential.
        '403':
          description: >-
            This function is not callable by an agent credential, or not in this
            workspace.
components:
  securitySchemes:
    agentKey:
      type: http
      scheme: bearer
      description: >-
        An agent key (`rpk_...`) created in Settings → API & MCP, sent as
        `Authorization: Bearer rpk_...`. Bearer only: a cookie session can never
        drive this API. An OAuth 2.1 access token obtained from the same host
        works identically and lands on the same ceiling.

````