Docs / Search

`lookup_search_ids`

Find LinkedIn's id for a place, company, school, industry, job title and the like, by name.

This action only reads. It changes nothing, so it is safe to try.

What you give it

Input	What it is	Where to get it
`type` needed	One of: LOCATION, REGION, PEOPLE, CONNECTIONS, COMPANY, SCHOOL, INDUSTRY, SERVICE, JOB_FUNCTION, JOB_TITLE, EMPLOYMENT_TYPE, SKILL, LANGUAGE, POST_JOB_FUNCTION, SENIORITY, GROUPS, SALES_INDUSTRY, DEPARTMENT, PERSONA, ACCOUNT_LISTS, LEAD_LISTS, TECHNOLOGIES, SAVED_ACCOUNTS, SAVED_SEARCHES, RECENT_SEARCHES, POSTAL_CODE, HIRING_PROJECTS, SAVED_FILTERS, DEGREE. What kind of thing to look up.	You write it.
`keywords` optional	Text, up to 200 characters. The name to look for, e.g. "Berlin" or "Software". Not used for EMPLOYMENT_TYPE.	You write it.
`service` optional	One of: CLASSIC, SALES_NAVIGATOR, RECRUITER. Whose list to search (default CLASSIC).	You write it.
`limit` optional	A number, 1 to 100. How many to return (1–100, default 10).	You write it.
`connectionId` optional	A connection id. Which of your LinkedIn accounts to act from (its id from list_linkedin_accounts). Omit to use your first live one.	Run `list_linkedin_accounts` and use `accounts[].id` from its answer. 15 more places to get it `get_my_profile` → `accounts[].connectionId` `list_connections` → `connections[].connectionId` `list_connections` → `summary.accounts[].connectionId` `list_sent_invitations` → `pendingInvitations[].connectionId` `preview_withdraw_invitations` → `breakdown[].linkedinConnectionId` `list_conversations` → `inbox[].linkedinConnectionId` `list_inmail` → `inmail[].connectionId` `get_inmail_credits` → `accounts[].connectionId` `list_sales_navigator_contracts` → `accounts[].connectionId` `who_is_waiting_on_me` → `waitingOnYou[].connectionId` `who_went_cold` → `coldConversations[].connectionId` `connections_never_messaged` → `summary.accounts[].connectionId` `get_usage` → `connectionId` `get_conversation` → `connectionId` `get_inmail_conversation` → `connectionId`

Call it

curl -X POST https://api.heyreagent.com/v1/actions/lookup_search_ids \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "content-type: application/json" \
  -d '{"type":"LOCATION","keywords":"Berlin"}'

The same call in JavaScript

const response = await fetch("https://api.heyreagent.com/v1/actions/lookup_search_ids", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_KEY",
    "content-type": "application/json",
  },
  body: JSON.stringify({
    "type": "LOCATION",
    "keywords": "Berlin"
  }),
});
const answer = await response.json();
console.log(answer);

The same call in Python

import requests

response = requests.post(
    "https://api.heyreagent.com/v1/actions/lookup_search_ids",
    headers={"Authorization": "Bearer YOUR_KEY"},
    json={
        "type": "LOCATION",
        "keywords": "Berlin",
    },
)
print(response.json())

The same call in n8n

Add an HTTP Request node and fill it in like this:

Method	`POST`
URL	`https://api.heyreagent.com/v1/actions/lookup_search_ids`
Send Headers	On. Name `Authorization`, Value `Bearer YOUR_KEY`
Send Body	On. Body Content Type `JSON`, Specify Body `Using JSON`, then paste the body below

{
  "type": "LOCATION",
  "keywords": "Berlin"
}

Put your own key where it says YOUR_KEY. New here? Start with your first call.

What you get back

When it worked, the answer is { "ok": true, "result": { … } }. Inside result:

`returned`	number
`nextCursor`	Cursor or null
`matches[].id`	A search filter id. Other actions take it.
`matches[].title`	string
`matches[].pictureUrl`	string

A field that does not apply to an answer is left out, or is null.

An example answer

A sample from the documentation of the API underneath, put in the shape this action returns it. Lists are cut to their first entry.

{
  "returned": 1,
  "nextCursor": null,
  "matches": [
    {
      "title": "Technology, Information and Internet",
      "id": "6"
    }
  ]
}

When it did not work, the answer is { "ok": false, "error": "…", "message": "…" }. What each error means.

Good to know

An id is good only for filters that ask for the same type: a LOCATION id is not a REGION id.
service selects which product's list is searched. Some types exist only for Sales Navigator (SALES_INDUSTRY, POSTAL_CODE, PERSONA, ACCOUNT_LISTS, LEAD_LISTS, TECHNOLOGIES, SAVED_ACCOUNTS, RECENT_SEARCHES), only for Recruiter (HIRING_PROJECTS, SAVED_FILTERS, DEGREE), or for those two and not ordinary LinkedIn (GROUPS, DEPARTMENT, SAVED_SEARCHES).
It has no cursor: narrow the keywords instead.

In Claude or ChatGPT

Once connected, ask in your own words. The assistant sees this action as a tool with the same name, lookup_search_ids, and the same inputs.