ExtractionCreateOut
202 Accepted response for URL + profile-list extractions. Old wire shape uses ``extraction_id`` (not ``search_id``) on POSTs; GET endpoints continue to expose the same value as ``search_id``. See evaboot_django/public_api/views/extraction.py:506 (URL), line 867 (profile_ids/upload).
Properties
| Name | Type | Description |
|---|---|---|
| success | boolean | Always `true` when the extraction was accepted. |
| extraction_id | string | Identifier of the new extraction. Poll `GET /v1/extractions/{extraction_id}/` with it to follow progress and collect the results; it is the same value the list endpoint returns as `search_id`. |
| message | string | Human-readable confirmation that the job was queued. |
| status | string | Stage the job was in when it was accepted. |
| count | integer | Number of leads or accounts submitted, when known upfront. It is `0` for a search or list URL, whose real size is only known once Sales Navigator has been paged through. URLs in `unresolved_urls` are |
| unresolved_urls | array | Public `linkedin.com/in/...` URLs from the request that could not be matched to a Sales Navigator profile. They are left out of the extraction and not charged. Empty when every URL was used. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/evaboot-com/json-schema/evaboot-com-extraction-create-out-schema.json",
"title": "ExtractionCreateOut",
"description": "202 Accepted response for URL + profile-list extractions.\n\nOld wire shape uses ``extraction_id`` (not ``search_id``) on POSTs;\nGET endpoints continue to expose the same value as ``search_id``.\nSee evaboot_django/public_api/views/extraction.py:506 (URL),\nline 867 (profile_ids/upload).",
"x-generated": "2026-11-07",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/evaboot-com-openapi.json#/components/schemas/ExtractionCreateOut",
"properties": {
"success": {
"default": true,
"description": "Always `true` when the extraction was accepted.",
"title": "Success",
"type": "boolean"
},
"extraction_id": {
"description": "Identifier of the new extraction. Poll `GET /v1/extractions/{extraction_id}/` with it to follow progress and collect the results; it is the same value the list endpoint returns as `search_id`.",
"title": "Extraction Id",
"type": "string"
},
"message": {
"default": "",
"description": "Human-readable confirmation that the job was queued.",
"title": "Message",
"type": "string"
},
"status": {
"default": "",
"description": "Stage the job was in when it was accepted.",
"title": "Status",
"type": "string"
},
"count": {
"default": 0,
"description": "Number of leads or accounts submitted, when known upfront. It is `0` for a search or list URL, whose real size is only known once Sales Navigator has been paged through. URLs in `unresolved_urls` are not counted, and the same person sent twice counts once.",
"title": "Count",
"type": "integer"
},
"unresolved_urls": {
"description": "Public `linkedin.com/in/...` URLs from the request that could not be matched to a Sales Navigator profile. They are left out of the extraction and not charged. Empty when every URL was used.",
"items": {
"type": "string"
},
"title": "Unresolved Urls",
"type": "array"
}
},
"required": [
"extraction_id"
],
"type": "object"
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/json-schemas/evaboot-com-extraction-create-out"
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.