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

# Email to LinkedIn

> Resolve an email address to the highest-confidence LinkedIn profile URL when multiple candidates exist. Unlike `hem_to_linkedin`, which returns a slug, this endpoint scores all matching profiles and returns the single best full LinkedIn URL. Use this when email-to-LinkedIn match quality is critical — for example, before personalising outreach, triggering enrichment workflows, or appending LinkedIn data to a contact record.



## OpenAPI

````yaml /openapi.json post /email_to_linkedin
openapi: 3.1.0
info:
  title: MoltSets API
  version: 1.0.0
  description: >-
    Identity resolution API. Resolve emails, LinkedIn profiles, IP addresses,
    and emails into enriched contact and company data.
servers:
  - url: https://api.moltsets.com/api/v1/tools
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Search
    description: >-
      Search and filter company and business profiles by name, domain, industry,
      size, or revenue.
  - name: Get Valid Emails
    description: Resolve and enrich valid business and personal email addresses.
  - name: Get Carrier-Verified Mobile Phones
    description: Enrich carrier-verified mobile phone numbers.
  - name: Get Full Business Profile
    description: Resolve identifiers to full business profiles and company firmographics.
  - name: Get Ad Audience
    description: >-
      Resolve identifiers to hashed email (HEM) and mobile advertising IDs
      (MAIDs) for audience matching.
  - name: Get Company
    description: Resolve IP addresses to company data.
  - name: Account
    description: Account management tools. Free — do not consume credits.
paths:
  /email_to_linkedin:
    post:
      tags:
        - Get LinkedIn
      summary: Email to LinkedIn
      description: >-
        Resolve an email address to the highest-confidence LinkedIn profile URL
        when multiple candidates exist. Unlike `hem_to_linkedin`, which returns
        a slug, this endpoint scores all matching profiles and returns the
        single best full LinkedIn URL. Use this when email-to-LinkedIn match
        quality is critical — for example, before personalising outreach,
        triggering enrichment workflows, or appending LinkedIn data to a contact
        record.
      operationId: hemToBestLinkedin
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                email:
                  type: string
                  description: Email address.
            examples:
              email:
                summary: Using email
                value:
                  email: john.smith@example.com
      responses:
        '200':
          description: Success
          content:
            application/json:
              examples:
                found:
                  summary: Data found
                  value:
                    results:
                      linkedin_url: https://www.linkedin.com/in/john-smith-123
                    status: ok
                    metadata:
                      tokens_charged: 1
                      tokens_remaining: unlimited
                      daily_results_remaining: 9876
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorBadRequest'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorUnauthorized'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorNotFound'
        '422':
          description: Invalid Input
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorInvalidInput'
        '429':
          description: Rate limit exceeded
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorRateLimit'
components:
  schemas:
    ErrorBadRequest:
      type: object
      properties:
        error:
          type: string
          example: Bad Request
        message:
          type: string
          example: >-
            The server cannot process the request due to a client error (400 Bad
            Request).
    ErrorUnauthorized:
      type: object
      properties:
        error:
          type: string
          example: Unauthorized
        message:
          type: string
          example: Invalid API key.
    ErrorNotFound:
      type: object
      properties:
        error:
          type: string
          example: Not Found
        message:
          type: string
          example: No match was found for the data provided.
    ErrorInvalidInput:
      type: object
      properties:
        error:
          type: string
          example: Invalid Input
        message:
          type: string
          example: Message describing the nature of the invalid input.
    ErrorRateLimit:
      type: object
      properties:
        error:
          type: string
          example: Too Many Requests
        message:
          type: string
          example: Rate limit exceeded. Maximum 100 requests per second.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Pass your API key as a Bearer token. Keys follow the format
        `ms_XXXXXXXXXXX`.

````