> For the complete documentation index, see [llms.txt](https://docs.pockethrms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pockethrms.com/integrations/linkedin.md).
# LinkedIn
### How to get the Company ID from LinkedIn?
#### Method 1
**Step 1:** Go to LinkedIn
**Step 2:** Search the company name in the search field at the upper left corner of the screen.
**Step 3:** Click on the company profile from the search results.
**Step 4:** Click on the ‘Jobs’ tab as shown in the image below.
**Step 5:** Click on any of the jobs posted by the company.
Once you click on the job post you will find the ‘Company ID’ in the URL of the next page.
In the above example ‘Company ID’ is ‘370289’ as shown in the image above.
#### Method 2
You can also get a Company ID from the personal profile page of the employee who worked for the company.
**Step 1:** Search the employee’s name and go to their profile by clicking on their name from the search results.
Step 2: Hover your cursor over the company logo from the ‘Experience’ section and get the Company ID in the link that appears at the lower left-hand corner of the screen.
**Note:** To confirm the company on LinkedIn, enter the link given below followed by the company Id in the search bar and you will be redirected to the company profile.
For Example,
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.pockethrms.com/integrations/linkedin.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 `build a script that syncs our docs to a CMS` 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.
