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

# Merged contact info for a person

> Narrow contact-info merger across Apollo, People Data Labs, and (when opted in) the caller's connected CRMs (HubSpot/Folk/Affinity). Accepts any subset of person-side identifiers (email, linkedin_url, name+company, phone, twitter_url, github_url, instagram_handle) and returns a merged `contact` with per-field provenance citing which sources supplied each value. Best for sales/CRM workflows that need name/title/company/email/phone for a known person. Charges sum of upstream provider costs plus a $0.05 lava-enrich markup. The sibling /enrich/profile endpoint returns a richer dossier (social, news, narrative).



## OpenAPI

````yaml /openapi.json post /enrich/contact
openapi: 3.0.0
info:
  title: Lava API
  description: >-
    Lava API enables businesses to implement usage-based billing for AI
    services. This API allows tracking, managing, and billing for third-party AI
    API usage through a forwarding system.
  version: 1.0.0
  contact:
    name: Lava support
    url: https://www.lava.so/contact
servers:
  - url: https://api.lava.so/v1/
    description: Lava API v1
security: []
tags:
  - name: Authentication
  - name: Core Endpoints
  - name: Models
  - name: Services
  - name: Requests
  - name: Wallet
  - name: Payment Methods
  - name: Spend Keys
  - name: Usage
  - name: Checkout Sessions
  - name: Customers
  - name: Plans
  - name: Subscriptions
  - name: Meters
  - name: Webhooks
  - name: Secret Keys
  - name: Credit Bundles
  - name: Gateway Settings
  - name: Skills
  - name: News Data
  - name: Search
  - name: Enrich
paths:
  /enrich/contact:
    post:
      tags:
        - Enrich
      summary: Merged contact info for a person
      description: >-
        Narrow contact-info merger across Apollo, People Data Labs, and (when
        opted in) the caller's connected CRMs (HubSpot/Folk/Affinity). Accepts
        any subset of person-side identifiers (email, linkedin_url,
        name+company, phone, twitter_url, github_url, instagram_handle) and
        returns a merged `contact` with per-field provenance citing which
        sources supplied each value. Best for sales/CRM workflows that need
        name/title/company/email/phone for a known person. Charges sum of
        upstream provider costs plus a $0.05 lava-enrich markup. The sibling
        /enrich/profile endpoint returns a richer dossier (social, news,
        narrative).
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/EnrichRequestBody'
      responses:
        '200':
          description: >-
            Merged contact record. `contact` is null when the fanout returned
            candidates but no confident match was found — the markup is still
            charged because the work was performed.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/EnrichContactResponse'
        '400':
          description: >-
            Person identifier missing (e.g. domain-only or company-only input)
            or request body invalid.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '502':
          description: >-
            Every enabled enrich provider failed. No merger attempted, no markup
            charged.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - Auth: []
components:
  schemas:
    EnrichRequestBody:
      type: object
      description: >-
        Person identifiers for /v1/enrich/contact and /v1/enrich/profile. At
        least one strong identifier (email, linkedin_url, phone, twitter_url,
        github_url, instagram_handle) OR name+company is required. Domain-only
        or company-only input returns 400.
      properties:
        email:
          type: string
          nullable: true
        linkedin_url:
          type: string
          nullable: true
        name:
          type: string
          nullable: true
        company:
          type: string
          nullable: true
        phone:
          type: string
          nullable: true
        twitter_url:
          type: string
          nullable: true
          description: >-
            Twitter/X profile URL. When supplied, /profile additionally fans out
            to Apify Twitter scraper.
        github_url:
          type: string
          nullable: true
          description: >-
            GitHub profile URL. When supplied, /profile additionally fans out to
            Apify GitHub scraper.
        instagram_handle:
          type: string
          nullable: true
          description: >-
            Instagram handle (with or without @ prefix). When supplied, /profile
            additionally fans out to Apify Instagram scraper.
        include_connected_crms:
          type: boolean
          nullable: true
          description: >-
            Opt-in flag for adding the caller's connected CRMs
            (HubSpot/Folk/Affinity) to the fanout. Only adapters for services
            the caller has actually connected are added; opt-in does not fan out
            to the universe of CRMs.
    EnrichContactResponse:
      type: object
      properties:
        contact:
          nullable: true
          allOf:
            - $ref: '#/components/schemas/MergedContact'
        sources_failed:
          type: array
          items:
            $ref: '#/components/schemas/EnrichSourceFailed'
        available_connections:
          type: array
          items:
            type: string
          description: >-
            CRM service names the caller has connected (hubspot, folk,
            affinity). Returned regardless of opt-in so callers can discover
            what's available.
        cost:
          $ref: '#/components/schemas/EnrichCost'
      required:
        - contact
        - sources_failed
        - available_connections
        - cost
    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            message:
              type: string
              description: Human-readable error message describing what went wrong
              example: Invalid authentication credentials
            code:
              type: string
              description: Machine-readable error code describing what went wrong
              example: forward_token_json_invalid
            status:
              type: integer
              description: HTTP status code of the error
              example: 400
            issues:
              type: array
              items:
                type: object
                properties:
                  path:
                    type: array
                    items:
                      type: string
                    description: Path to the field that caused the validation error
                  message:
                    type: string
                    description: Error message describing the validation issue
                required:
                  - path
                  - message
              description: >-
                Optional array of specific validation issues with their paths
                and messages
              example:
                - path:
                    - model
                  message: 'Missing required field: model'
                - path:
                    - messages
                    - '0'
                    - content
                  message: Invalid message content format
          required:
            - message
            - code
            - status
      required:
        - error
    MergedContact:
      type: object
      description: >-
        Merged contact record with per-field provenance. Fields are null when
        the merger had no confident value. `provenance` maps each populated
        field to the array of source ids that contributed.
      properties:
        name:
          type: string
          nullable: true
        first_name:
          type: string
          nullable: true
        last_name:
          type: string
          nullable: true
        title:
          type: string
          nullable: true
        company:
          type: string
          nullable: true
        company_domain:
          type: string
          nullable: true
        email:
          type: string
          nullable: true
        linkedin_url:
          type: string
          nullable: true
        phone:
          type: string
          nullable: true
        location:
          type: string
          nullable: true
        twitter_url:
          type: string
          nullable: true
        github_url:
          type: string
          nullable: true
        bio:
          type: string
          nullable: true
        provenance:
          type: object
          additionalProperties:
            type: array
            items:
              type: string
        confidence:
          type: number
    EnrichSourceFailed:
      type: object
      properties:
        provider:
          type: string
        reason:
          type: string
      required:
        - provider
        - reason
    EnrichCost:
      type: object
      description: >-
        Cost breakdown returned on every successful or no-match response.
        `markup` is the flat lava-enrich fee; `breakdown` lists each upstream
        provider's cost as reported by its adapter; `total` is markup +
        sum(breakdown).
      properties:
        total:
          type: string
        markup:
          type: string
        breakdown:
          type: object
          additionalProperties:
            type: string
      required:
        - total
        - markup
        - breakdown
  securitySchemes:
    Auth:
      type: http
      scheme: bearer
      description: >-
        Bearer token authentication used for standard API calls. Format: 'Bearer
        YOUR_API_KEY'

````