Skip to main content

Find LinkedIn URL by Name API

Written by Kadri - RichAPI Support Team

POST /find_linkedin_url_by_name • Credits: 0.2 credits per call that finds a profile

Find LinkedIn URL by Name takes the full name of a person and the name of the employer. The endpoint returns the LinkedIn profile URL of that person. Send a POST request to /find_linkedin_url_by_name with the full_name parameter and the company_name parameter. The response returns the URL in the LinkedIn Profile URL field. A call that finds a profile costs 0.2 credits, which is $0.004. A call that finds no profile returns 404 and costs nothing.

What does Find LinkedIn URL by Name do?

A lead record often holds a person name and an employer name, and no LinkedIn URL. Find LinkedIn URL by Name closes that gap. The endpoint sends the name pair to a licensed third-party data set and returns the single best profile match as a URL. The company name is the second half of the match key, and not an optional filter. The endpoint is synchronous, so the response arrives in the same HTTP call. One call covers one person.

Find LinkedIn URL by Name returns a URL and no profile data. To read the name, the headline, the work history and the skills behind that URL, send the URL to Profile Enrichment API.

Where do I send a Find LinkedIn URL by Name request?

  • Method: POST

  • URL: https://api.richapi.ai/api/v1/find_linkedin_url_by_name

  • Authentication: x-api-key header

  • Content type: application/json

  • Response: synchronous JSON

  • Cost: 0.2 credits per call that finds a profile. A call that finds none costs nothing.

  • Data source: licensed third-party data provider

How to send a Find LinkedIn URL by Name request

  1. Copy the API key from the RichAPI dashboard.

  2. Set the x-api-key header to that API key.

  3. Set the Content-Type header to application/json.

  4. Put the full name of the person in the full_name field.

  5. Put the current employer of the person in the company_name field.

  6. Send the request to https://api.richapi.ai/api/v1/find_linkedin_url_by_name.

  7. Read the LinkedIn Profile URL value from the data object.

CAUTION: A lookup that finds no profile returns the HTTP status 404 and costs no credit. Check the status code before you read the profile URL.

cURL

curl -X POST https://api.richapi.ai/api/v1/find_linkedin_url_by_name   
-H "x-api-key: YOUR_API_KEY"
-H "Content-Type: application/json"
-d '{
"full_name": "Daniela Ferreira",
"company_name": "Northwind Logistics"
}'

Python

import requests

response = requests.post(
"https://api.richapi.ai/api/v1/find_linkedin_url_by_name",
headers={"x-api-key": "YOUR_API_KEY"},
json={
"full_name": "Daniela Ferreira",
"company_name": "Northwind Logistics",
},
timeout=60,
)
if response.status_code == 404:
print("No profile found. No credit charged.")
else:
response.raise_for_status()
result = response.json()
print(result["data"]["LinkedIn Profile URL"])

Node.js

const response = await fetch(
"https://api.richapi.ai/api/v1/find_linkedin_url_by_name",
{
method: "POST",
headers: {
"x-api-key": "YOUR_API_KEY",
"Content-Type": "application/json",
},
body: JSON.stringify({
full_name: "Daniela Ferreira",
company_name: "Northwind Logistics",
}),
},
);

const data = await response.json();
console.log(data.data["LinkedIn Profile URL"]);

Which parameters does Find LinkedIn URL by Name accept?

Parameter

Type

Required

Default

Description

full_name

string

Yes

""

The full name of the person, for example Daniela Ferreira. Send the first name and the last name together in one value.

company_name

string

Yes

""

The name of the company of the person, for example Northwind Logistics. Send the company name, and not the website domain.

Find LinkedIn URL by Name accepts these two parameters and no others. The endpoint accepts no job title, no location, no email address and no domain parameter.

CAUTION: Do not send the keys FullName or CompanyName in the request body. The API returns a 400 error with the message Unknown input field(s), and charges no credit.

The RichAPI dashboard, the MCP tool find_linkedin_url_by_name, and the n8n operation find_linkedin_url_by_name use the same two parameter names. Those names are full_name and company_name.

