Skip to main content
import_search_connection_rows Import selected saved Bing backlink rows as unchecked discovery candidates. Keep the same request key when retrying. Review and verify candidates before monitoring.
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.
This operation changes saved state. Review its inputs and retry behavior before calling.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Validation and omitted values

Select one through 100 distinct rowId values from the saved Bing snapshot and supply idempotencyKey. Keep the same request fields and request key when retrying. Import saves unchecked discovery candidates with provider provenance and coverage. It starts no placement monitoring and invents no first-seen or last-seen dates. Google performance rows cannot be imported as backlinks. Review the saved discovery run, verify selected candidates, then choose which placements to monitor.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • v (number, required): must equal 1
  • id (string, required): Resource identifier returned by the operation. minLength: 1; maxLength: 128; pattern: ”^[a-zA-Z0-9_-]+$”
  • workspace_id (string, required): Workspace that owns this record. minLength: 1; maxLength: 128; pattern: ”^[a-zA-Z0-9_-]+$”
  • project_id (string, required): Project that owns this record. minLength: 1; maxLength: 128; pattern: ”^[a-zA-Z0-9_-]+$”
  • provider (string, required): values: “linktrail_corpus”, “dataforseo”, “imported”
  • data_mode (string, required): values: “synthetic”, “owned_corpus”, “provider_index”, “imported”
  • query (object, required): additional fields rejected
  • status (string, required): Resource lifecycle status. values: “queued”, “running”, “succeeded”, “partial”, “failed”, “reconciliation_required”
  • created_at (string, required): UTC timestamp when the record was created. format: “date-time”; pattern: ”^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d\.\d{3}(?:Z))$”
  • started_at (string / null, required).
  • finished_at (string / null, required).
  • coverage (string, required): Dataset scope and completeness, including limits on what these results establish. values: “pending”, “complete_for_query”, “capped”, “partial”, “unknown”
  • coverage_reason (string / null, required).
  • provider_total_count (integer / null, required).
  • usage (object, required): additional fields rejected
  • operation (string, required): must equal “backlinks”
  • coverage_scope (string, required): values: “customer_import”, “corpus_subset”, “provider_query”
  • whole_web_coverage (boolean, required): False: these results do not measure the whole web. must equal false
  • replayed (boolean, optional): True when the response reuses an earlier request with the same idempotency value.
  • rejected (array, required).
  • duplicates (array, required).
  • rejected_total (number, required).
  • duplicates_total (number, required).
Download input schema · Download output schema

Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Continue

get_discovery_run · verify_discovery_candidates Follow the related workflow, inspect capability status, or return to the command index.