The gtm-api AI Assistant: Where to Start with the LinkedIn API
The gtm-api AI Assistant sits in the API docs, reads the live API and the changelog, and answers in plain English. The fastest way to start with the LinkedIn API.
The gtm-api AI Assistant sits in the API docs, reads the live API and the changelog, and answers in plain English. The fastest way to start with the LinkedIn API.
Paste a GoLogin profile ID and gtm-api connects a LinkedIn account that already runs in GetSales. No new session, no re-login, the profile keeps its proxy.
The obvious move is to paste the server into Claude’s config file. Claude Desktop quietly discards it, and nothing in the app tells you why.
The obvious place to get a LinkedIn profile is LinkedIn, and it is the one source that will only ever return your own.
Creating the app takes ten minutes. Getting permission to call anything useful with it is the part with no timeline.
Sales tooling eventually reaches for the Sales Navigator API, and the form it points you at no longer leads anywhere.
You can design around a number you know. LinkedIn gives you one you can only find by hitting it.
For the people who have to pick one and then build on it: developers shipping AI agents, platforms adding LinkedIn to a product, and agencies running their own stack.
Every cap in one place: invitations, messages, InMail, search, profile views and the network ceiling, per plan, with what actually resets when.
Adding accounts is the obvious way to send more, and it is also how you lose the ones you already have.