What does Find LinkedIn URL by Name return?

The block below is an example response for the full name Daniela Ferreira at the company Northwind Logistics. The field names and the structure are exact. The person and the URL are illustrative.

{
"data": {
"LinkedIn Profile URL": "https://www.linkedin.com/in/danielaferreira"
},
"message": "success"
}

When no profile matches, the response has the HTTP status 404 and this body. The call costs no credit.

{
"data": {
"LinkedIn Profile URL": null
},
"message": "not_found"
}

RichAPI also adds a richapi_meta object to every response, with the request ID and the credits charged.

The field name LinkedIn Profile URL holds two spaces. Read the field with a bracket lookup, such as result["data"]["LinkedIn Profile URL"] in Python, or data.data["LinkedIn Profile URL"] in JavaScript.

Which fields does the Find LinkedIn URL by Name response hold?

Field

Type

Description

data

object

The result container. The object holds the matched profile URL.

data["LinkedIn Profile URL"]

string or null

The LinkedIn profile URL of the matched person. null when no profile matches.

message

string

success when a profile matches. not_found when none matches.

Why does Find LinkedIn URL by Name need a company name?

A full name is not a unique key on LinkedIn. Thousands of profiles carry the same common name. The company name is the second half of the match key, and it separates one person from every namesake.

Both parameters are required. If the request body omits company_name, the API returns a 400 error with the message Missing required field: company_name, and RichAPI charges no credit.

Three rules raise the match rate:

  1. Send the current employer of the person, and not a past employer.

  2. Send the trading name of the company, such as Northwind Logistics.

  3. Remove the legal suffix, such as Inc, Ltd, GmbH or LLC.

What happens when the name is common?

Find LinkedIn URL by Name returns one profile URL per call. The endpoint returns no candidate list, no match score and no confidence value. For a common name, the company name decides which profile the data set returns.

Three outcomes are possible for a common name:

Case

Outcome

One person with that name works at that company.

The response returns the profile URL of that person.

The person left the company, or the profile lists a different employer.

The data set holds no match on the name pair, and the response carries no profile URL.

Two people with the same name work at the same company.

The data set returns one profile, and the response carries no signal about the second person.

CAUTION: Do not treat a returned URL as a verified identity for a common name. Verify the match before you write the URL to a customer record.

To verify a match, send the returned URL to Profile Enrichment API. Compare the currentCompany value and the currentTitle value in that response against your own record. An email address is unique. If an email address for the person exists, Find LinkedIn URL by Email API resolves the profile from that address instead.

How do I enrich the profile that Find LinkedIn URL by Name returns?

Find LinkedIn URL by Name returns a URL. Profile Enrichment turns that URL into a full person record. Chain the two calls in this order:

  1. Send the name pair to /find_linkedin_url_by_name.

  2. Read the LinkedIn Profile URL value from the data object.

  3. If the status is 404 or the value is empty, stop and log the record as unresolved.

  4. Send the value as the url parameter to /enrich_profile.

  5. Read the profile fields from the Profile Enrichment response.

import requests

HEADERS = {"x-api-key": "YOUR_API_KEY"}

lookup = requests.post(
"https://api.richapi.ai/api/v1/find_linkedin_url_by_name",
headers=HEADERS,
json={
"full_name": "Daniela Ferreira",
"company_name": "Northwind Logistics",
},
timeout=60,
)
profile_url = None
if lookup.status_code != 404:
lookup.raise_for_status()
profile_url = lookup.json().get("data", {}).get("LinkedIn Profile URL")

if profile_url:
profile = requests.post(
"https://api.richapi.ai/api/v1/enrich_profile",
headers=HEADERS,
json={"url": profile_url},
timeout=60,
)
profile.raise_for_status()
print(profile.json())
else:
print("No LinkedIn profile URL for this name and company.")

The two calls bill separately. The lookup costs 0.2 credits and the Profile Enrichment call costs 1 credit, so one resolved and enriched record costs 1.2 credits, which is $0.024. An unresolved record costs nothing: the lookup returns 404, and step 3 skips the second call.

