ContactOut Contact Info API - Single API

The Contact Info API - Single API from ContactOut — 1 operation(s) for contact info api - single.

Operations 1

GET /v1/people/linkedin from LinkedIn Profile #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/contactout:contactout-contact-info-api-single-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

contactout-contact-info-api-single-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: ContactOut Contact Info API - Single API
  version: v1
  summary: 'B2B contact data: people and company enrichment, search, contact checks, email verification, campaigns and usage stats.'
  description: Welcome to ContactOut's API. Find anyone's email & phone number 10x faster with the most powerful sales and recruitment intelligence software available. (Generated from the published API reference at https://api.contactout.com; every operation carries x-source pointing at the section it was read from.)
  contact:
    name: ContactOut
    url: https://contactout.com/meeting?utm_source=api_docs
  termsOfService: https://contactout.com/terms
  x-generated-from: documentation
  x-generated-on: '2026-10-07'
  x-generator: 'api-evangelist enrichment pass: deterministic parse of the Slate API reference HTML (headings, parameter tables, example blocks); the pipeline generator generate-contract-from-docs.py was run first and its path-collapse heuristic merged the literal resources linkedin/email/domain into a {v1id} template, so its output was replaced by this parse'
servers:
- url: https://api.contactout.com
security:
- apiToken: []
tags:
- name: Contact Info API - Single
paths:
  /v1/people/linkedin:
    get:
      summary: from LinkedIn Profile
      tags:
      - Contact Info API - Single
      operationId: contactInfoSingleFromLinkedinProfile
      description: GET https://api.contactout.com/v1/people/linkedin?{profile=&include_phone=}
      x-source: https://api.contactout.com#contactinfo-from-linkedin-http-request
      x-section: Contact Info API - Single from LinkedIn Profile
      parameters:
      - name: profile
        in: query
        required: true
        schema:
          type: string
        description: 'The fully formed URL of the LinkedIn profile. URL must begin with http and must contain linkedin.com/in/ or linkedin.com/pub/ (profile: (string, URL encoded, required))'
      - name: include_phone
        in: query
        required: false
        schema:
          type: boolean
        description: If set to true, it will include phone information in the response and deduct phone credits. (boolean, optional, Defaults to false)
      - name: email_type
        in: query
        required: false
        schema:
          type: string
        description: email_type=personal — Returns only personal emails  email_type=work — Returns only work emails  email_type=personal,work — Returns both personal and work emails  email_type=none — Returns no emails and consumes no email credits  By default, both personal and work emails are returned. (string, optional)
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ContactInfoSingleFromLinkedinProfileResponse'
        '400':
          $ref: '#/components/responses/BadCredentials'
        '401':
          $ref: '#/components/responses/BadRequest'
        '403':
          $ref: '#/components/responses/Forbidden'
        '429':
          $ref: '#/components/responses/RateLimited'
      x-cost:
      - Consumes 1 email credit if email is found and 1 phone credit if phone number is found (and include_phone is set to true).
components:
  responses:
    Forbidden:
      description: 'You''re out of credits, please email your sales manager or book a meeting; or: No access to endpoint'
    RateLimited:
      description: 'Rate limit reached. Check header retry-after: <time_in_seconds> for when rate limit will reset'
      headers:
        retry-after:
          schema:
            type: integer
          description: Seconds until the rate limit resets
    BadCredentials:
      description: Bad credentials or invalid headers
    BadRequest:
      description: Bad request or invalid input
  schemas:
    ContactInfoSingleFromLinkedinProfileResponse:
      type: object
      properties:
        status_code:
          type: integer
          description: The HTTP status code of the response. (integer)
        profile:
          type: object
          description: An object containing contact details for the LinkedIn profile. url - The URL of the LinkedIn profile.email - An array of email addresses associated with the profile.work_email - An array of work email addresses.work_email_status - A dictionary indicating the verification status of work emails.personal_email - An array of personal email addresses.phone - An array of phone numbers associated with the profile.github - An array of GitHub usernames associated with the profile. (object)
  securitySchemes:
    apiToken:
      type: apiKey
      in: header
      name: token
      description: 'ContactOut uses API keys to allow access to the API. You can request an API key by booking a meeting. ContactOut expects the API key to be included in all API requests to the server in a header that looks like the following: token : <YOUR_API_TOKEN>'
externalDocs:
  url: https://api.contactout.com
  description: ContactOut API Reference
x-rate-limits:
- 'People Search API: 60 requests per minute'
- 'Contact Checker APIs: 150 requests per minute'
- 'Other APIs: 1000 requests per minute'