> For the complete documentation index, see [llms.txt](https://docs.clearout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clearout.io/reverse-lookup/linkedin-reverse-lookup.md). # Linkedin Reverse Lookup Identify LinkedIn profile contacts & details LinkedIn Reverse Lookup **converts LinkedIn profile URLs into** **enriched contact records with pre-verified email addresses** and related details. This enables you to utilize your LinkedIn network's connections, profile visits, and saved leads as a means of generating high-intent prospects and conducting outreach via the email channel. ## How to use LinkedIn Reverse Lookup * Go to Reverse Lookup → [LinkedIn Reverse Lookup](https://app.clearout.io/reverse-lookup/linkedin) in the Clearout dashboard. * Paste the LinkedIn profile URL into the input box. * Click Search to fetch the associated contact details (emails and other available attributes). * Successful search results will be automatically added to the default list and you can export them to your sales tools for outreach activities. {% hint style="info" %} **Developer note** Want to automate email reverse lookup, refer to the **Reverse LinkedIn Lookup API**[ ](https://docs.clearout.io/developers/api/reverse-lookup#get-reverse_lookup-linkedin) section for sample code and integration details. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.clearout.io/reverse-lookup/linkedin-reverse-lookup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.