How much does Find LinkedIn URL by Name cost?

Find LinkedIn URL by Name costs 0.2 credits for a call that finds a profile. 1 credit costs $0.02 on the 1,000 and 5,000 credit packs, so one call costs $0.004 there. Larger packs cost less per credit. A call that finds no profile returns 404 and costs nothing.

Calls that find a profile

Credits

Cost

1

0.2

$0.004

100

20

$0.40

1,000

200

$4.00

10,000

2,000

$40.00

RichAPI holds 0.2 credits at the start of each call. It charges them when the lookup finds a profile and releases them for every other outcome: a 404 with no match, a 4xx error, or a 5xx error.

A repeated name pair is a new call, and it costs 0.2 credits again when it finds a profile. To control the cost of a repeated list, store the result per unique name pair in your own store. Store the unresolved pairs too.

Which errors can Find LinkedIn URL by Name return?

Status

Meaning

What to do

400

The request body is not valid JSON, a required parameter is missing, or the body holds an unknown field.

Send a JSON object with a full_name value and a company_name value, and no other key.

401

The API key is missing, wrong or revoked.

Send a valid key in the x-api-key header.

402

Insufficient credits: the organization has too few credits. Or Monthly spend limit reached: the team hit its monthly spend limit.

Buy credits in the RichAPI dashboard, or ask the organization owner to raise the spend limit.

403

Endpoint not available on your plan: this API key has no access to this endpoint.

Call GET /api/v1/my-endpoints to list the endpoints this key can use. Contact support for access.

404

No profile matches the name pair, and message is not_found. Or the endpoint name is wrong.

Check the name and the current employer. Check that the request goes to /find_linkedin_url_by_name.

405

The request method is not POST.

Send the request with the POST method.

429

Too many requests.

Read the Retry-After header. Wait that many seconds, then send the request again.

500

RichAPI failed.

Send the request again. If the failure repeats, contact support.

503

The lookup is temporarily unavailable, and message is unavailable.

Send the request again after a short wait. If the failure repeats, contact support.

RichAPI charges no credit for a 400, 401, 402, 403, 404, 405, 429, 500 or 503 response.

Frequently asked questions

Does a Find LinkedIn URL by Name call that finds no profile still cost credits?

No. A lookup that matches no profile returns the HTTP status 404 and costs no credit. Find LinkedIn URL by Name charges 0.2 credits only for a 200 response that carries a profile URL.

Why does Find LinkedIn URL by Name require a company name?

A full name matches many LinkedIn profiles, so a name alone is not a unique key. Find LinkedIn URL by Name uses the company name as the second half of the match key. Both full_name and company_name are required, and a request without one of them returns a 400 error.

Can I send the parameters as FullName and CompanyName?

No. The request body of Find LinkedIn URL by Name accepts the lower-case names full_name and company_name only. A body with the key FullName or the key CompanyName returns a 400 error with the message Unknown input field(s).

What does Find LinkedIn URL by Name return for a person who changed jobs?

Find LinkedIn URL by Name matches on the current employer in the data set. If the person left the company in the company_name value, the lookup can return 404 with no profile URL. A 404 costs no credit. Send the current employer of the person for the highest match rate.

How do I get profile data after Find LinkedIn URL by Name returns a URL?

Send the returned LinkedIn Profile URL value as the url parameter of Profile Enrichment API. Profile Enrichment returns the name, the headline, the location, the current role, the work history and the skills for that URL. Profile Enrichment costs 1 credit per call.

Is Find LinkedIn URL by Name synchronous?

Yes. Find LinkedIn URL by Name returns the result in the same HTTP call. The endpoint uses no polling, no job_id and no webhook.

Can Find LinkedIn URL by Name resolve many people in one call?

No. One Find LinkedIn URL by Name call covers one person. To resolve a list, send one request per person, and control your own request rate. A 429 response means that the rate is too high.

Related articles

Did this answer your question?