> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/social-accounts-and-platform-faqs/linkedin.md).

# LinkedIn

Blotato supports publishing to LinkedIn personal profiles and company Pages.

For AI-agent and API publishing, use the [LinkedIn guide](/platform-publishing/platforms/linkedin.md). For account setup, see [Connect LinkedIn Accounts](/social-accounts-and-platform-faqs/linkedin/connect-accounts.md).

The following LinkedIn engagement features are not available:

* First Comment
* Comments Inbox
* Messaging Inbox
* DM automations

These engagement features support Instagram and Facebook only. LinkedIn restricts access to the comment and messaging API endpoints Blotato needs. Blotato is seeking approved API access, with no release date.

Some tools use browser extensions that store LinkedIn session cookies as a workaround. Blotato does not use this method because it violates LinkedIn's terms.

See [LinkedIn Limitations](/social-accounts-and-platform-faqs/linkedin/limitations.md) for the full list of unsupported features.


---

# 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://help.blotato.com/social-accounts-and-platform-faqs/linkedin.md?ask=<question>&goal=<user_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.