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

# Get Person

> Returns details for a single identified person

Returns the same acquisition attribution fields as [List People](https://docs.trywildcard.ai/api-reference/list-people.md),
including the stored referrer, UTM fields, and campaign history when available.


## OpenAPI

````yaml GET /v1/people/{id}
openapi: 3.0.3
info:
  title: Wildcard API
  description: >
    Programmatic access to your Wildcard data — identified website visitors,

    companies, events, and analytics.


    ## Authentication

    Visitor-data endpoints require an `mk_live_...` data key in `X-API-Key`.

    Partner management endpoints under `/v1/partner/*` require your
    `pk_live_...`

    management key instead. `/v1/health` is public and requires no key.


    ```bash

    curl -H "X-API-Key: mk_live_your_key_here"
    https://api-v1.maverickintelligence.co/v1/people

    ```


    ## Data API Rate Limiting

    - **1,000 requests per hour** per customer (shared across all API keys)

    - Every response includes `X-RateLimit-Limit` and `X-RateLimit-Remaining`
    headers

    - When exceeded, you'll receive a `429` response with a `Retry-After` header


    ## Pagination

    List endpoints use cursor-based pagination. Pass the `nextCursor` from the
    response

    as the `cursor` query parameter to fetch the next page.


    ## Sorting

    Visitor lists are sorted by most recently seen first (`lastSeen`
    descending).

    Traffic pages sort by observed human and AI page views, then domain and
    path.

    Custom sorting is not yet supported — passing a `sort` or `order` query

    parameter returns `400 bad_request`. Custom sorting options will be
    available

    in a future version.
  version: 1.1.0
  contact:
    name: Wildcard Support
    email: support@trywildcard.ai
    url: https://trywildcard.ai
servers:
  - url: https://api-v1.maverickintelligence.co
    description: Production
security:
  - ApiKeyAuth: []
tags:
  - name: Traffic
    description: >-
      Per-page human and AI traffic, including anonymous activity and server
      collection
  - name: System
    description: API health and status
  - name: People
    description: Identified website visitors
  - name: Events
    description: Behavioral events (page views, clicks, scrolls)
  - name: Companies
    description: Companies identified from visitors
  - name: Statistics
    description: Aggregate analytics
paths:
  /v1/people/{id}:
    get:
      tags:
        - People
      summary: Get a person
      description: |
        Returns details for a single identified person, including the
        `emailVerification` block and `emailStatus` summary from the ZeroBounce
        verification cache.
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
          description: Person ID
        - $ref: '#/components/parameters/exclude_bad_emails'
        - $ref: '#/components/parameters/domain_group_id'
      responses:
        '200':
          description: Person details
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    $ref: '#/components/schemas/Person'
        '404':
          description: Person not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  parameters:
    exclude_bad_emails:
      name: exclude_bad_emails
      in: query
      schema:
        type: boolean
        default: false
      description: >
        Blank any email field whose address is confirmed undeliverable (invalid,
        spamtrap, abuse, do_not_mail), matching what a verified CSV export does.
        The person is still returned, and `emailVerification` still reports the
        status, so you can see why a field came back empty. Addresses that are
        catch-all, unknown, or not yet verified are kept. Off by default — it
        empties fields existing integrations already read.
    domain_group_id:
      name: domain_group_id
      in: query
      schema:
        type: string
        pattern: ^[A-Za-z0-9][A-Za-z0-9_-]{0,63}$
      description: >
        Partner domain group ID. Matches exact member hostnames (www aliases
        normalized), including any member site the person has visited.
        Intersects domain, client_ref, and the key's scope; never grants extra
        access. Empty group returns zero matches; missing/foreign group returns
        404; invalid ID returns 400. Keep this filter when following pagination
        cursors.
      example: acme
  schemas:
    Person:
      type: object
      properties:
        id:
          type: string
        email:
          type: string
          nullable: true
          description: Raw primary email address
        businessEmail:
          type: string
          nullable: true
          description: Best classified business email (company-domain match preferred)
        personalEmail:
          type: string
          nullable: true
          description: Best classified personal email (gmail > outlook > yahoo)
        emailStatus:
          type: string
          enum:
            - valid
            - invalid
            - catch-all
            - unknown
            - spamtrap
            - abuse
            - do_not_mail
          description: >
            Deliverability status of the address you would actually contact
            (businessEmail, else personalEmail, else email). `unknown` when the
            address has not been verified yet.
        emailVerification:
          type: object
          description: >
            Cached ZeroBounce deliverability results, keyed by lowercased email
            address, covering every address in this response. Results come from
            the verification cache populated by verified exports — reading this
            endpoint never triggers a new verification, so an address that no
            export has covered reports `unknown` with a null `checkedAt`.
          additionalProperties:
            type: object
            properties:
              status:
                type: string
                enum:
                  - valid
                  - invalid
                  - catch-all
                  - unknown
                  - spamtrap
                  - abuse
                  - do_not_mail
              subStatus:
                type: string
                description: ZeroBounce sub-status detail (e.g. mailbox_not_found)
              checkedAt:
                type: string
                format: date-time
                nullable: true
                description: When this address was last verified; null if never
              stale:
                type: boolean
                description: >
                  True when the result is older than 90 days (or absent). Stale
                  entries are re-verified on the next verified export.
        firstName:
          type: string
          nullable: true
        lastName:
          type: string
          nullable: true
        title:
          type: string
          nullable: true
        company:
          type: string
          nullable: true
        location:
          type: string
          nullable: true
        region:
          type: string
          nullable: true
          enum:
            - USA
            - UK
            - EUR
            - Other
        linkedinUrl:
          type: string
          nullable: true
        phone:
          type: string
          nullable: true
          description: >-
            Best available phone number (DNC-filtered, matches dashboard
            display)
        profileImageUrl:
          type: string
          nullable: true
          description: Person's profile photo URL
        visitCount:
          type: integer
        firstSeen:
          type: string
          format: date-time
        lastSeen:
          type: string
          format: date-time
        isHotLead:
          type: boolean
        classifiedSeniority:
          type: string
          nullable: true
        classifiedJobFunction:
          type: string
          nullable: true
        trafficType:
          type: string
          nullable: true
          description: How the visitor arrived (organic, paid, direct, referral)
        adPlatform:
          type: string
          nullable: true
          description: >-
            Ad platform if traffic type is paid (google, facebook, linkedin,
            etc.)
        referrer:
          type: string
          nullable: true
          description: >-
            Stored referrer, usually a URL. Some providers supply a serialized
            referrer object. Null when unavailable; not necessarily the referrer
            of the latest visit.
        utmSource:
          type: string
          nullable: true
          description: >-
            Stored attribution source, from campaign tags or an inferred
            referrer source when available.
        utmMedium:
          type: string
          nullable: true
          description: Stored campaign medium, such as cpc or email.
        utmCampaign:
          type: string
          nullable: true
          description: Stored campaign name.
        utmTerm:
          type: string
          nullable: true
          description: Stored campaign keyword or term.
        utmContent:
          type: string
          nullable: true
          description: Stored campaign content or creative label.
        campaignHistory:
          type: array
          description: >
            Recorded campaign touches, oldest first, retaining up to 20 entries.
            Consecutive touches with the same campaign and platform are
            deduplicated; this is not a complete visit history. Empty when
            unavailable. Attribution fields retain the last meaningful campaign
            touch and may differ from the latest visit. Reading the API does not
            generate missing attribution.
          items:
            type: object
            properties:
              campaign:
                type: string
              platform:
                type: string
              trafficType:
                type: string
              source:
                type: string
                description: Marketing attribution source, not the identity-data provider.
              timestamp:
                type: string
                format: date-time
        trackedDomain:
          type: string
          nullable: true
          description: >
            Partner accounts: the tracked client domain this visitor was
            identified on. Omitted for non-partner accounts.
        clientRef:
          type: string
          nullable: true
          description: >
            Partner accounts: the partner's own label for the client that owns
            this visitor. Empty when the domain has no reference set.
        companyData:
          type: object
          nullable: true
          properties:
            companyId:
              type: string
            name:
              type: string
            domain:
              type: string
            standardizedIndustry:
              type: string
            location:
              type: string
            employeeCount:
              type: integer
    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            code:
              type: string
              enum:
                - unauthorized
                - forbidden
                - not_found
                - rate_limit_exceeded
                - bad_request
                - validation_error
                - invalid_cursor
                - internal_error
            message:
              type: string
            status:
              type: integer
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key
      description: 'API key in format: mk_live_{40 hex chars}'

````

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