> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# People and ids

> How a person is named in a call, how to find the id from an email or a name, and what to do when several people match.

## The id every call takes

Circle, edge and paths name a person by a **LinkedIn profile URL**, or the **public identifier** from one — the part after `/in/`. Both of these name the same person:

```json theme={null}
{ "id": "https://www.linkedin.com/in/maya-okafor" }
{ "id": "maya-okafor" }
```

A LinkedIn member token (`ACoAA…`) is not a public identifier, and is answered `404 person_not_found`.

## Finding the id: resolve

When you hold an email, or a name and a company, [`/v1/resolve`](https://docs.orbb.com/api-reference/resolve) finds the profile. It takes one of three bodies:

```json By email theme={null}
{ "email": "maya@northwind.example" }
```

```json By name and company theme={null}
{ "full_name": "Maya Okafor", "company_domain": "northwind.example" }
```

```json By profile, no search theme={null}
{ "id": "maya-okafor" }
```

* A name is `full_name`, or `first_name` with `last_name`. A one-word name has no last name: send it in `first_name` and `last_name`.
* A company is any of `company`, `company_domain` or `company_linkedin_url`. It also decides which current position the answer shows.
* An email that finds no one falls back to a search by name — the name you sent, or one read from the address.
* `on_miss: RESEARCH` searches a further profile source and does not reuse an earlier search that found no one. It takes longer, and counts towards the [research limit](https://docs.orbb.com/api/rate-limits.md).

## Reading the answer

`resolution.status` is what to branch on:

| Status | Means | Do |
| - | - | - |
| `RESOLVED` | One profile matches. | Use `person.publicId` in the next call. |
| `AMBIGUOUS` | Several profiles match, listed in `candidates`. | Choose one with your own context — the company, the role — or ask the user. Never pick the first. |
| `UNRESOLVED` | No profile matches. | A `200`, not an error. Try another form (email, then name with company), or `on_miss: RESEARCH`. |

`resolution.method` says what answered: `EMAIL`, `NAME_COMPANY`, `PUBLIC_ID` or `LINKEDIN_URL`.

## Two ids, one person

Every person in an answer carries a `key` and a `publicId`.

* **`publicId`** is the person's *current* LinkedIn identifier. It is a valid id in any call.
* **`key`** is the identifier percent-decoded and lower-cased. Two people in answers are the same person when their keys are equal — use it to de-duplicate across calls.

A profile can have been held by more than one person over time. A circle, edge or paths call with such an id is answered `422 ambiguous_person`, with the `candidates` in the error body: call again with the one you mean.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.