> ## 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. # Search for LinkedIn Profile > Find the LinkedIn profile for a person or company from a name and company domain. Pass a full name (we parse it into first and last for you) or send `first_name` and `last_name` separately, then add the company as a domain like `acme.com`. URLs are normalised automatically, so you do not need to clean your inputs first. Run a free count first with `count_only: true` to see how many matches exist, then tighten or loosen your search before committing tokens. Full results are only charged when we actually find data, so an empty search costs you nothing. ## OpenAPI ````yaml /openapi.json post /search_linkedin_profile 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: /search_linkedin_profile: post: tags: - Search summary: Search for LinkedIn Profile description: >- Find the LinkedIn profile for a person or company from a name and company domain. Pass a full name (we parse it into first and last for you) or send `first_name` and `last_name` separately, then add the company as a domain like `acme.com`. URLs are normalised automatically, so you do not need to clean your inputs first. Run a free count first with `count_only: true` to see how many matches exist, then tighten or loosen your search before committing tokens. Full results are only charged when we actually find data, so an empty search costs you nothing. operationId: linkedinSlugSearch requestBody: required: false content: application/json: schema: type: object properties: name: type: string description: >- Full name (e.g. 'John Smith') — parsed into first and last name automatically. first_name: type: string description: First name (used if `name` is not provided). last_name: type: string description: Last name (used if `name` is not provided). company: type: string description: >- Company domain (e.g. 'acme.com') or URL (e.g. 'https://acme.com') — normalized to domain. example: acme.com company_domain: type: string description: Alias for `company` — company domain or URL. count_only: type: boolean default: false description: >- Free — returns the count of matching results without fetching data or charging tokens. Use this first to gauge result volume before committing to a full search. example: name: John Smith company: acme.com count_only: true responses: '200': description: Success content: application/json: examples: count_only: summary: Count only value: results: count: 3 status: ok metadata: tokens_charged: 0 tokens_remaining: unlimited daily_results_remaining: 9876 found: summary: Data found value: results: - full_name: John Smith first_name: Tate last_name: Blahnik linkedin_slug: tate-blahnik-123 linkedin_url: https://linkedin.com/in/tate-blahnik-123 company: acme.com 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`. ````