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

# Find a person

> Looks up one respondent by `email` or `external_id`: who they are, their responses (newest first) and the MRR of the billing customers matched to them.



## OpenAPI

````yaml /openapi.json get /v1/people
openapi: 3.1.0
info:
  title: Rumorly API
  version: 1.0.0
  description: >-
    Send "how did you hear about us?" answers in; get channels, named entities
    and revenue out. All JSON is snake_case.
servers:
  - url: https://api.rumorly.io
    description: Production
security: []
tags:
  - name: Basics
  - name: Responses
    description: Answers and their classification.
  - name: Taxonomy
    description: Your channels and your dictionary of named entities.
  - name: People
    description: The people who answered.
  - name: Reports
    description: Revenue by self-reported channel.
  - name: Snippet
    description: Endpoints the JS snippet calls.
paths:
  /v1/people:
    get:
      tags:
        - People
      summary: Find a person
      description: >-
        Looks up one respondent by `email` or `external_id`: who they are, their
        responses (newest first) and the MRR of the billing customers matched to
        them.
      parameters:
        - schema:
            type: string
            format: email
          required: false
          description: The respondent's email (case-insensitive).
          name: email
          in: query
        - schema:
            type: string
          required: false
          description: Your id for the respondent. Pass both to require both to match.
          name: external_id
          in: query
      responses:
        '200':
          description: The person.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PersonDetail'
        '400':
          description: The body or query failed validation; `issues` says which field.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Missing or invalid API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '402':
          description: >-
            `plan_required`: your plan doesn't include API access (Growth and
            up; the signup trial does). `no_plan`: the workspace has no active
            plan (trial ended or subscription lapsed) and is paused until one is
            chosen. `quota_exceeded` (POST only): this month's response
            allowance is used up.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: >-
            The key is not allowed to do this (e.g. a publishable key reading
            data).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: Nobody with that email or external id in your workspace.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - secretKey: []
components:
  schemas:
    PersonDetail:
      type: object
      properties:
        id:
          type: string
          format: uuid
        email:
          type:
            - string
            - 'null'
        external_id:
          type:
            - string
            - 'null'
        name:
          type:
            - string
            - 'null'
        domain:
          type:
            - string
            - 'null'
        first_touch_channel:
          type:
            - string
            - 'null'
          description: >-
            The channel click-based analytics would credit (UTMs, referrer),
            when known.
        created_at:
          type: string
          format: date-time
        responses:
          type: array
          items:
            type: object
            properties:
              id:
                type: string
                format: uuid
              answer:
                type: string
              status:
                type: string
                enum:
                  - pending
                  - classified
                  - needs_review
                  - failed
              answered_at:
                type: string
                format: date-time
              channel:
                type:
                  - string
                  - 'null'
              entity:
                type:
                  - object
                  - 'null'
                properties:
                  id:
                    type: string
                    format: uuid
                  name:
                    type: string
                required:
                  - id
                  - name
              proposed_entity:
                type:
                  - string
                  - 'null'
              overridden:
                type: boolean
            required:
              - id
              - answer
              - status
              - answered_at
              - channel
              - entity
              - proposed_entity
              - overridden
          description: Their responses, newest first (up to 100).
        billing:
          type:
            - object
            - 'null'
          properties:
            mrr_cents:
              type: integer
            currency:
              type: string
            match_method:
              type: string
              enum:
                - id
                - email
                - domain
              description: >-
                How the strongest match was found: `id` (rumorly_id metadata),
                `email` or company `domain`.
            billing_customers:
              type: integer
          required:
            - mrr_cents
            - currency
            - match_method
            - billing_customers
          description: >-
            Their matched billing customers, summed; `null` when none is
            matched.
      required:
        - id
        - email
        - external_id
        - name
        - domain
        - first_touch_channel
        - created_at
        - responses
        - billing
      description: Example values are illustrative.
      example:
        id: 8a1d2c3b-4e5f-4a6b-8c7d-9e0f1a2b3c4d
        email: emily@acmeanalytics.com
        external_id: 8f2c91
        name: Emily Carter
        domain: acmeanalytics.com
        first_touch_channel: search
        created_at: '2026-10-20T14:03:11.000Z'
        responses:
          - id: 3f6c0a2e-5d1b-4f7a-9c2e-0b8d4e6a1f23
            answer: Heard Jake on Lenny's Podcast
            status: classified
            answered_at: '2026-10-20T14:03:11.000Z'
            channel: podcast
            entity:
              id: b7e6d5c4-3b2a-4190-8f7e-6d5c4b3a2910
              name: Lenny's Podcast
            proposed_entity: null
            overridden: false
        billing:
          mrr_cents: 49000
          currency: usd
          match_method: email
          billing_customers: 1
    Error:
      type: object
      properties:
        error:
          type: string
          example: invalid body
        code:
          type: string
        issues:
          type: array
          items:
            type: object
            properties:
              path:
                type: array
                items:
                  anyOf:
                    - type: string
                    - type: number
              message:
                type: string
            required:
              - path
              - message
      required:
        - error
  securitySchemes:
    secretKey:
      type: http
      scheme: bearer
      description: >-
        A secret key (`sk_live_…` / `sk_test_…`) from Settings → API keys.
        Server-side only.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.