---
title: "Extract a single Sales Navigator profile"
method: POST
path: "/v1/extractions/single/"
tags: ["LinkedIn Extraction"]
---

# Extract a single Sales Navigator profile

`POST /v1/extractions/single/`

## Request

- Base URL: `https://api.evaboot.com`
- URL: `https://api.evaboot.com/v1/extractions/single/`
- Auth: HTTP bearer

Extract one Sales Navigator lead or account and get the full record back in the response.

This is the only extraction endpoint that is synchronous: there is nothing to poll and no webhook to wire up, so it suits enriching a single record inside a live workflow. Expect it to take a few seconds.

**Slow lookups:** if the scrape and email lookup are still running after about 25 seconds you get `202` with an `extraction_id` instead. It carries on and is billed the same way; poll `GET /v1/extractions/{extraction_id}/` for the prospect. Use `POST /v1/extractions/profiles/` for more than one profile at a time.

The returned `prospect` object carries the identity, role, tenure and company fields Evaboot collects, plus a verified email address and its status where one exists.

**Cost:** 1 credit, email included.

## Request body

- SingleExtractionCreateIn
  - `profile_id` string, required: The lead or account to extract, as a Sales Navigator URL (`linkedin.com/sales/lead/...`) or as a bare Sales Navigator id. Public `linkedin.com/in/...` profile URLs are not accepted.
  - `enrich_email` 'none' | 'matching' | 'all': Deprecated and ignored: every lead extraction now finds and verifies a professional email for every lead, and each lead costs 1 credit with its email included. Still accepted so existing integrations keep working.

## Response `200`

OK

- SingleExtractionOut: 200 OK response for single-profile extraction. Like the other POST endpoints, the legacy wire format uses ``extraction_id`` rather than ``search_id``. See evaboot_django/public_api/views/extraction.py:1350.
  - `success` boolean: Always `true` when the profile was extracted.
  - `extraction_id` string, required: Identifier of the extraction that produced this record. Use it with `GET /v1/extractions/{extraction_id}/` to fetch the same result again later.
  - `prospect` object: The extracted record, as human-readable column names mapped to values: identity, role and tenure, company details, and the email address plus its verification status when enrichment was requested. Which columns are present depends on whether a lead or an account was extracted. Empty if nothing could be extracted.

## Other responses

- `202`: Accepted
- `401`: The API key is missing, malformed or unknown.
- `402`: Not enough credits to cover the request.
- `409`: No usable Sales Navigator seat (never connected, or expired).
- `422`: The request body or a supplied URL failed validation.
- `429`: A daily quota or rate limit is exhausted.

---

[API](https://skmtc.dev/evaboot/apis/evaboot-public-api.md) · [All operations](https://skmtc.dev/evaboot/apis/evaboot-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/evaboot/apis/evaboot-public-api/revisions/d770494f2718?raw)