LinkedIn profile API for AI assistants

The LinkedIn profile API takes the link to a public LinkedIn profile and returns what the profile says: the name, the headline, the current role and company, past roles with dates, schools, and the location. The reply is JSON, so your assistant reads the fields directly and does not have to open a browser and scroll.

What it does

You pass one input, the profile URL. The router sends the call to one provider, and the provider returns the public profile as it stands on the day of the call. Some providers have a second, larger endpoint that adds skills, recent posts, and recommendations, and it costs more per call.

The API reads public profiles only. It does not log in as you, it does not send connection requests, and it cannot see anything that LinkedIn hides from people outside the member's network.

How a Joshu assistant uses it

Before a first meeting, Joshu looks up each outside guest on the invite and puts a short note at the top of your calendar event with their current role, how long they have held it, and where they worked before.

When someone asks you for an intro, Joshu pulls both profiles and drafts the intro email with one line on each person, so you only have to check the facts and press send.

When you hand Joshu a list of names for outreach, it checks each profile first and flags the people who changed jobs since the list was made.

Choosing a provider

Most jobs only need the base profile, so start with the cheapest endpoint that returns the current role and work history. Pick a full profile endpoint when you need skills or recent posts, e.g., to write a personal opening line.

Providers differ in how fresh the data is and in how they name the fields.

curl https://hello.joshu.me/api/router/call \
  -H "Authorization: Bearer $JOSHU_ROUTER_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "endpoint": "anyapi.linkedin.user.profile",
    "params": {
      "url": "https://www.linkedin.com/in/username"
    }
  }'