Linkedin Company Profile Id To Slug Finder avatar
Linkedin Company Profile Id To Slug Finder

Pricing

Pay per usage

Go to Store
Linkedin Company Profile Id To Slug Finder

Linkedin Company Profile Id To Slug Finder

Developed by

ScrapeVerse

ScrapeVerse

Maintained by Community

This is a utility Actor, it can help you to find slug based url by entering id based company profile url. Which can be used in Linkedin Company Profile Scraper to scrape company profile.

0.0 (0)

Pricing

Pay per usage

1

Total users

62

Monthly users

13

Runs succeeded

>99%

Last modified

a month ago

You can access the Linkedin Company Profile Id To Slug Finder programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"local-actors-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--actors",
"sanjeta/linkedin-company-profile-id-to-slug-finder"
],
"env": {
"APIFY_TOKEN": "<YOUR_API_TOKEN>"
}
}
}
}

Configure MCP server with Linkedin Company Profile Id To Slug Finder

You can interact with the MCP server via standard input/output - stdio (as shown above), which is ideal for local integrations and command-line tools such as the Claude desktop client, or you can interact with the server through Server-Sent Events (SSE) to send messages and receive responses, which looks as follows:

{
"mcpServers": {
"remote-actors-mcp-server": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=sanjeta/linkedin-company-profile-id-to-slug-finder",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other supported MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.