Jobs
List Failed Import Items
See which people an import could not bring in, and why
GET
An import that reports failures says how many, not who. This endpoint names them: one
item per LinkedIn URL the import was given, with a plain-English
reason, a stable
reasonCode you can branch on, and the raw errorMessage the import recorded.
When Clustr holds the person’s profile, the item also carries name, headline,
jobTitle, companyName and avatarUrl. A failed item usually has none, since the
profile is often what could not be fetched; use linkedinUrl to identify it.
By default it lists the items that failed. That includes the ones a finished import left
unprocessed, which a running import would still get to. Prospects discovered through your
contacts are left out unless you ask for them with itemType.
Also available to AI assistants as the
list_failed_import_items tool on the
MCP server. In the app, open an import’s Details in Import history.Reasons
New codes may be added; treat an unfamiliar one like
unknown.
retryable is true for the contacts that retrying the import’s unfinished items would
re-process: a contact that did not complete, of an import that is no longer running, with
a valid URL. A profile that was not found will most likely fail again.
Authorizations
The API key you created on the API settings page of the Clustr app.
Path Parameters
Query Parameters
failed (the default) lists the items that failed, completed the ones imported, and all every item.
Available options:
failed, completed, all contact (a URL you sent), employee (a person an account-research run searched) or
prospect (a person discovered through a contact). Send a comma-separated list for several.
Items per page, up to 500.
Required range:
x <= 500The number of items to skip, to read the next page.