AIsa Backlinks
Server Details
Your agent needs the link graph — who points at a competitor, what anchor text they use, what was won or lost last month, and which sites link to all of your rivals but not to you.
What you can ask for • "Who links to my competitor and not to me?" • "What anchors point at this domain, and how spammy are the sources?" • "Which links did this site win and lose in the last 30 days?" • "Compare the referring domains of these five competitors." • "Summarise the backlink profile of these 100 domains in bulk."
How to use it Point any MCP client at https://mcp.aisa.one/seo-backlinks/mcp and sign in with OAuth — there is no key to create or paste. 27 tools: backlinks and referring domains, anchors, new and lost links over time, domain and page intersections, referring networks, spam scores, bulk summaries for many domains at once, plus Semrush's own backlink and indexed-page sets.
Why this rather than the source Two independent link indexes behind one account — coverage differs, and the gap is usually the interesting part.
It is also a door to the rest The same login reaches 26 sources and 580+ operations. Find the link gap here, then ask the same agent who runs those sites and how to reach them — without adding a second server.
What it costs Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident.
Where else it reaches https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
- Status
- Healthy
- Uptime
- 94.1% over 45 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
Scored across 34 tools
Most endpoints are distinguishable by provider and metric, but there is substantial conceptual overlap across Semrush and DataForSEO equivalents (backlinks, overview/summary, referring domains, competitors). Several Semrush tools lack functional descriptions beyond pricing, and the deprecated `use` tool sits beside `batch_use`, increasing misselection risk.
All names are lowercase snake_case, but the set mixes several conventions: `get_*`, `post_*`, `batch_*`, and generic names like `account`, `search`, and `use`. The provider-prefixed backlink tools are mostly readable, but the overall pattern is not consistently verb_noun.
With 34 tools, the surface is heavy for the apparent scope, and many endpoint wrappers duplicate similar capabilities across Semrush and DataForSEO. The presence of search/batch meta-tools suggests the large direct endpoint list could be reduced or routed more selectively.
Coverage of backlink analytics is broad: summaries, detailed backlinks, anchors, referring domains/networks, competitors, intersections, historical and timeseries data, bulk variants, spam scores, and ranks are all represented. Minor gaps exist around cross-provider reconciliation and some Semrush endpoints lack descriptive documentation, but core backlink workflows are covered.
Available Tools
34 toolsaccountShow account and usageARead-onlyInspect
Who am I, what can I use, how much can I spend: the key, the account balance, the Go-to-Market wallet when one is active, and usage for today, 7 days and 30 days. Free; needs the Authorization header. Call it to verify a new connection or to explain a 402. ok is true only when the balance was read; otherwise each entry of errors says what to do in next_step.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds substantial context beyond the readOnlyHint/openWorldHint/destructiveHint annotations: the call is free, it requires the Authorization header, and it discloses result semantics ('ok is true only when the balance was read; otherwise each entry of errors says what to do in next_step'). That tells an agent how to interpret partial failure, which annotations cannot convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with what the agent gets, followed by cost/auth, then call triggers, then result interpretation. No sentence is redundant and none could be dropped without losing information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read tool with an output schema already present, the description covers the remaining gaps: cost, auth requirement, invocation triggers, and the ok/errors/next_step contract. Nothing an agent needs to call or interpret it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the description has nothing parameter-level to compensate for, and the schema is fully covered. A 4 rather than 5 reflects that it adds no input-syntax detail, though none is possible here.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a concrete resource set (identity/key, account balance, Go-to-Market wallet, usage over 1/7/30 days) rather than restating the name. It is clearly distinguishable from every sibling, which are all Reddit, batch, or search tools. An agent knows exactly what it will learn by calling it.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit triggering conditions are given: 'Call it to verify a new connection or to explain a 402.' That is a strong when-to-use statement. It stops short of 5 because it names no alternative tool or a when-not condition, though the sibling list offers no obvious competing diagnostic.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
batch_get_schemaGet AIsa tool schemas in one batchARead-onlyIdempotentInspect
Retrieve schemas for 1 to 20 exact tool names from search. Build arguments from successful schemas, then call batch_quote. Do not call batch_use yet. Use tool names exactly as search returns them, without a client prefix such as mcp__aisa__. Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.
| Name | Required | Description | Default |
|---|---|---|---|
| tools | Yes | Exact tool names returned by search whose complete contracts are needed. Never invent tool names. | |
| session_id | No | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. | |
| include_documentation | No | Return the complete immutable public OpenAPI operation, referenced declarations, provenance and scoped completeness. Documentation does not change execution support. | |
| include_response_schema | No | Return the complete response_schema. Defaults to false. | |
| include_arguments_schema | No | Return the complete arguments_schema. Defaults to true. |
Output Schema
| Name | Required | Description |
|---|---|---|
| tools | Yes | |
| session_id | Yes | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. |
| error_count | Yes | |
| total_count | Yes | |
| success_count | Yes | |
| next_steps_guidance | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not required to restate it. It adds genuine operational context: the batch_use prohibition, exact-name/prefix requirements, and session reuse semantics. It does not cover failure handling when names are invalid, keeping it below a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core action and size limit, and every sentence carries workflow value. The session_id sentence duplicates the schema's own parameter description, which is minor redundancy rather than bloat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only batch retrieval tool with an output schema, the description supplies the orchestration context an agent needs (source of names, next steps, session handling) without needing to explain return values. Nothing essential to correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds real meaning beyond the schema by constraining names to those returned by search and warning against a client prefix such as mcp__aisa__, which is not encoded in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Retrieve schemas for 1 to 20 exact tool names') and pins the source of those names to search. This clearly separates it from siblings like search (finds tools), batch_quote, and batch_use.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly sequences the workflow: build arguments from successful schemas, then call batch_quote, and 'Do not call batch_use yet.' This is an explicit when-to-use and when-not-to-use instruction naming the alternative siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
batch_quoteQuote published AIsa tools without executing themARead-onlyIdempotentInspect
Obtain AIsaServices cost quotes for 1 to 20 published tools without executing them. Same input as batch_use: exact tool names and schema-valid arguments. Never falls back to execution. The response reports auto_execute_eligible and auto_execute_threshold_micros_usd. auto_execute_eligible waives only the extra cost-confirmation step and does not override a user prohibition on execution, a narrower scope, or a tighter budget limit. Quotes are price observations, not authorization grants. Use tool names exactly as search returns them, without a client prefix such as mcp__aisa__. Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.
| Name | Required | Description | Default |
|---|---|---|---|
| calls | Yes | ||
| search_id | No | Optional search correlation identifier returned by search. | |
| session_id | No | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. |
Output Schema
| Name | Required | Description |
|---|---|---|
| results | Yes | |
| batch_id | Yes | |
| session_id | Yes | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. |
| error_count | Yes | |
| total_count | Yes | |
| success_count | Yes | |
| next_steps_guidance | Yes | Deterministic next-step instructions derived from this result. Not an authorization grant. |
| auto_execute_eligible | No | True when the worst-known total of successful USD quotes is at or below auto_execute_threshold_micros_usd. A non-USD successful quote makes the batch ineligible. Present on quote responses. |
| auto_execute_threshold_micros_usd | No | Configured auto-execute threshold in micro-USD. 0 disables automatic execution. Present on quote responses. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well past the readOnly/idempotent annotations by explaining that quotes are price observations rather than authorization grants, and precisely delimiting what auto_execute_eligible does and does not waive (user prohibition, narrower scope, tighter budget). It also guarantees no execution fallback, which is the key behavioral risk for this tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Purpose is front-loaded and most sentences carry distinct rules (no fallback, eligibility limits, naming, session reuse). It is on the long side and the argument-shape constraint is stated twice in spirit, but little is truly wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value documentation isn't required, yet the description still flags the two response fields that matter for a downstream decision. Combined with session and naming guidance, an agent has everything needed to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
At 67% schema coverage the schema already documents each parameter, so the description earns credit only for added meaning: exact-name rules for 'tool', session_id reuse semantics, and the 1-to-20 argument-shape parallel with batch_use. It doesn't clarify search_id beyond what the schema states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Obtain AIsaServices cost quotes for 1 to 20 published tools') plus the crucial scope qualifier 'without executing them.' It is immediately distinguishable from the sibling batch_use, which executes rather than quotes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly names the parallel sibling ('Same input as batch_use') and draws the boundary ('Never falls back to execution'). It also gives operational conditions: use names exactly as search returns them, strip any mcp__aisa__ prefix, and reuse session_id from Search for the task.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
batch_useExecute published AIsa toolsADestructiveInspect
Billable API calls can incur substantial charges. Never call before a successful batch_quote for the same tools and arguments. Execute only when that quote response reports auto_execute_eligible=true for these calls, or when explicit user authorization covers that cost and risk. auto_execute_eligible waives only the extra cost-confirmation step; it does not override a user prohibition on execution, a narrower scope, or a tighter budget limit. Re-quote if tools, arguments, or scope change. Execute 1 to 20 independent published-tool calls; never silently retry. A missing or failed quote is not free. Use tool names exactly as search returns them, without a client prefix such as mcp__aisa__. Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.
| Name | Required | Description | Default |
|---|---|---|---|
| calls | Yes | ||
| search_id | No | Optional search correlation identifier returned by search. | |
| session_id | No | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. |
Output Schema
| Name | Required | Description |
|---|---|---|
| results | Yes | |
| batch_id | Yes | |
| session_id | Yes | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. |
| error_count | Yes | |
| total_count | Yes | |
| success_count | Yes | |
| next_steps_guidance | Yes | Deterministic next-step instructions derived from this result. Not an authorization grant. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover mutability, destructiveness, and open-world behavior. The description adds critical business logic: billable calls, quote dependency, the meaning of auto_execute_eligible (waives only cost confirmation, not user prohibitions), and no silent retry. It doesn't detail rate limits or return format, but with an output schema present, that's acceptable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is dense and front-loads the cost warning, but it packs many separate instructions into one block, making it less scannable. Some sentences like 'A missing or failed quote is not free' add value, but the overall flow could be better structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the destructive, open-world annotations and the presence of an output schema, the description covers the essential preconditions and behavioral constraints. It could mention error handling or partial failure behavior, but the core guidance is sufficient for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 67%, and the description adds important semantics: tool names must be exact without client prefix, session_id reuse guidance, and 1-20 call limit. It doesn't explain search_id, but the schema description for search_id is already clear enough.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb and resource: 'Execute 1 to 20 independent published-tool calls', and the title matches. It distinguishes itself from batch_quote by requiring a quote first, but doesn't explicitly contrast with the singular 'use' sibling, though that's implied by 'batch'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit when-to-use and when-not-to-use conditions: only after a successful batch_quote with auto_execute_eligible=true or explicit user authorization. It also states re-quote conditions and prohibits silent retries, leaving little ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_dataforseo_backlinks_indexBacklinks IndexBRead-onlyIdempotentInspect
This endpoint will provide you with the total number of backlinks, domains, and pages our database contains for the moment when you make a request. You will also get stats for the last 12 months.
Usage-based billing; Default request estimate: $0.012 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the full safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower. The description adds value by specifying that the data is a live snapshot at request time plus a trailing 12-month series, and the pricing block discloses billing behavior; it does not, however, discuss rate limits or response shape.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The two purpose sentences are front-loaded and waste-free, answering what the endpoint returns immediately. The trailing pricing boilerplate and a stray leading formatting character are minor detractions.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, return values need not be explained in prose, and annotations cover safety; the description adequately conveys what the tool reports and that it needs no inputs. It is essentially complete for a zero-parameter read tool, missing only sibling routing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so schema coverage and parameter-semantics burden are effectively absent; baseline 4 applies. The description correctly implies no input is required ('the moment when you make a request').
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource and verb: it returns the total number of backlinks, domains, and pages in the database, plus 12-month stats. This 'index totals' function is conceptually distinct from the target-specific siblings, but the description never names or contrasts any sibling tool, so an agent must infer the distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives among the many get_semrush_* and post_dataforseo_backlinks_* siblings. The intended usage (fetching global index size rather than per-target metrics) is only implied by the purpose sentence.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_semrush_backlink_anchorsBacklink AnchorsDRead-onlyIdempotentInspect
Usage-based billing; Default request estimate: $0.08 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | ||
| target_type | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, covering the safety profile. The description adds only a cost estimate (~$0.08, usage-based, variable), which is genuinely useful pre-call context, but it says nothing about scope, rate limits, or what a call actually returns.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The text is short, but every sentence is about billing rather than the tool's function. It is not bloated so much as misallocated — the space is spent on metadata instead of the core purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists so return values need not be documented, but for a two-parameter tool with no parameter documentation and no stated purpose, the description is completely inadequate to guide a correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Both required parameters (target, target_type) have 0% schema description coverage and the description explains neither. The meaning of target_type in particular is left entirely to guesswork.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description never states what the tool does. It contains only a billing/pricing notice, so an agent cannot tell that this retrieves backlink anchor data, nor distinguish it from the many sibling backlink endpoints.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no mention of alternatives such as get_semrush_backlinks or the DataForSEO anchor tools, and no exclusions. The description offers zero routing information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_semrush_backlink_competitorsBacklink CompetitorsDRead-onlyIdempotentInspect
Usage-based billing; Default request estimate: $0.08 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | ||
| target_type | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered without help. The description's only contribution beyond structured data is the usage-based cost estimate (~$0.08, variable), which is genuine behavioral context an agent cannot get elsewhere — but it says nothing about response shape, limits, or what 'competitors' means in practice.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is short, but the length is spent on HTML-comment-wrapped pricing markup rather than tool semantics. There is no front-loaded sentence describing the operation, so the structure is efficient only in the sense of being near-empty.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values needn't be explained, but everything else is missing: no statement of the operation, no clarification of the two required parameters at 0% coverage, and no distinction from a large family of near-identical backlink endpoints. For a tool in a crowded sibling set, this is inadequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and both required parameters (target, target_type) are undocumented in the schema. The description adds nothing — notably it never clarifies what values target_type accepts (domain vs. URL) or how target is interpreted, leaving an agent to guess on a required field.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description contains no statement of what the tool does; it is entirely a billing/pricing notice. An agent reading it learns only that requests cost roughly $0.08, not that the tool returns competitor backlink data for a target. The title 'Backlink Competitors' is the sole clue, and that is a restatement of the name rather than a described purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no mention of related endpoints, and no differentiation from siblings such as get_semrush_backlinks, get_semrush_referring_domains, or post_dataforseo_backlinks_competitors_live. The only usable signal is an implicit cost warning, which does not tell an agent when this tool is the right choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_semrush_backlinksBacklinksDRead-onlyIdempotentInspect
Usage-based billing; Default request estimate: $0.08 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | ||
| target_type | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The pricing note is genuinely useful cost context ($0.08 default estimate, not fixed), but it is generic boilerplate that says nothing about this operation's behavior, scope, or limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is short, but brevity here comes from omission rather than conciseness. The text is a pricing banner rather than a tool definition, and nothing about the tool's purpose is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With two undocumented required parameters and no purpose statement, the definition is inadequate regardless of the existing output schema. An agent cannot confidently select or invoke this tool over its numerous siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for two required parameters ('target' and 'target_type'), and the description provides no compensating detail. The agent has no idea what format 'target' expects (domain, URL, path) or what values 'target_type' accepts.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description never states what the tool does. Its entire content is an auto-injected pricing disclaimer, so the agent learns nothing about the operation beyond what the name 'get_semrush_backlinks' and title 'Backlinks' already imply.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no mention of alternatives, and no differentiation from the many backlink siblings such as get_semrush_backlinks_overview, get_semrush_backlink_anchors, or get_semrush_referring_domains.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_semrush_backlinks_overviewSemrush Backlinks OverviewDRead-onlyIdempotentInspect
Published reference price: $0.004 USD per successful request. Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The only real contribution is the pricing disclosure ($0.004 per successful request), which is genuinely useful cost context, but the description says nothing about what the call does, what it returns, or any limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The text is short and cleanly formatted, but it is entirely off-topic relative to the tool's function; every sentence is about pricing rather than the operation. Brevity here reflects missing content, not efficient writing.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value explanation is not required, yet the description omits purpose, usage context, and parameter meaning for a live external-API tool. It is not remotely complete for an agent to select and invoke it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and the single required parameter 'target' has no description anywhere. The description does not clarify whether 'target' is a domain, URL, or path — the one piece of information that would most help an agent invoke this correctly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description contains no functional statement at all — it is purely a pricing notice. Nothing tells the agent that this tool returns a Semrush backlinks overview for a target, nor how it differs from siblings like get_semrush_backlinks or get_semrush_referring_domains.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no prerequisite information, and no reference to any alternative among the many sibling backlink tools. The agent has to infer applicability from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_semrush_indexed_pagesIndexed PagesDRead-onlyIdempotentInspect
Usage-based billing; Default request estimate: $0.08 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | ||
| target_type | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description does add one genuinely non-annotation behavioral fact: usage-based billing with a ~$0.08 default estimate and the caveat that final settlement may differ — useful for an agent weighing cost. It says nothing, however, about rate limits, result scope, or what the call actually returns.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Brief, but the content is pricing boilerplate fenced in HTML comment markers rather than functional information, so there is nothing meaningful that is 'front-loaded'. It is short by omission of substance, not by editorial discipline.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described. But for a tool with two undocumented required parameters, a crowded sibling set of Semrush/DataForSEO backlink tools, and zero functional description, the definition leaves the agent unable to select or invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Both required parameters (target, target_type) have 0% schema description coverage, and the description contributes nothing about them — not the valid values for target_type, not the accepted target formats (domain vs URL), not whether these are mutually constrained. With two undocumented required params the description is required to compensate and does not.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description text contains no statement of what the tool does — it is entirely a pricing/billing disclaimer wrapped in HTML comments. Only the name and title ('Indexed Pages') hint at the resource, and nothing distinguishes it from siblings like get_semrush_backlinks or get_semrush_referring_domains. This is effectively a tautological restatement at best.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no alternatives, no prerequisites, no mention of the sibling tools that retrieve related Semrush link data. An agent has nothing to route on.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_semrush_referring_domainsReferring DomainsDRead-onlyIdempotentInspect
Usage-based billing; Default request estimate: $0.08 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| target | Yes | ||
| target_type | Yes |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only a default cost estimate and billing caveat, which is useful but not a substantive behavioral trait about the operation itself.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short but does not earn its place: it is entirely pricing boilerplate wrapped in HTML comment markers. It is not front-loaded with any actionable purpose or usage information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with two required parameters, no parameter documentation, and many similar sibling tools, the description is completely inadequate. The presence of an output schema does not compensate for the absence of purpose, usage, and parameter guidance.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the two required parameters (target and target_type) are undocumented in both the schema and description. The description provides no meaning, format, or allowed values for either parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description does not state what the tool does. It only contains pricing metadata, leaving the tool's purpose to be inferred entirely from the name/title and sibling context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as post_dataforseo_backlinks_referring_domains_live or other Semrush backlink tools. The pricing note does not help an agent choose the correct tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_categoriesBrowse the AIsa catalogueARead-onlyInspect
The AIsa catalogue at a glance: categories, the servers in each, tool counts, and the dedicated endpoint to connect if you only need one category. Free. (AIsa-only: tool-router has no equivalent.) Use mcp.aisa.one/mcp?modules=<category> (or mcp.aisa.one/<category>/mcp) to have that category's tools listed directly instead of via search.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that this is a safe, read-only, closed-world operation. The description adds useful context beyond annotations by saying it returns categories, servers, tool counts, and the dedicated endpoint, and that it is free. It omits auth/rate-limit details, but those are less critical given the read-only annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with what the tool returns and is generally efficient. The parenthetical about tool-router and the endpoint URL add some density, but each part contributes usage or content context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With zero parameters, read-only annotations, and an output schema available, the description supplies enough context for correct invocation. It explains the catalogue contents and gives the category-specific endpoint alternative, leaving no critical gap for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so parameter semantics are not a meaningful differentiator. The schema has no properties to explain, and the description does not need to document any inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that this tool gives a catalogue overview: categories, servers per category, tool counts, and a dedicated endpoint. The resource is specific and recognizable, though sibling differentiation is only partial because it references 'tool-router' rather than the listed siblings like search/use.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives a clear alternative: use the category-specific endpoint if you only need one category, rather than going via search. It also notes the tool is free and AIsa-only, but it does not explicitly state when to call list_categories instead of search or use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_anchors_liveAnchorsBDestructiveInspect
This endpoint will provide you with a detailed overview of anchors used when linking to the specified website with relevant backlink data for each of them.
Usage-based billing; Default request estimate: $0.033 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already carry the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true). The description adds one piece of context not in the annotations — the usage-based billing estimate of ~$0.033 per request — which is genuinely useful for an agent deciding whether to call. It adds nothing about rate limits, auth, or what the 'live' retrieval semantics mean, and it does not reconcile the odd destructive annotation with what is evidently a data-retrieval operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One tight sentence that states the resource and its payload, front-loaded with no preamble. The appended pricing block is boilerplate but short and informative. Nothing is padded or repeated from the schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described, and the nested schema documents the 13 optional request fields. What is missing for a tool of this complexity is routing context: why pick 'anchors' over the many sibling backlinks endpoints, and any note about the 'live' retrieval/billing model beyond the price estimate. Adequate but with a clear routing gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Top-level schema description coverage is 0% (the single 'body' array wrapper is undocumented), and the description adds no parameter meaning at all — no mention of target, filters, limit, or order_by. However, the nested schema entries carry very detailed prose for target, limit, offset, filters, order_by, rank_scale, and the backlink scope switches, plus a worked example, so an agent can construct a request from the schema alone. Schema does the heavy lifting; the description contributes nothing.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb and resource: it returns 'a detailed overview of anchors used when linking to the specified website with relevant backlink data for each of them.' The resource (anchors for a target's backlinks) is unambiguous and distinct from the sibling referring-domain/backlinks endpoints by name and content. It does not, however, explicitly contrast itself with the other anchor/backlink endpoints an agent could pick.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no prerequisites, and no mention of alternatives. With ~30 sibling endpoints in the same backlinks family (e.g. post_dataforseo_backlinks_backlinks_live, post_dataforseo_backlinks_referring_domains_live, get_semrush_backlink_anchors), the agent gets no help deciding when anchor data is the right choice. Usage is only implied by the word 'anchors'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_backlinks_liveBacklinksCDestructiveInspect
This endpoint will provide you with a list of backlinks and relevant data for the specified domain, subdomain, or webpage.
Usage-based billing; Default request estimate: $0.06 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description depicts a pure retrieval ('provide you with a list of backlinks'), yet annotations declare readOnlyHint=false and destructiveHint=true. This is a direct conflict that could mislead an agent about the safety profile, and the description offers no behavioral context (rate limits, billing scope beyond boilerplate, idempotency) to resolve it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The functional sentence is short and front-loaded, and the pricing note is compact. No filler prose, though the description is arguably too terse for the surface area it covers.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists so return values need not be explained, but for a 12-field filtering/pagination endpoint with heavy siblings the description omits usage routing and key behavioral caveats. It is under-specified relative to the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage on the top-level parameter is reported at 0%, and the description says nothing about the body arguments (mode, limit, offset, filters, order_by, rank_scale, backlinks_status_type, etc.). The nested schema carries detailed field docs, but the description itself adds no parameter meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (provide a list) and resource (backlinks) and names the accepted targets (domain, subdomain, or webpage). It is clear what the tool does, but it does not differentiate itself from the many sibling backlinks endpoints (anchors, summary, referring_domains, competitors), so the agent must infer selection from the name alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this endpoint versus the numerous alternatives in the sibling list. The description gives no conditions, prerequisites, or exclusions, leaving the agent to guess from the tool name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_bulk_backlinks_liveBulk BacklinksADestructiveInspect
This endpoint will provide you with the number of backlinks pointing to domains, subdomains, and pages specified in the targets array. The returned numbers correspond to all live backlinks, that is, total number of referring links with all attributes (e.g., nofollow, noreferrer, ugc, sponsored etc) that were found during the latest check.
Usage-based billing; Default request estimate: $0.024 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true), so the bar is lower. The description still adds real context beyond that: the figures are counts of ALL live backlinks including every attribute (nofollow, noreferrer, ugc, sponsored) and reflect the latest check, which directly shapes interpretation of the result. The embedded billing note also flags cost, a behavioral trait annotations do not carry. Rate limits/auth are not mentioned, keeping it from a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The core purpose is front-loaded in the first sentence and the second sentence adds genuinely useful clarification about what the counts include. The stray zero-width characters and the templated pricing block add minor noise, but overall it is tight and readable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter live endpoint with an output schema, the description covers the essential ground: what is returned and how to interpret it. Return value structure is handled by the output schema, so it need not explain it. The main gap is absent routing guidance against the many sibling backlinks endpoints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description points at the targets array and clarifies it accepts domains, subdomains, and pages, which is meaningful. It says nothing about the tag identifier, the 1000-target limit, or the domain-vs-absolute-URL formatting rules. The reported schema coverage is 0% at the top level, so the description does not fully compensate, though the schema's nested field descriptions carry most of the format detail.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb and resource: it returns the 'number of backlinks' for domains, subdomains, and pages in the targets array. This distinguishes it from list-style siblings like post_dataforseo_backlinks_backlinks_live (which returns actual backlinks) and scopes it to counts. However, it never explicitly contrasts itself with the many other backlinks siblings (anchors, referring_domains, summary), so differentiation is left to inference.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use or when-not-to-use guidance, no named alternative, and no prerequisites. An agent must infer from the name and sibling list why it would pick this bulk endpoint over the single-target backlinks_live or the bulk_* variants. Pricing boilerplate is present but is not usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_bulk_new_lost_backlinks_liveBulk New & Lost BacklinksCDestructiveInspect
This endpoint will provide you with the number of new and lost backlinks for the domains, subdomains, and pages specified in the targets array.
Usage-based billing; Default request estimate: $0.06 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description frames a pure data-retrieval operation ('will provide you with the number of new and lost backlinks'), which contradicts the annotations readOnlyHint=false and destructiveHint=true. Per the rubric this mismatch caps the score at 1. Beyond the pricing note, no other behavioral traits (limits, auth, latency, idempotency) are disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One efficient, front-loaded sentence states the core purpose, followed by a short auto-generated pricing block. It is appropriately sized for the operation, with only the leading whitespace and boilerplate pricing as minor noise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described. However, for a bulk, date-sensitive endpoint with rich nested parameter semantics, the description omits the date-range mechanics, the target-format rules, and any routing guidance, leaving an agent under-informed despite the otherwise complex schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is reported at 0%, so the description must carry the burden, but it only alludes to the 'targets array' and never explains the domain-without-https/www vs. absolute-page-URL rule, the 1000-target cap, the date_from default (today minus one month) or its one-year minimum. It also fails to signal that targets is effectively required even though the outer schema lists no required parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('provide you with the number of') and a specific resource (new and lost backlinks) plus its scope (bulk, domains/subdomains/pages in the targets array). It is clearly distinguishable from a plain backlinks listing, though it never explicitly contrasts itself with the very close sibling post_dataforseo_backlinks_timeseries_new_lost_live.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to choose this endpoint over alternatives such as bulk_backlinks_live or timeseries_new_lost_live, no prerequisites, and no exclusions. Usage can only be inferred from the word 'bulk' and the word 'live' in the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_bulk_new_lost_ref_domains_liveBulk New & Lost Referring DomainsCDestructiveInspect
This endpoint will provide you with the number of referring domains pointing to the domains, subdomains and pages specified in the targets array.
Usage-based billing; Default request estimate: $0.06 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare openWorldHint=true, destructiveHint=true, idempotentHint=false, so the safety profile is carried structurally. The description adds genuinely useful billing context ('Default request estimate: $0.06 USD, not a fixed price'), but it never reconciles the read-flavored 'will provide you with' phrasing with a destructiveHint=true annotation, and says nothing about auth, rate limits, or task/queue behavior. No direct contradiction, but the tension is left unexplained.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The substantive text is a single front-loaded sentence with no padding, and the pricing note is clearly delimited. It is docked only for the stray leading zero-width character before the first sentence, which is a formatting artifact rather than a content problem.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be documented, and the request schema is detailed. However, for an endpoint whose whole point is comparing new versus lost referring domains over a bounded historical window, the description never mentions the time-range semantics or the one-year lookback constraint that an agent needs to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is reported at 0%, so the description is expected to compensate, and it does not. It names only 'targets array' while the request body also carries tag and date_from, and it adds no syntax, format, or limit information ('up to 1000 domains', date format) beyond what the schema already happens to spell out.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a verb and resource ('provide you with the number of referring domains'), which is clear on its face, but it omits the defining 'new & lost' time-window dimension that lives only in the title. That omission makes it read like the sibling post_dataforseo_backlinks_bulk_referring_domains_live, so an agent cannot distinguish the two from the description alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no mention of when to prefer this over the bulk referring-domains or timeseries_new_lost siblings, and no prerequisites. The only non-purpose sentence is injected pricing boilerplate, which is not usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_bulk_pages_summary_liveBulk Pages SummaryBDestructiveInspect
This endpoint will provide you with a comprehensive overview of backlinks and related data for a bulk of up to 1000 pages, domains, or subdomains. If you indicate a single page as a target, you will get comprehensive summary data on all backlinks for that page.
Usage-based billing; Default request estimate: $0.0242 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false, and the description does not explain this read-flavored "live" retrieval endpoint's destructive label — a notable gap. It does, however, add value beyond the annotations by disclosing usage-based billing with a concrete per-request estimate (~$0.0242 USD), which is useful operational context for a paid endpoint.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core capability and capacity limit, with the single-target case as a follow-on. Slightly verbose phrasing ("This endpoint will provide you with") and a large billing block, but nothing is padding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists so return values need not be described, and the billing note covers cost awareness. But for a 1000-target bulk endpoint, the description omits the operational constraint that URLs in one request cannot span more than 100 domains (present only in schema text) and gives no guidance on sibling selection, leaving it minimally adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Measured top-level schema coverage is 0% (no description on the `body` wrapper), but the nested properties in the schema are richly documented (targets URL format rules, rank_scale enum, include_subdomains default). The description only echoes the "up to 1000 pages, domains, or subdomains" capacity and adds no format or constraint detail beyond that, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource — "provide a comprehensive overview of backlinks and related data" — and scopes it to a bulk of up to 1000 pages, domains, or subdomains, which meaningfully separates it from single-target summary siblings. However, it never names the closely competing siblings (post_dataforseo_backlinks_summary_live, post_dataforseo_backlinks_domain_pages_summary_live), so an agent must infer the boundary from the word "bulk" alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description only notes that a single-target request returns summary data for that one page, which describes behavior rather than when to prefer this tool over the many other summary endpoints. There is no statement of when-not-to-use it, no prerequisites, and no routing to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_bulk_ranks_liveBulk RanksBDestructiveInspect
This endpoint will provide you with rank scores of the domains, subdomains, and pages specified in the targets array. The score is based on the number of referring domains pointing to the specified domains, subdomains, or pages. The rank values represent real-time data for the date of the request and range from 0 (no backlinks detected) to 1,000 (highest rank). A similar scoring system is used in Google’s Page Rank algorithm. You can learn more about rank scores in this help center article
Usage-based billing; Default request estimate: $0.025 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds useful behavioral context — real-time data for the request date and a usage-based cost estimate ($0.025) — but does not explain why a data-retrieval endpoint carries a destructive hint (credit consumption) or address rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The core paragraph is front-loaded and efficient, defining the output and its meaning in a few sentences. The appended pricing block is boilerplate but compact and clearly delimited, so it does not obscure the main content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, return values need not be described, and the description adequately covers the operation, the rank scale, and its real-time nature for a simple single-parameter tool. The main omission is routing guidance relative to the numerous sibling backlinks endpoints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Reported schema description coverage is 0% for the single top-level 'body' parameter, so the description carries extra weight; it references the 'targets array' and the rank range (0–1000). However, it does not explain the 'rank_scale' toggle or the 'tag' identifier beyond what the nested schema already documents, so it does not fully compensate for the coverage gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: it returns rank scores for the domains, subdomains, and pages passed in the targets array, and explains the scoring basis (number of referring domains). This clearly separates it from siblings like bulk_backlinks or bulk_referring_domains. It stops short of explicitly naming which sibling to prefer, but the resource is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this endpoint versus the many sibling backlinks endpoints (e.g., bulk_spam_score, bulk_pages_summary), and no mention of prerequisites or exclusions. The description explains the concept of a rank score but never says in what situation an agent should choose this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_bulk_referring_domains_liveBulk Referring DomainsCDestructiveInspect
This endpoint will provide you with the number of referring domains pointing to domains, subdomains, and pages specified in the targets array. The returned numbers are based on all live referring domains, that is, total number of domains pointing to the target with any type of backlinks (e.g., nofollow, noreferrer, ugc, sponsored etc) that were found during the latest check.
Usage-based billing; Default request estimate: $0.0254 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description frames a pure data-retrieval query ('will provide you with the number...'), which is incompatible with the annotations declaring destructiveHint=true and readOnlyHint=false. It also omits rate limits, auth needs, and the 1000-target ceiling. The one genuine disclosure — that counts cover all live referring domains regardless of link type (nofollow, ugc, sponsored) as of the latest check — does not offset the behavioral-profile contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two front-loaded sentences that lead with the tool's function, followed by a short billing note. No filler or repetition; the only mild bloat is the pricing boilerplate, which is at least actionable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value explanation is not required, and the description adequately covers what data is produced. It is still incomplete for a mutation-annotated, open-world endpoint: no usage routing, no auth/limit context, and the destructive/read-only mismatch is left unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is reported at 0% for the top level, so the description must carry the load; it names the 'targets array' and clarifies that domains, subdomains, and pages can be supplied, which is the most important semantic. However it says nothing about the `tag` identifier, the 1000-target limit, or the URL-formatting rules (no https://www. for domains, absolute URL for pages), so it only partially compensates.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: it returns the number of referring domains for the domains/subdomains/pages in the targets array. This clearly distinguishes it from anchor or backlink endpoints, but it never differentiates itself from its closest sibling, post_dataforseo_backlinks_referring_domains_live (the non-bulk variant) or post_dataforseo_backlinks_bulk_new_lost_ref_domains_live, so the 'bulk' scope advantage is left implicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no mention of prerequisites (auth/API key), and no named alternative. The description only says what the endpoint returns, leaving the agent to infer when this beats the single-target referring-domains endpoint or the new/lost variant.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_bulk_spam_score_liveBulk Spam ScoreBDestructiveInspect
This endpoint will provide you with spam scores of the domains, subdomains, and pages you specified in the targets array. Spam Score is DataForSEO’s proprietary metric that indicates how “spammy” your target is on a scale from 0 to 100. You can learn more about Spam Score, how it is calculated, and signals it takes into account in this help center article
Usage-based billing; Default request estimate: $0.06 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare openWorldHint, non-idempotency, and a destructive flag; the description does not explain or reconcile that destructive flag with what reads like a pure data-retrieval call, and says nothing about latency despite the 'live' endpoint name. It does add genuine behavioral value by disclosing usage-based billing with a $0.06 USD default per-request estimate, which helps an agent judge cost before calling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three purposeful sentences that lead with what the endpoint returns, then define the metric, then point to external documentation. The only noise is a stray zero-width character and the boilerplate pricing comment block, which is nonetheless useful information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple (one array parameter), has an output schema, and the description covers purpose, metric definition, and cost. However it omits any selection guidance among ~25 sibling backlinks endpoints and never addresses the destructive/non-idempotent annotation, which is the biggest remaining gap for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Reported schema description coverage is 0% at the top level, but the description explicitly names the 'targets array' and clarifies that domains, subdomains, and pages are accepted. The formatting rules (no https://www for domains, absolute URLs for pages, up to 1000 targets) live in the nested schema rather than the description, so this compensates partially but not fully.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a concrete verb and resource: it returns spam scores for the domains, subdomains, and pages supplied in the targets array, and defines the metric's 0-100 scale. An agent can tell this apart from other backlinks endpoints by the 'spam score' resource, though the description never explicitly contrasts itself with siblings such as post_dataforseo_backlinks_bulk_ranks_live.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to choose this tool versus the many sibling bulk/backlinks endpoints, no prerequisites, and no stated exclusions. The only implicit context is 'use it when you want spam scores for a list of targets', which the agent could infer from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_competitors_liveCompetitorsCDestructiveInspect
This endpoint will provide you with a list of competitors that share some part of the backlink profile with a target website, along with a number of backlink intersections and the rank of every competing website.
Usage-based billing; Default request estimate: $0.0276 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=false and destructiveHint=true even though the description frames this as a passive 'provide you with a list' data-retrieval endpoint, creating real tension an agent must resolve. The description adds no behavioral context of its own beyond a boilerplate pricing estimate; it does not explain the POST semantics, whether anything is mutated, auth requirements, or rate limits. Only the cost note counts as added value.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The core sentence is a single, front-loaded statement of what the endpoint returns, with no wasted prose. The appended pricing block is templated boilerplate, and the leading zero-width/whitespace characters are slightly untidy, but overall the structure is efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so the description need not explain return values, and the input schema documents the individual fields. What is missing is the context that matters for a paid, ambiguously-annotated POST endpoint: why to pick it, and any reassurance about its real read-only nature versus the destructiveHint annotation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description contributes no parameter information whatsoever. Although the context signal reports 0% schema description coverage, the underlying schema actually documents target, limit, offset, filters, order_by, rank_scale, main_domain, and the exclusion flags in rich detail, so the schema effectively carries the load while the top-level 'body' wrapper remains undocumented in both places.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: it returns a list of competitors sharing part of a target site's backlink profile, plus backlink intersections and competitor ranks. This is far more concrete than the bare title 'Competitors'. It does not, however, distinguish itself from adjacent siblings like post_dataforseo_backlinks_domain_intersection_live or referring_domains_live, which an agent could easily confuse it with.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description says what the endpoint returns but never states when to choose it over the many sibling backlink tools (domain_intersection, referring_domains, page_intersection). There is no mention of prerequisites, cost awareness for the paid call, or any exclusion criteria, leaving the agent to infer usage entirely from the resource name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_domain_intersection_liveDomain IntersectionBDestructiveInspect
This endpoint will provide you with the list of domains pointing to the specified websites. This endpoint is especially useful for creating a Link Gap feature that shows what domains link to your competitors but do not link out to your website.
Usage-based billing; Default request estimate: $0.06 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description does add one piece of behavioral context the annotations do not carry: usage-based billing with a ~$0.06 default estimate. Otherwise it says nothing about the safety profile, and its framing as a pure retrieval sits awkwardly against annotations declaring readOnlyHint=false / destructiveHint=true. Because the text never affirmatively claims non-destructiveness, this reads as tension rather than an outright contradiction, but it leaves an agent guessing about the actual mutation/billing side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences plus a short billing note, with the purpose front-loaded before the use case. It is let down only by formatting noise — a leading zero-width space and an injected HTML comment block (aisa-pricing) that may render as raw markup in some clients.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described, and the nested schema documents the request options. What is missing for a tool this configurable is any hint of sibling routing (domain vs. page intersection) and the required 'targets' field. Adequate but with visible gaps for a heavily parameterized endpoint.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is reported at 0% for the single top-level 'body' parameter, so the description carries the burden of compensating and it does not: no parameter is named, and even the fact that 'targets' is a required field inside the body is never surfaced. The nested schema does document the options in detail, but the description contributes zero parameter meaning on its own.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a concrete verb and resource: it returns the list of domains that link to the specified websites, and it adds a real-world framing (Link Gap: domains linking to competitors but not to you). It goes beyond the redundant title 'Domain Intersection'. It stops short of explicitly distinguishing itself from near-neighbours such as post_dataforseo_backlinks_page_intersection_live or post_dataforseo_backlinks_competitors_live, which is why it is not a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
One usage context is asserted ('especially useful for creating a Link Gap feature'), which implies when a caller would reach for this tool. However, there is no when-not-to-use guidance and no routing against the many sibling intersection/competitor/referring-domain endpoints. Usage is implied by example rather than stated as a rule.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_domain_pages_liveDomain PagesCDestructiveInspect
This endpoint will provide you with a detailed overview of domain pages with backlink data for each page.
Usage-based billing; Default request estimate: $0.0276 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=false and destructiveHint=true, implying a state-changing/destructive POST, while the description frames the tool purely as a data-retrieval endpoint ("will provide you with... data") with no mention of any mutation, side effect, or reason the operation would be destructive. No permissions, rate limits, or freshness/caching behavior are disclosed either, so the description adds nothing to — and in fact conflicts with — the annotation profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The text is short, front-loaded, and free of padding; the price note is compact and potentially useful for cost-aware selection. It is under-specified rather than bloated, so it is not penalized for length.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex backlinks endpoint with many nested filter/sort options, the description is essentially one generic sentence. An output schema exists so return values need not be explained, but selection guidance, the required target format, and any behavioral context are all missing, leaving the agent reliant on the schema alone.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is reported at 0% for the single top-level parameter (body), and the description says nothing about any parameter — not target, limit/offset, filters, order_by, rank_scale, backlinks_status_type, or include_subdomains. With low coverage the description is expected to compensate, and it does not.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description gives a verb+resource ("provide... a detailed overview of domain pages with backlink data for each page"), which is more specific than the bare title "Domain Pages". However, "detailed overview" is vague and it makes no attempt to distinguish this tool from the near-identical sibling post_dataforseo_backlinks_domain_pages_summary_live, nor from post_dataforseo_backlinks_backlinks_live. An agent cannot tell from the text alone which of the domain-pages endpoints it wants.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use guidance, no when-not-to-use exclusion, and no mention of any alternative sibling endpoint. The only extra sentence is pricing boilerplate, which tells the agent nothing about tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_domain_pages_summary_liveDomain Pages SummaryCDestructiveInspect
This endpoint will provide you with detailed summary data on all backlinks and related metrics for each page of the target domain or subdomain you specify. If you indicate a single page as a target, you will get comprehensive summary data on all backlinks for that page.
Usage-based billing; Default request estimate: $0.0276 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description frames this purely as passive retrieval ('provide you with detailed summary data'), yet the annotations declare readOnlyHint=false and destructiveHint=true. The description and the structured safety profile tell the agent opposite things about whether this mutates state, which is a direct contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences, purpose front-loaded, followed by the pricing note. Nothing is wasted, though the second sentence partly restates the first for the single-page case.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, and the annotations (however inconsistent) do carry a safety profile. However, the description omits usage guidance and sibling routing, which is the main gap for a tool surrounded by many near-identical backlinks endpoints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The top-level 'body' parameter has no description (coverage 0%), but the nested object properties carry rich documentation. The description only restates the domain/subdomain-vs-page target distinction that the schema already specifies, adding no syntax or filtering detail of its own. Baseline 3 is appropriate since the nested schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: it returns summary backlink data 'for each page of the target domain or subdomain', and explicitly handles the single-page case. This distinguishes it reasonably well from the domain-level summary sibling, though it never names that sibling. Clear purpose, but sibling differentiation is left implicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no when-to-use guidance, no prerequisites, and no comparison against the many sibling tools (e.g. post_dataforseo_backlinks_summary_live for whole-domain metrics vs post_dataforseo_backlinks_domain_pages_live). An agent must infer the choice from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_history_liveBacklinks HistoryBDestructiveInspect
This endpoint will provide you with historical backlinks data back to the beginning of 2019. You can receive the number of backlinks a given domain had in a specific time period, the number of new & lost backlinks, referring domains, and more.
Usage-based billing; Default request estimate: $0.0271 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds genuinely useful behavioral context beyond the annotations, notably the 2019-to-present data coverage window and the usage-based billing note with a ~$0.0271 default request estimate. However, it frames the call purely as data retrieval while the annotations declare readOnlyHint=false and destructiveHint=true, and the description never reconciles that tension or explains what the call costs/destroys at a side-effect level.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two front-loaded sentences give the capability and the data window with no wasted words. The appended pricing boilerplate is verbose but appears to be a mandatory block rather than author-written padding. A stray leading character and the long pricing comment slightly hurt the structure.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described, and the description correctly covers the data availability window and cost. What is missing is any disambiguation from the many sibling backlinks endpoints and any note on required inputs, which matters for an agent choosing among ~25 similar tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is reported as 0% for the top-level parameter, so the description must compensate, and it only partially does: "a given domain" implies target and "a specific time period" implies date_from/date_to. It says nothing about date format, the 2019-01-01 minimum, the default endpoint date, or the rank_scale option, all of which remain undocumented at the description level.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: it returns historical backlinks data for a domain back to January 2019, including backlink counts, new/lost links, and referring domains. That is enough to identify the tool's output. It does not differentiate itself from close siblings such as post_dataforseo_backlinks_timeseries_summary_live or post_dataforseo_backlinks_summary_live, which the description's metric list also describes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to choose this endpoint over the many sibling backlinks endpoints (live vs bulk vs timeseries vs summary), and no prerequisites are stated. The only conditional information is an implicit "specific time period", with nothing about defaults or limits. An agent must infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_page_intersection_livePage IntersectionBDestructiveInspect
This endpoint will provide you with the list of referring pages pointing to the specified targets. It is especially useful for finding the backlinks that point to your competitors but don’t point to your website.
Usage-based billing; Default request estimate: $0.033 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds the usage-based billing estimate ($0.033 default), a genuinely useful behavioral trait not present in annotations or schema. However, it says nothing about the destructiveHint=true / readOnlyHint=false annotations, so an agent reading only the prose would assume a harmless read while the annotations declare a destructive, non-idempotent call; the discrepancy is left unexplained.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight, front-loaded sentences with the purpose first and the use case second; the pricing note is clearly delimited by comment markers. Minor deduction for the stray zero-width character at the start and for the fact that the most decision-relevant differentiator (page- vs domain-intersection) is absent.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described, and the annotations carry the safety profile. For a tool with a single required-empty body parameter that the provider actually marks as a required field (targets), and with ~30 closely related backlinks siblings, the description should do more to place the tool in that family and warn that targets is effectively required.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The reported top-level schema description coverage is 0% and the description adds no parameter detail of its own. In practice the nested item properties (targets, limit, offset, filters, order_by, intersection_mode, etc.) are documented exhaustively inside the schema, so an agent is not left blind, but the description itself contributes nothing beyond the schema for a tool whose key parameter (body) is undocumented at the top level.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: it returns "the list of referring pages pointing to the specified targets," and adds a concrete analytic use case (backlinks pointing to competitors but not to your site). It does not, however, differentiate itself from the very similar sibling post_dataforseo_backlinks_domain_intersection_live, which an agent could easily confuse it with.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied through the competitor-gap example rather than stated: the agent can infer "use this for link-gap analysis over named targets," but there is no explicit when-to-use/when-not-to-use guidance and no routing to the domain-intersection or bulk alternatives. No prerequisites, limits prior to calling, or exclusions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_referring_domains_liveReferring DomainsCDestructiveInspect
This endpoint will provide you with a detailed overview of referring domains pointing to the target you specify.
Usage-based billing; Default request estimate: $0.0276 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description implies a read/query operation ('provide you with a detailed overview of referring domains'), while the annotations declare readOnlyHint=false and destructiveHint=true — an outright mismatch in the safety profile an agent would act on. The only genuinely additive behavioral fact is the auto-inserted usage-based billing estimate ($0.0276 default), which does not offset the contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One purpose sentence followed by the pricing block; the purpose is front-loaded and nothing is padded. The pricing boilerplate is auto-generated rather than authored content, which keeps this from being a crisp 5.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value explanation is not needed, but for a live POST endpoint with a single highly configurable 'body' parameter, the definition supplies neither usage context nor any parameter guidance, and its implicit read framing conflicts with the declared destructive behavior. An agent cannot call this confidently from the description alone.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description says nothing about any request field — no mention of the required 'target' format, the filter/order_by syntax, pagination via limit/offset, or the backlinks_status_type semantics. The input schema text itself is rich, but the reported description coverage is 0% and the prose contributes zero parameter meaning of its own.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('provide you with a detailed overview') and resource ('referring domains pointing to the target you specify'), so an agent knows it is a live referrer-report call. However, it offers no differentiation from close siblings such as post_dataforseo_backlinks_bulk_referring_domains_live, post_dataforseo_backlinks_referring_networks_live, or get_semrush_referring_domains, and 'overview' is vague for what is really a paginated domain list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use, when-not-to-use, or alternative-tool guidance. The agent gets no signal that this is the single-target live variant versus the bulk sibling, or when a cached/batch variant would be preferable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_referring_networks_liveReferring NetworksBDestructiveInspect
This endpoint will provide you with a detailed overview of referring IPs and subnets pointing to the target you specify.
Usage-based billing; Default request estimate: $0.0276 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true. The description's only behavioral addition beyond those structured fields is the usage-based billing estimate ($0.0276 USD, not a fixed price), which is genuinely useful cost context not present elsewhere. It does not reconcile its read-style 'provide an overview' framing with destructiveHint=true, nor explain the POST body-array invocation shape.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One front-loaded purpose sentence with no filler, followed by a short pricing notice. Nothing is wasted, though the pricing boilerplate adds visual noise to a very short description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be described. But for a tool exposing 14 nested body fields (filtering, sorting, pagination, rank scaling, subdomain/indirect-link toggles), the description omits that filtering and sorting are supported at all and never mentions the billing or the required target field. Adequate but thin against the tool's complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The reported top-level schema coverage is 0% because the single 'body' parameter carries no description, and the description itself says nothing about any parameter. However, the nested schema documents every field thoroughly (target required with https://www. formatting rules, limit default 100/max 1000, offset, filters with operators, order_by, rank_scale, network_address_type ip/subnet, backlinks_status_type, etc.), so the semantics are available to the agent even though the description does not contribute.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific resource and scope: 'detailed overview of referring IPs and subnets pointing to the target you specify.' The IP/subnet framing implicitly distinguishes it from the many referring_domain siblings, though it never names an alternative. Clear verb+resource, but no explicit sibling differentiation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use, when-not-to-use, or alternative-selection guidance. With ~25 siblings including post_dataforseo_backlinks_referring_domains_live and post_dataforseo_backlinks_bulk_referring_domains_live, the agent gets no help deciding which referring-entity endpoint to call.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_summary_liveBacklinks SummaryCDestructiveInspect
This endpoint will provide you with an overview of backlinks data available for a given domain, subdomain, or webpage.
Usage-based billing; Default request estimate: $0.024 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare openWorldHint, idempotentHint, and destructiveHint, so the description's burden is lighter, and it does add a useful usage-based pricing estimate. It says nothing, however, about the read-like nature implied by 'provide', nor how the destructive annotation should be interpreted for a data retrieval endpoint, so behavioral disclosure remains modest.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The core description is a single front-loaded sentence with no filler, and the pricing note is separated by comment markers. The leading zero-width character is a minor cosmetic flaw, but the overall structure is efficient and easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complex nested body schema, an output schema, and many sibling tools, the description is too thin. It does not explain what metrics the 'overview' includes, when to choose this over siblings, or how to interpret the contradictory annotations, leaving critical operational context missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is reported as 0%, so the description is expected to compensate for parameter meaning, but it does not. It vaguely mentions 'domain, subdomain, or webpage' without naming the target parameter, its required URL/domain format, or any of the other body fields like backlinks_filters or rank_scale.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb and resource: providing an overview of backlinks data for a domain, subdomain, or webpage. However, it does not distinguish this 'summary' endpoint from sibling tools like backlinks_live, referring_domains_live, or anchors_live, leaving the agent to infer the difference from the tool name alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no when-to-use guidance, no prerequisites, and no explicit alternatives. With over 30 sibling backlinks tools, an agent has no basis for selecting this summary endpoint over a more specific one such as post_dataforseo_backlinks_backlinks_live or post_dataforseo_backlinks_referring_domains_live.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_timeseries_new_lost_liveNew & Lost Backlinks Timeseries SummaryCDestructiveInspect
This endpoint will provide you with the number of new and lost backlinks and referring domains for the domain specified in the target field.
Usage-based billing; Default request estimate: $0.0372 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already carry the safety profile (readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false), yet the description adds no behavioral context of its own — no mention of auth, rate limits, credit consumption beyond the generic pricing boilerplate, or what the response contains. Notably, the text reads as a pure data-retrieval operation while the annotations declare it destructive and non-read-only, a tension the description never clarifies.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One focused sentence front-loads the purpose, followed by a pricing block. The core sentence is tight and wastes nothing, though the injected billing boilerplate is non-informative noise that dilutes the definition slightly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value details need not be spelled out, and the nested parameter descriptions cover the inputs. What is missing is selection guidance against the large family of sibling backlink tools and any behavioral clarification relative to the surprisingly destructive annotations, leaving the definition only adequate for a tool in such a crowded namespace.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description only points at one field ('the domain specified in the target field') and explains nothing about date_from, date_to, group_range, or include_subdomains. However, the input schema itself carries rich per-field descriptions for those nested parameters, so the structured data does most of the work and the description's contribution is marginal.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb+resource: it returns counts of new and lost backlinks and referring domains for a target domain. That is clear and concrete. It does not, however, distinguish this tool from close siblings such as post_dataforseo_backlinks_bulk_new_lost_backlinks_live or post_dataforseo_backlinks_timeseries_summary_live, so an agent cannot easily tell which new/lost variant to pick.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The text only says what the endpoint returns; it gives no when-to-use guidance, no when-not-to-use, and never names an alternative sibling. With many overlapping backlink endpoints available, a routing hint (e.g. use this vs. the bulk new/lost or timeseries_summary variants) is missing entirely.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
post_dataforseo_backlinks_timeseries_summary_liveBacklinks Timeseries SummaryBDestructiveInspect
This endpoint will provide you with an overview of backlink data for the target domain available during a period between the two indicated dates. Backlink metrics will be grouped by the time range that you define: day, week, month, or year.
Usage-based billing; Default request estimate: $0.0273 USD (not a fixed price). Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already carry a rich behavioral profile (destructiveHint=true, readOnlyHint=false, openWorldHint=true, idempotentHint=false), so the description does not need to re-state safety. It does add genuinely useful context by disclosing usage-based billing with a per-request estimate (~$0.0273), which matters for a paid live endpoint. It says nothing further about rate limits, latency, or data freshness beyond 'live'.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two front-loaded sentences state purpose and grouping, followed by a clearly delimited pricing block. Almost no waste, though the second sentence largely repeats the group_range semantics already present in the schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema exists, so return values need not be described, and annotations cover the safety profile. Purpose, the date-bounded scope, the grouping dimension, and cost are all present, which is sufficient for an agent to invoke this endpoint correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one top-level parameter (a body array) is reported at 0% top-level description coverage, but the nested schema items actually document target, date_from, date_to, group_range, rank_scale and include_subdomains in detail. The description restates the date range and the day/week/month/year grouping, which mirrors group_range in the schema rather than adding new semantics, so it sits at the baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource: it returns an overview of backlink data for a target domain, grouped into a day/week/month/year time series. That is clear enough to act on, but it never distinguishes itself from close siblings such as post_dataforseo_backlinks_summary_live or post_dataforseo_backlinks_history_live, so the 'timeseries' angle is only weakly differentiated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies a date-bounded, grouped query but gives no when-to-use guidance, no exclusions, and names no alternative among the many sibling backlink endpoints. An agent cannot tell from this text why it should pick the timeseries summary over the plain summary or history endpoints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
searchSearch AIsa tools and agent-ready plansARead-onlyInspect
Discover AIsa tools and Plans for external data or actions. Skip tasks that only need supplied content or general knowledge. For multi-step tasks, search the full goal before decomposing it. Use English; put identifiers in known_fields. If has_full_schema=false, call batch_get_schema. Next call batch_quote, not batch_use. Do not search for standalone rewriting, translation, summarization, formatting, or calculations on supplied content. For one capability, use an atomic query. Select a matching capability, date window, and metric. A Plan may cover only part of the task; assess its purpose and follow next_steps_guidance.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of additional direct tool candidates. | |
| query | Yes | Natural-language capability or task to discover. | |
| category | No | Restrict retrieval to one category. Omit to search everything. (AIsa-only: tool-router has no equivalent.) | |
| session_id | No | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. | |
| known_fields | No | Known values such as ticker, URL, provider, or identifier that improve retrieval. | |
| provider_filters | No | Optional exact catalog provider keys used to narrow retrieval (for example similarweb). Do not use display brands. Omit this field if the exact key is unknown. |
Output Schema
| Name | Required | Description |
|---|---|---|
| plan | No | |
| tools | Yes | |
| search_id | Yes | |
| session_id | Yes | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. |
| retrieval_mode | No | |
| next_steps_guidance | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds workflow behavior the annotations cannot: the has_full_schema flag gates a required batch_get_schema call, and the next step after search is batch_quote, not batch_use. It stops short of disclosing retrieval limits or catalog breadth that would push it to a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a dense run of imperatives rather than flowing prose, but each sentence carries a distinct rule (scope, language, workflow branch, negative cases, result interpretation) and the most important scoping guidance is front-loaded. Slightly more compression would help.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description need not explain return values, and it correctly avoids doing so while still referencing the output fields that drive the workflow (has_full_schema, next_steps_guidance). A mutation-free, well-annotated search tool is adequately covered, though catalog scope ('AIsa-only', no external providers) could be stated more explicitly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the structured baseline is 3. The description adds genuine meaning beyond the schema by telling the agent to write the query in English and to place tickers, URLs, providers, or identifiers in known_fields, which is non-obvious routing guidance for a nested free-form object.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb+resource: 'Discover AIsa tools and Plans for external data or actions.' It also separates this discovery step from the sibling execution tools by naming batch_get_schema, batch_quote, and batch_use and stating when each follows, so an agent can place it in the workflow without opening schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives explicit when-to-use ('tasks needing external data or actions'), when-not ('tasks that only need supplied content or general knowledge'; no standalone rewriting, translation, summarization, formatting, or calculations), and named alternatives (batch_get_schema when has_full_schema=false, batch_quote rather than batch_use). It also specifies query language and atomic-query style, leaving little to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
useRun an AIsa operationCDestructiveInspect
deprecated, use batch_use instead
| Name | Required | Description | Default |
|---|---|---|---|
| arguments | No | Arguments matching input_schema / arguments_schema | |
| search_id | No | search_id from the search that found this operation | |
| operation_id | Yes | operation_id as returned by search | |
| max_price_usd | No | Refuse the call before any spend if its quoted price is above this many USD |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the agent knows this is a state-changing, open-world operation. The description adds only the deprecation status and says nothing about what gets mutated, spend behavior (despite a max_price_usd param), or authorization needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single clause with zero waste; the deprecation notice and the replacement are front-loaded. It is terse by design for a deprecated endpoint, though it is under-specified rather than optimally efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Has an output schema and annotations, which reduces the burden, but a 4-parameter operation tool with a deprecation notice gives no information about what it executes or whether it remains functional. For an agent deciding between this and batch_use, the description is thin.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all four parameters (operation_id, arguments, search_id, max_price_usd) are already documented in the schema. The description adds no parameter meaning on top, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description never states what the tool does — no verb or resource. It only labels the tool as deprecated and points to a replacement, leaving the actual capability ('Run an AIsa operation' from the title) unexplained. An agent must infer the purpose from the title and schema alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly routes the agent to the alternative ('use batch_use instead'), which is exactly the guidance needed for a deprecated tool. It doesn't explain when, if ever, this tool should still be called (e.g., during a migration window), so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
22 tool updates
- Added
account - Removed
get_details - Changed
post_dataforseo_backlinks_anchors_live3 fields changed- added
Input schema / $defsAdded value: +{ + "Provider0A3E90081762_AisaDataforseoFilterJsonValue": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + } +} - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get anchors for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / oneOfRemoved value: -[ - { - "example": [ - { - "filters": [ - "anchor", - "like", - "%news%" - ], - "limit": 4, - "order_by": [ - "backlinks,desc" - ], - "target": "forbes.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get anchors for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -]
- Changed
post_dataforseo_backlinks_backlinks_live3 fields changed- added
Input schema / $defsAdded value: +{ + "Provider0A3E90081762_AisaDataforseoFilterJsonValue": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + } +} - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "properties": { + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "custom_mode": { + "additionalProperties": { + "type": [ + "object", + "null" + ] + }, + "description": "<em>detailed results grouping type</em><br>optional field<br>use this object to get a specific number of backlinks per <code>field</code><br>if you use <code>custom_mode</code>, then <code>mode</code> will be ignored<br>example:<br><code>\"custom_mode\": {\"field\": \"domain\", \"value\": 100}</code>", + "type": [ + "object", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>regex</code>, <code>not_regex</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"80\"]</code><p><code>[[\"page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"dofollow\",\"=\",true]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"text_pre\",\"like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "mode": { + "description": "<em>results grouping type</em><br>optional field<br>possible grouping types:<br><code>as_is</code> - returns all backlinks<br><code>one_per_domain</code> - returns one backlink per domain<br><code>one_per_anchor</code> - returns one backlink per anchor<p>default value: <code>as_is</code>", + "type": [ + "string", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks;<br><strong>Note:</strong> the maximum value is <code>20,000</code>, use the <code>search_after_token</code> if you would like to offset more results", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "search_after_token": { + "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get backlinks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / oneOfRemoved value: -[ - { - "example": [ - { - "filters": [ - "dofollow", - "=", - true - ], - "limit": 5, - "mode": "as_is", - "target": "forbes.com" - } - ], - "properties": { - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "custom_mode": { - "additionalProperties": { - "type": [ - "object", - "null" - ] - }, - "description": "<em>detailed results grouping type</em><br>optional field<br>use this object to get a specific number of backlinks per <code>field</code><br>if you use <code>custom_mode</code>, then <code>mode</code> will be ignored<br>example:<br><code>\"custom_mode\": {\"field\": \"domain\", \"value\": 100}</code>", - "type": [ - "object", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>regex</code>, <code>not_regex</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"80\"]</code><p><code>[[\"page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"dofollow\",\"=\",true]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"text_pre\",\"like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "mode": { - "description": "<em>results grouping type</em><br>optional field<br>possible grouping types:<br><code>as_is</code> - returns all backlinks<br><code>one_per_domain</code> - returns one backlink per domain<br><code>one_per_anchor</code> - returns one backlink per anchor<p>default value: <code>as_is</code>", - "type": [ - "string", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks;<br><strong>Note:</strong> the maximum value is <code>20,000</code>, use the <code>search_after_token</code> if you would like to offset more results", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "search_after_token": { - "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get backlinks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -]
- Changed
post_dataforseo_backlinks_bulk_backlinks_live1 field changed- changed
Input schema / properties / body / items / oneOfPrevious value: -[ - { - "example": [ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get the number of backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -]New value: +[ + { + "properties": { + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get the number of backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_new_lost_backlinks_live1 field changed- changed
Input schema / properties / body / items / oneOfPrevious value: -[ - { - "example": [ - { - "date_from": "2026-09-12 05:48:19", - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks;<br>the backlinks that appeared in our index after the specified date will be considered as new;<br>the backlinks that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get new & lost backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without `https://` and `www.` the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br> `\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -]New value: +[ + { + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks;<br>the backlinks that appeared in our index after the specified date will be considered as new;<br>the backlinks that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get new & lost backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without `https://` and `www.` the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br> `\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_new_lost_ref_domains_live1 field changed- changed
Input schema / properties / body / items / oneOfPrevious value: -[ - { - "example": [ - { - "datetime_from": "2026-48-12", - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost referring domains;<br>the referring domains that appeared in our index after the specified date will be considered as new;<br>the referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get new & lost referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -]New value: +[ + { + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost referring domains;<br>the referring domains that appeared in our index after the specified date will be considered as new;<br>the referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get new & lost referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_pages_summary_live1 field changed- changed
Input schema / properties / body / items / oneOfPrevious value: -[ - { - "example": [ - { - "targets": [ - "https://dataforseo.com/solutions", - "https://dataforseo.com/about-us" - ] - } - ], - "properties": { - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>you can specify up to 1000 pages, domains, or subdomains in each request.<br><strong>note that the URLs you set in a single request cannot belong to more than 100 different domains</strong>.", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -]New value: +[ + { + "properties": { + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>you can specify up to 1000 pages, domains, or subdomains in each request.<br><strong>note that the URLs you set in a single request cannot belong to more than 100 different domains</strong>.", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_ranks_live1 field changed- changed
Input schema / properties / body / items / oneOfPrevious value: -[ - { - "example": [ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -]New value: +[ + { + "properties": { + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_referring_domains_live1 field changed- changed
Input schema / properties / body / items / oneOfPrevious value: -[ - { - "example": [ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get the number of referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -]New value: +[ + { + "properties": { + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get the number of referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_spam_score_live1 field changed- changed
Input schema / properties / body / items / oneOfPrevious value: -[ - { - "example": [ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -]New value: +[ + { + "properties": { + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_competitors_live3 fields changed- added
Input schema / $defsAdded value: +{ + "Provider0A3E90081762_AisaDataforseoFilterJsonValue": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + } +} - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "properties": { + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "exclude_large_domains": { + "description": "<em>indicates whether large domain will appear in results</em><br>optional field<br>if set to <code>true</code>, the results from the large domain (google.com, amazon.com, etc.) will be omitted;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"100\"]</code><p><code>[[\"target\",\"like\",\"%forbes%\"],<br>\"and\",<br>[[\"rank\",\">\",\"100\"],\"or\",[\"intersections\",\">\",\"5\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "main_domain": { + "description": "<em>indicates if only main domain of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>true</code>, only the main domain will be included in search;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"intersections,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get competitor domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / oneOfRemoved value: -[ - { - "example": [ - { - "filters": [ - "rank", - ">", - 100 - ], - "limit": 5, - "order_by": [ - "rank,desc" - ], - "target": "dataforseo.com" - } - ], - "properties": { - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "exclude_large_domains": { - "description": "<em>indicates whether large domain will appear in results</em><br>optional field<br>if set to <code>true</code>, the results from the large domain (google.com, amazon.com, etc.) will be omitted;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"100\"]</code><p><code>[[\"target\",\"like\",\"%forbes%\"],<br>\"and\",<br>[[\"rank\",\">\",\"100\"],\"or\",[\"intersections\",\">\",\"5\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "main_domain": { - "description": "<em>indicates if only main domain of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>true</code>, only the main domain will be included in search;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"intersections,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get competitor domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -]
- Changed
post_dataforseo_backlinks_domain_intersection_live3 fields changed- added
Input schema / $defsAdded value: +{ + "Provider0A3E90081762_AisaDataforseoFilterJsonValue": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + } +} - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be omitted and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "exclude_targets": { + "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can specify up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring domains that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"2.referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"1.backlinks\",\">\",\"10\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"2.target\",\"like\",\"%dataforseo.com%\"],\"or\",[\"1.referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "intersection_mode": { + "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified domains<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", + "type": [ + "string", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned results</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the array of returned results</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "additionalProperties": { + "type": [ + "string", + "null" + ] + }, + "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", + "type": [ + "object", + "null" + ] + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / oneOfRemoved value: -[ - { - "example": [ - { - "exclude_internal_backlinks": true, - "exclude_targets": [ - "semrush.com" - ], - "include_subdomains": false, - "limit": 5, - "order_by": [ - "1.backlinks,desc" - ], - "targets": { - "1": "moz.com", - "2": "ahrefs.com" - } - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be omitted and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "exclude_targets": { - "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can specify up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring domains that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"2.referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"1.backlinks\",\">\",\"10\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"2.target\",\"like\",\"%dataforseo.com%\"],\"or\",[\"1.referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "intersection_mode": { - "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified domains<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", - "type": [ - "string", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned results</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the array of returned results</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "additionalProperties": { - "type": [ - "string", - "null" - ] - }, - "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", - "type": [ - "object", - "null" - ] - } - }, - "type": "object" - } -]
- Changed
post_dataforseo_backlinks_domain_pages_live3 fields changed- added
Input schema / $defsAdded value: +{ + "Provider0A3E90081762_AisaDataforseoFilterJsonValue": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + } +} - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"meta.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"meta.external_links_count\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_visited\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"title\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned pages</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned pages</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"page_summary.backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"page_summary.backlinks,desc\",\"page_summary.rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain or subdomain</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>forbes.com</code>", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / oneOfRemoved value: -[ - { - "example": [ - { - "filters": [ - [ - "page_summary.backlinks", - ">", - 5 - ], - "and", - [ - "page", - "like", - "%sites%" - ] - ], - "limit": 5, - "target": "forbes.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"meta.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"meta.external_links_count\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_visited\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"title\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned pages</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned pages</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"page_summary.backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"page_summary.backlinks,desc\",\"page_summary.rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain or subdomain</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>forbes.com</code>", - "type": "string" - } - }, - "type": "object" - } -]
- Changed
post_dataforseo_backlinks_domain_pages_summary_live3 fields changed- added
Input schema / $defsAdded value: +{ + "Provider0A3E90081762_AisaDataforseoFilterJsonValue": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + } +} - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, backlinks from the subdomains of the <code>target</code> domain will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> domain will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / oneOfRemoved value: -[ - { - "example": [ - { - "limit": 4, - "order_by": [ - "backlinks,desc" - ], - "target": "forbes.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, backlinks from the subdomains of the <code>target</code> domain will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> domain will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -]
- Changed
post_dataforseo_backlinks_history_live1 field changed- changed
Input schema / properties / body / items / oneOfPrevious value: -[ - { - "example": [ - { - "date_from": "2020-01-01", - "date_to": "2021-01-01", - "target": "cnn.com" - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>minimum value <code>2019-01-01</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", - "type": [ - "string", - "null" - ] - }, - "date_to": { - "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", - "type": [ - "string", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code>", - "type": "string" - } - }, - "type": "object" - } -]New value: +[ + { + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>minimum value <code>2019-01-01</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "date_to": { + "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code>", + "type": "string" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_page_intersection_live3 fields changed- added
Input schema / $defsAdded value: +{ + "Provider0A3E90081762_AisaDataforseoFilterJsonValue": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + } +} - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "properties": { + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the result<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "exclude_targets": { + "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can set up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring pages that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.rank\",\">\",\"80\"]</code><p><code>[[\"2.page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"1.original\",\"=\",\"true\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"1.acnhor\",\"like\",\"%seo%\"],\"or\",[\"1.text_pre\",\"not_like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>targets</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>attributes</code><br><code>domain_from_platform_type</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "intersection_mode": { + "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified URLs<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", + "type": [ + "string", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "additionalProperties": { + "type": [ + "string", + "null" + ] + }, + "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", + "type": [ + "object", + "null" + ] + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / oneOfRemoved value: -[ - { - "example": [ - { - "exclude_targets": [ - "skysports.com" - ], - "filters": [ - [ - "2.domain_from_rank", - ">", - 400 - ], - "and", - [ - "1.dofollow", - "=", - true - ] - ], - "limit": 5, - "order_by": [ - "1.rank,desc" - ], - "targets": { - "1": "football.com", - "2": "fifa.com" - } - } - ], - "properties": { - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the result<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "exclude_targets": { - "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can set up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring pages that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.rank\",\">\",\"80\"]</code><p><code>[[\"2.page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"1.original\",\"=\",\"true\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"1.acnhor\",\"like\",\"%seo%\"],\"or\",[\"1.text_pre\",\"not_like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>targets</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>attributes</code><br><code>domain_from_platform_type</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "intersection_mode": { - "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified URLs<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", - "type": [ - "string", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "additionalProperties": { - "type": [ - "string", - "null" - ] - }, - "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", - "type": [ - "object", - "null" - ] - } - }, - "type": "object" - } -]
- Changed
post_dataforseo_backlinks_referring_domains_live3 fields changed- added
Input schema / $defsAdded value: +{ + "Provider0A3E90081762_AisaDataforseoFilterJsonValue": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + } +} - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"domain\",\"like\",\"%dataforseo.com%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get referring domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / oneOfRemoved value: -[ - { - "example": [ - { - "backlinks_filters": [ - "dofollow", - "=", - true - ], - "exclude_internal_backlinks": true, - "filters": [ - "backlinks", - ">", - 100 - ], - "limit": 5, - "order_by": [ - "rank,desc" - ], - "target": "backlinko.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"domain\",\"like\",\"%dataforseo.com%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get referring domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -]
- Changed
post_dataforseo_backlinks_referring_networks_live3 fields changed- added
Input schema / $defsAdded value: +{ + "Provider0A3E90081762_AisaDataforseoFilterJsonValue": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + } +} - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"network_address\",\"like\",\"194.1.%\"],\"or\",[\"referring_ips\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned networks</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "network_address_type": { + "description": "<em>indicates the type of network to get data for</em><br>optional field<br>possible values: <code>ip</code>, <code>subnet</code><br>default value: <code>ip</code>", + "type": [ + "string", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned networks</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get referring networks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / oneOfRemoved value: -[ - { - "example": [ - { - "backlinks_filters": [ - "dofollow", - "=", - true - ], - "exclude_internal_backlinks": true, - "filters": [ - "backlinks", - ">", - 100 - ], - "limit": 5, - "network_address_type": "subnet", - "order_by": [ - "rank,desc" - ], - "target": "backlinko.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"network_address\",\"like\",\"194.1.%\"],\"or\",[\"referring_ips\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned networks</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "network_address_type": { - "description": "<em>indicates the type of network to get data for</em><br>optional field<br>possible values: <code>ip</code>, <code>subnet</code><br>default value: <code>ip</code>", - "type": [ - "string", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned networks</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get referring networks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -]
- Changed
post_dataforseo_backlinks_summary_live3 fields changed- added
Input schema / $defsAdded value: +{ + "Provider0A3E90081762_AisaDataforseoFilterJsonValue": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + } +} - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", + "items": { + "anyOf": [ + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "additionalProperties": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": [ + "object", + "null" + ] + }, + { + "items": { + "$ref": "#/$defs/Provider0A3E90081762_AisaDataforseoFilterJsonValue" + }, + "type": "array" + } + ], + "description": "JSON representation of filter values and nested expressions. Field names, operators, condition counts and operand compatibility remain provider-validated as documented for each endpoint; this is not a complete filter-language validator." + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / oneOfRemoved value: -[ - { - "example": [ - { - "backlinks_filters": [ - "dofollow", - "=", - true - ], - "backlinks_status_type": "all", - "include_subdomains": true, - "internal_list_limit": 10, - "target": "explodingtopics.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -]
- Changed
post_dataforseo_backlinks_timeseries_new_lost_live1 field changed- changed
Input schema / properties / body / items / oneOfPrevious value: -[ - { - "example": [ - { - "date_from": "2021-12-01", - "date_to": "2022-02-01", - "group_range": "month", - "target": "dataforseo.com" - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", - "type": [ - "string", - "null" - ] - }, - "date_to": { - "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", - "type": [ - "string", - "null" - ] - }, - "group_range": { - "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", - "type": [ - "string", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", - "type": "string" - } - }, - "type": "object" - } -]New value: +[ + { + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "date_to": { + "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "group_range": { + "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", + "type": [ + "string", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", + "type": "string" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_timeseries_summary_live1 field changed- changed
Input schema / properties / body / items / oneOfPrevious value: -[ - { - "example": [ - { - "date_from": "2021-12-01", - "date_to": "2022-02-01", - "group_range": "month", - "target": "dataforseo.com" - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for summary data;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", - "type": [ - "string", - "null" - ] - }, - "date_to": { - "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", - "type": [ - "string", - "null" - ] - }, - "group_range": { - "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", - "type": [ - "string", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", - "type": "string" - } - }, - "type": "object" - } -]New value: +[ + { + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for summary data;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "date_to": { + "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "group_range": { + "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", + "type": [ + "string", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", + "type": "string" + } + }, + "type": "object" + } +]
20 tool updates
- Changed
post_dataforseo_backlinks_anchors_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "filters": [ - "anchor", - "like", - "%news%" - ], - "limit": 4, - "order_by": [ - "backlinks,desc" - ], - "target": "forbes.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get anchors for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "filters": [ + "anchor", + "like", + "%news%" + ], + "limit": 4, + "order_by": [ + "backlinks,desc" + ], + "target": "forbes.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get anchors for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_backlinks_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "filters": [ - "dofollow", - "=", - true - ], - "limit": 5, - "mode": "as_is", - "target": "forbes.com" - } - ], - "properties": { - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "custom_mode": { - "additionalProperties": { - "type": [ - "object", - "null" - ] - }, - "description": "<em>detailed results grouping type</em><br>optional field<br>use this object to get a specific number of backlinks per <code>field</code><br>if you use <code>custom_mode</code>, then <code>mode</code> will be ignored<br>example:<br><code>\"custom_mode\": {\"field\": \"domain\", \"value\": 100}</code>", - "type": [ - "object", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>regex</code>, <code>not_regex</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"80\"]</code><p><code>[[\"page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"dofollow\",\"=\",true]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"text_pre\",\"like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "mode": { - "description": "<em>results grouping type</em><br>optional field<br>possible grouping types:<br><code>as_is</code> - returns all backlinks<br><code>one_per_domain</code> - returns one backlink per domain<br><code>one_per_anchor</code> - returns one backlink per anchor<p>default value: <code>as_is</code>", - "type": [ - "string", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks;<br><strong>Note:</strong> the maximum value is <code>20,000</code>, use the <code>search_after_token</code> if you would like to offset more results", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "search_after_token": { - "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get backlinks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "filters": [ + "dofollow", + "=", + true + ], + "limit": 5, + "mode": "as_is", + "target": "forbes.com" + } + ], + "properties": { + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "custom_mode": { + "additionalProperties": { + "type": [ + "object", + "null" + ] + }, + "description": "<em>detailed results grouping type</em><br>optional field<br>use this object to get a specific number of backlinks per <code>field</code><br>if you use <code>custom_mode</code>, then <code>mode</code> will be ignored<br>example:<br><code>\"custom_mode\": {\"field\": \"domain\", \"value\": 100}</code>", + "type": [ + "object", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>regex</code>, <code>not_regex</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"80\"]</code><p><code>[[\"page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"dofollow\",\"=\",true]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"text_pre\",\"like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "mode": { + "description": "<em>results grouping type</em><br>optional field<br>possible grouping types:<br><code>as_is</code> - returns all backlinks<br><code>one_per_domain</code> - returns one backlink per domain<br><code>one_per_anchor</code> - returns one backlink per anchor<p>default value: <code>as_is</code>", + "type": [ + "string", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks;<br><strong>Note:</strong> the maximum value is <code>20,000</code>, use the <code>search_after_token</code> if you would like to offset more results", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "search_after_token": { + "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get backlinks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_backlinks_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get the number of backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get the number of backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_new_lost_backlinks_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "date_from": "2026-09-12 05:48:19", - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks;<br>the backlinks that appeared in our index after the specified date will be considered as new;<br>the backlinks that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get new & lost backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without `https://` and `www.` the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br> `\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "date_from": "2026-09-12 05:48:19", + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks;<br>the backlinks that appeared in our index after the specified date will be considered as new;<br>the backlinks that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get new & lost backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without `https://` and `www.` the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br> `\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_new_lost_ref_domains_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "datetime_from": "2026-48-12", - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost referring domains;<br>the referring domains that appeared in our index after the specified date will be considered as new;<br>the referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get new & lost referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "datetime_from": "2026-48-12", + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost referring domains;<br>the referring domains that appeared in our index after the specified date will be considered as new;<br>the referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get new & lost referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_pages_summary_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "targets": [ - "https://dataforseo.com/solutions", - "https://dataforseo.com/about-us" - ] - } - ], - "properties": { - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>you can specify up to 1000 pages, domains, or subdomains in each request.<br><strong>note that the URLs you set in a single request cannot belong to more than 100 different domains</strong>.", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "targets": [ + "https://dataforseo.com/solutions", + "https://dataforseo.com/about-us" + ] + } + ], + "properties": { + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>you can specify up to 1000 pages, domains, or subdomains in each request.<br><strong>note that the URLs you set in a single request cannot belong to more than 100 different domains</strong>.", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_ranks_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_referring_domains_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get the number of referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get the number of referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_bulk_spam_score_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_competitors_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "filters": [ - "rank", - ">", - 100 - ], - "limit": 5, - "order_by": [ - "rank,desc" - ], - "target": "dataforseo.com" - } - ], - "properties": { - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "exclude_large_domains": { - "description": "<em>indicates whether large domain will appear in results</em><br>optional field<br>if set to <code>true</code>, the results from the large domain (google.com, amazon.com, etc.) will be omitted;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"100\"]</code><p><code>[[\"target\",\"like\",\"%forbes%\"],<br>\"and\",<br>[[\"rank\",\">\",\"100\"],\"or\",[\"intersections\",\">\",\"5\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "main_domain": { - "description": "<em>indicates if only main domain of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>true</code>, only the main domain will be included in search;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"intersections,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get competitor domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "filters": [ + "rank", + ">", + 100 + ], + "limit": 5, + "order_by": [ + "rank,desc" + ], + "target": "dataforseo.com" + } + ], + "properties": { + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "exclude_large_domains": { + "description": "<em>indicates whether large domain will appear in results</em><br>optional field<br>if set to <code>true</code>, the results from the large domain (google.com, amazon.com, etc.) will be omitted;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"100\"]</code><p><code>[[\"target\",\"like\",\"%forbes%\"],<br>\"and\",<br>[[\"rank\",\">\",\"100\"],\"or\",[\"intersections\",\">\",\"5\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "main_domain": { + "description": "<em>indicates if only main domain of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>true</code>, only the main domain will be included in search;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"intersections,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get competitor domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_domain_intersection_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "exclude_internal_backlinks": true, - "exclude_targets": [ - "semrush.com" - ], - "include_subdomains": false, - "limit": 5, - "order_by": [ - "1.backlinks,desc" - ], - "targets": { - "1": "moz.com", - "2": "ahrefs.com" - } - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be omitted and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "exclude_targets": { - "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can specify up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring domains that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"2.referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"1.backlinks\",\">\",\"10\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"2.target\",\"like\",\"%dataforseo.com%\"],\"or\",[\"1.referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "intersection_mode": { - "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified domains<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", - "type": [ - "string", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned results</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the array of returned results</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "additionalProperties": { - "type": [ - "string", - "null" - ] - }, - "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", - "type": [ - "object", - "null" - ] - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "exclude_internal_backlinks": true, + "exclude_targets": [ + "semrush.com" + ], + "include_subdomains": false, + "limit": 5, + "order_by": [ + "1.backlinks,desc" + ], + "targets": { + "1": "moz.com", + "2": "ahrefs.com" + } + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be omitted and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "exclude_targets": { + "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can specify up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring domains that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"2.referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"1.backlinks\",\">\",\"10\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"2.target\",\"like\",\"%dataforseo.com%\"],\"or\",[\"1.referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "intersection_mode": { + "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified domains<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", + "type": [ + "string", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned results</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the array of returned results</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "additionalProperties": { + "type": [ + "string", + "null" + ] + }, + "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", + "type": [ + "object", + "null" + ] + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_domain_pages_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "filters": [ - [ - "page_summary.backlinks", - ">", - 5 - ], - "and", - [ - "page", - "like", - "%sites%" - ] - ], - "limit": 5, - "target": "forbes.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"meta.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"meta.external_links_count\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_visited\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"title\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned pages</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned pages</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"page_summary.backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"page_summary.backlinks,desc\",\"page_summary.rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain or subdomain</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>forbes.com</code>", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "filters": [ + [ + "page_summary.backlinks", + ">", + 5 + ], + "and", + [ + "page", + "like", + "%sites%" + ] + ], + "limit": 5, + "target": "forbes.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"meta.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"meta.external_links_count\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_visited\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"title\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned pages</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned pages</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"page_summary.backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"page_summary.backlinks,desc\",\"page_summary.rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain or subdomain</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>forbes.com</code>", + "type": "string" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_domain_pages_summary_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "limit": 4, - "order_by": [ - "backlinks,desc" - ], - "target": "forbes.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, backlinks from the subdomains of the <code>target</code> domain will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> domain will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "limit": 4, + "order_by": [ + "backlinks,desc" + ], + "target": "forbes.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, backlinks from the subdomains of the <code>target</code> domain will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> domain will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_history_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "date_from": "2020-01-01", - "date_to": "2021-01-01", - "target": "cnn.com" - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>minimum value <code>2019-01-01</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", - "type": [ - "string", - "null" - ] - }, - "date_to": { - "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", - "type": [ - "string", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code>", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "date_from": "2020-01-01", + "date_to": "2021-01-01", + "target": "cnn.com" + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>minimum value <code>2019-01-01</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "date_to": { + "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code>", + "type": "string" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_page_intersection_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "exclude_targets": [ - "skysports.com" - ], - "filters": [ - [ - "2.domain_from_rank", - ">", - 400 - ], - "and", - [ - "1.dofollow", - "=", - true - ] - ], - "limit": 5, - "order_by": [ - "1.rank,desc" - ], - "targets": { - "1": "football.com", - "2": "fifa.com" - } - } - ], - "properties": { - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the result<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "exclude_targets": { - "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can set up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring pages that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.rank\",\">\",\"80\"]</code><p><code>[[\"2.page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"1.original\",\"=\",\"true\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"1.acnhor\",\"like\",\"%seo%\"],\"or\",[\"1.text_pre\",\"not_like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>targets</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>attributes</code><br><code>domain_from_platform_type</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "intersection_mode": { - "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified URLs<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", - "type": [ - "string", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "additionalProperties": { - "type": [ - "string", - "null" - ] - }, - "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", - "type": [ - "object", - "null" - ] - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "exclude_targets": [ + "skysports.com" + ], + "filters": [ + [ + "2.domain_from_rank", + ">", + 400 + ], + "and", + [ + "1.dofollow", + "=", + true + ] + ], + "limit": 5, + "order_by": [ + "1.rank,desc" + ], + "targets": { + "1": "football.com", + "2": "fifa.com" + } + } + ], + "properties": { + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the result<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "exclude_targets": { + "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can set up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring pages that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.rank\",\">\",\"80\"]</code><p><code>[[\"2.page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"1.original\",\"=\",\"true\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"1.acnhor\",\"like\",\"%seo%\"],\"or\",[\"1.text_pre\",\"not_like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>targets</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>attributes</code><br><code>domain_from_platform_type</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "intersection_mode": { + "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified URLs<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", + "type": [ + "string", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "additionalProperties": { + "type": [ + "string", + "null" + ] + }, + "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", + "type": [ + "object", + "null" + ] + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_referring_domains_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "backlinks_filters": [ - "dofollow", - "=", - true - ], - "exclude_internal_backlinks": true, - "filters": [ - "backlinks", - ">", - 100 - ], - "limit": 5, - "order_by": [ - "rank,desc" - ], - "target": "backlinko.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"domain\",\"like\",\"%dataforseo.com%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get referring domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "exclude_internal_backlinks": true, + "filters": [ + "backlinks", + ">", + 100 + ], + "limit": 5, + "order_by": [ + "rank,desc" + ], + "target": "backlinko.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"domain\",\"like\",\"%dataforseo.com%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get referring domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_referring_networks_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "backlinks_filters": [ - "dofollow", - "=", - true - ], - "exclude_internal_backlinks": true, - "filters": [ - "backlinks", - ">", - 100 - ], - "limit": 5, - "network_address_type": "subnet", - "order_by": [ - "rank,desc" - ], - "target": "backlinko.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"network_address\",\"like\",\"194.1.%\"],\"or\",[\"referring_ips\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned networks</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "network_address_type": { - "description": "<em>indicates the type of network to get data for</em><br>optional field<br>possible values: <code>ip</code>, <code>subnet</code><br>default value: <code>ip</code>", - "type": [ - "string", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned networks</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get referring networks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "exclude_internal_backlinks": true, + "filters": [ + "backlinks", + ">", + 100 + ], + "limit": 5, + "network_address_type": "subnet", + "order_by": [ + "rank,desc" + ], + "target": "backlinko.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"network_address\",\"like\",\"194.1.%\"],\"or\",[\"referring_ips\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned networks</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "network_address_type": { + "description": "<em>indicates the type of network to get data for</em><br>optional field<br>possible values: <code>ip</code>, <code>subnet</code><br>default value: <code>ip</code>", + "type": [ + "string", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned networks</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get referring networks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_summary_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "backlinks_filters": [ - "dofollow", - "=", - true - ], - "backlinks_status_type": "all", - "include_subdomains": true, - "internal_list_limit": 10, - "target": "explodingtopics.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "backlinks_status_type": "all", + "include_subdomains": true, + "internal_list_limit": 10, + "target": "explodingtopics.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_timeseries_new_lost_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "date_from": "2021-12-01", - "date_to": "2022-02-01", - "group_range": "month", - "target": "dataforseo.com" - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", - "type": [ - "string", - "null" - ] - }, - "date_to": { - "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", - "type": [ - "string", - "null" - ] - }, - "group_range": { - "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", - "type": [ - "string", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "date_from": "2021-12-01", + "date_to": "2022-02-01", + "group_range": "month", + "target": "dataforseo.com" + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "date_to": { + "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "group_range": { + "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", + "type": [ + "string", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", + "type": "string" + } + }, + "type": "object" + } +]
- Changed
post_dataforseo_backlinks_timeseries_summary_live2 fields changed- removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "date_from": "2021-12-01", - "date_to": "2022-02-01", - "group_range": "month", - "target": "dataforseo.com" - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for summary data;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", - "type": [ - "string", - "null" - ] - }, - "date_to": { - "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", - "type": [ - "string", - "null" - ] - }, - "group_range": { - "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", - "type": [ - "string", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / oneOfAdded value: +[ + { + "example": [ + { + "date_from": "2021-12-01", + "date_to": "2022-02-01", + "group_range": "month", + "target": "dataforseo.com" + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for summary data;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "date_to": { + "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "group_range": { + "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", + "type": [ + "string", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", + "type": "string" + } + }, + "type": "object" + } +]
33 tool updates
- Added
batch_get_schema - Added
batch_quote - Changed
batch_use18 fields changed- added
Input schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / properties / calls / descriptionRemoved value: -"Up to 20 items of {call_id, operation_id, arguments}; steps at the same execution_level of a plan go in one batch" - added
Input schema / properties / calls / items / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema" - changed
Input schema / properties / calls / items / additionalPropertiesPrevious value: -trueNew value: +false - added
Input schema / properties / calls / items / propertiesAdded value: +{ + "arguments": { + "additionalProperties": true, + "description": "Strictly schema-compliant arguments using the exact field names and types from this tool's arguments_schema.", + "type": "object" + }, + "call_id": { + "description": "Caller-chosen identifier unique within this batch.", + "maxLength": 128, + "minLength": 1, + "type": "string" + }, + "tool": { + "description": "Exact tool name returned by search or batch_get_schema. Never invent a name.", + "minLength": 1, + "type": "string" + } +} - added
Input schema / properties / calls / items / requiredAdded value: +[ + "call_id", + "tool", + "arguments" +] - added
Input schema / properties / calls / maxItemsAdded value: +20 - added
Input schema / properties / calls / minItemsAdded value: +1 - removed
Input schema / properties / max_price_usdRemoved value: -{ - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ], - "default": null, - "description": "Per-call price cap applied to every item" -} - removed
Input schema / properties / search_id / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - removed
Input schema / properties / search_id / defaultRemoved value: -null - changed
Input schema / properties / search_id / descriptionPrevious value: -"search_id from the search that found these operations"New value: +"Optional search correlation identifier returned by search." - added
Input schema / properties / search_id / typeAdded value: +"string" - added
Input schema / properties / session_idAdded value: +{ + "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", + "maxLength": 128, + "pattern": "^[A-Za-z0-9_-]*$", + "type": "string" +} - added
Output schema / $defsAdded value: +{ + "jsonValue": { + "anyOf": [ + { + "additionalProperties": { + "$ref": "#/$defs/jsonValue" + }, + "type": "object" + }, + { + "items": { + "$ref": "#/$defs/jsonValue" + }, + "type": "array" + }, + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "type": "null" + } + ], + "description": "JSON value returned by the upstream tool." + } +} - added
Output schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / propertiesAdded value: +{ + "batch_id": { + "type": "string" + }, + "error_count": { + "minimum": 0, + "type": "integer" + }, + "next_steps_guidance": { + "description": "Deterministic next-step instructions derived from this result. Not an authorization grant.", + "items": { + "type": "string" + }, + "type": "array" + }, + "results": { + "items": { + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "call_id": { + "type": "string" + }, + "customer_cost_micros_usd": { + "description": "Actual customer charge settled by AIsaServices, in micro-USD. Omitted when the upstream response does not report it.", + "minimum": 0, + "type": "integer" + }, + "data": { + "$ref": "#/$defs/jsonValue" + }, + "error": { + "anyOf": [ + { + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "message": { + "type": "string" + }, + "retryable": { + "type": "boolean" + }, + "status": { + "type": "integer" + }, + "type": { + "enum": [ + "validation", + "authentication", + "payment", + "permission", + "rate_limit", + "upstream", + "timeout", + "internal" + ], + "type": "string" + } + }, + "required": [ + "type", + "status", + "retryable" + ], + "type": "object" + }, + { + "type": "null" + } + ] + }, + "request_id": { + "type": "string" + }, + "successful": { + "type": "boolean" + }, + "tool": { + "type": "string" + }, + "upstream_status": { + "description": "HTTP status returned by AIsaServices when a request was dispatched.", + "type": "integer" + } + }, + "required": [ + "call_id", + "tool", + "successful", + "request_id" + ], + "type": "object" + }, + "type": "array" + }, + "session_id": { + "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", + "maxLength": 128, + "minLength": 1, + "pattern": "^[A-Za-z0-9_-]*$", + "type": "string" + }, + "success_count": { + "minimum": 0, + "type": "integer" + }, + "total_count": { + "minimum": 1, + "type": "integer" + } +} - added
Output schema / requiredAdded value: +[ + "session_id", + "batch_id", + "total_count", + "success_count", + "error_count", + "results", + "next_steps_guidance" +]
- Changed
get_dataforseo_backlinks_index1 field changed- added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
get_details13 fields changed- added
Input schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / properties / argumentsRemoved value: -{ - "anyOf": [ - { - "additionalProperties": true, - "type": "object" - }, - { - "type": "null" - } - ], - "default": null, - "description": "The arguments the operation would be called with, for a price that reflects them. Keyed by operation_id for a batch, or passed flat for a single operation_id. Routes whose required parameters are validated before pricing have no price without them." -} - added
Input schema / properties / include_arguments_schemaAdded value: +{ + "default": true, + "description": "Return the complete arguments_schema. Defaults to true.", + "type": "boolean" +} - changed
Input schema / properties / include_documentation / descriptionPrevious value: -"Include the complete native public OpenAPI document, reference closure and scoped completeness. Existing execution schemas remain unchanged."New value: +"Return the complete immutable public OpenAPI operation, referenced declarations, provenance and scoped completeness. Documentation does not change execution support." - added
Input schema / properties / include_response_schemaAdded value: +{ + "default": false, + "description": "Return the complete response_schema. Defaults to false.", + "type": "boolean" +} - removed
Input schema / properties / operation_idRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "default": null, - "description": "One operation_id from search" -} - removed
Input schema / properties / operation_idsRemoved value: -{ - "anyOf": [ - { - "items": { - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ], - "default": null, - "description": "Up to 20 operation_ids, for a batch" -} - added
Input schema / properties / session_idAdded value: +{ + "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", + "maxLength": 128, + "pattern": "^[A-Za-z0-9_-]*$", + "type": "string" +} - added
Input schema / properties / toolsAdded value: +{ + "description": "Exact tool names returned by search whose complete contracts are needed. Never invent tool names.", + "items": { + "minLength": 1, + "pattern": "^\\S(?:.*\\S)?$", + "type": "string" + }, + "maxItems": 20, + "minItems": 1, + "type": "array", + "uniqueItems": true +} - removed
Input schema / properties / with_quoteRemoved value: -{ - "default": true, - "description": "Whether each operation is priced for this account before the answer. One round trip per operation; spends nothing.", - "type": "boolean" -} - added
Input schema / requiredAdded value: +[ + "tools" +] - added
Output schema / propertiesAdded value: +{ + "error_count": { + "type": "integer" + }, + "next_steps_guidance": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "session_id": { + "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", + "maxLength": 128, + "minLength": 1, + "pattern": "^[A-Za-z0-9_-]{1,128}$", + "type": "string" + }, + "success_count": { + "type": "integer" + }, + "tools": { + "additionalProperties": { + "additionalProperties": false, + "properties": { + "arguments_schema": { + "additionalProperties": true, + "anyOf": [ + { + "type": "null" + }, + { + "type": "object" + } + ] + }, + "canonical_operation_id": { + "type": "string" + }, + "documentation": { + "additionalProperties": true, + "type": "object" + }, + "error": { + "additionalProperties": false, + "anyOf": [ + { + "type": "null" + }, + { + "type": "object" + } + ], + "properties": { + "code": { + "type": "string" + }, + "message": { + "type": "string" + } + }, + "required": [ + "code", + "message" + ] + }, + "execution_supported": { + "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.", + "type": "boolean" + }, + "execution_unsupported_reason": { + "description": "Why execution and quoting remain unavailable through this router.", + "type": "string" + }, + "idempotent": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "boolean" + } + ] + }, + "known_pitfalls": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "read_only": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "boolean" + } + ] + }, + "response_schema": { + "additionalProperties": true, + "anyOf": [ + { + "type": "null" + }, + { + "type": "object" + } + ] + }, + "side_effects": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "successful": { + "type": "boolean" + } + }, + "required": [ + "successful" + ], + "type": "object" + }, + "type": "object" + }, + "total_count": { + "type": "integer" + } +} - added
Output schema / requiredAdded value: +[ + "error_count", + "next_steps_guidance", + "session_id", + "success_count", + "tools", + "total_count" +]
- Changed
get_semrush_backlink_anchors4 fields changed- removed
Input schema / properties / target / descriptionRemoved value: -"Target domain or URL." - removed
Input schema / properties / target / exampleRemoved value: -"ahrefs.com" - removed
Input schema / properties / target_type / descriptionRemoved value: -"One of `root_domain`, `domain`, or `url`." - removed
Input schema / properties / target_type / exampleRemoved value: -"root_domain"
- Changed
get_semrush_backlink_competitors4 fields changed- removed
Input schema / properties / target / descriptionRemoved value: -"Target domain or URL." - removed
Input schema / properties / target / exampleRemoved value: -"ahrefs.com" - removed
Input schema / properties / target_type / descriptionRemoved value: -"One of `root_domain`, `domain`, or `url`." - removed
Input schema / properties / target_type / exampleRemoved value: -"root_domain"
- Changed
get_semrush_backlinks4 fields changed- removed
Input schema / properties / target / descriptionRemoved value: -"Target domain or URL." - removed
Input schema / properties / target / exampleRemoved value: -"ahrefs.com" - removed
Input schema / properties / target_type / descriptionRemoved value: -"One of `root_domain`, `domain`, or `url`." - removed
Input schema / properties / target_type / exampleRemoved value: -"root_domain"
- Changed
get_semrush_backlinks_overview1 field changed- removed
Input schema / properties / target / descriptionRemoved value: -"Target root domain, e.g. `ahrefs.com`."
- Changed
get_semrush_indexed_pages4 fields changed- removed
Input schema / properties / target / descriptionRemoved value: -"Target domain or URL." - removed
Input schema / properties / target / exampleRemoved value: -"ahrefs.com" - removed
Input schema / properties / target_type / descriptionRemoved value: -"One of `root_domain`, `domain`, or `url`." - removed
Input schema / properties / target_type / exampleRemoved value: -"root_domain"
- Changed
get_semrush_referring_domains4 fields changed- removed
Input schema / properties / target / descriptionRemoved value: -"Target domain or URL." - removed
Input schema / properties / target / exampleRemoved value: -"ahrefs.com" - removed
Input schema / properties / target_type / descriptionRemoved value: -"One of `root_domain`, `domain`, or `url`." - removed
Input schema / properties / target_type / exampleRemoved value: -"root_domain"
- Changed
post_dataforseo_backlinks_anchors_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "filters": [ + "anchor", + "like", + "%news%" + ], + "limit": 4, + "order_by": [ + "backlinks,desc" + ], + "target": "forbes.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "filters": [ + "anchor", + "like", + "%news%" + ], + "limit": 4, + "order_by": [ + "backlinks,desc" + ], + "target": "forbes.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get anchors for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [[\"dofollow\", \"=\", true]]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, the backlinks from subdomains of the target will be ommited and you won’t receive the same domain in the response; default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"referring_links_types.anchors\",\">\",\"1\"] [[\"broken_pages\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "limit": { - "description": "the maximum number of returned anchors optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "offset": { - "description": "offset in the results array of returned anchors optional field default value: 0 if you specify the 10 value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get anchors for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_backlinks_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "filters": [ + "dofollow", + "=", + true + ], + "limit": 5, + "mode": "as_is", + "target": "forbes.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "filters": [ + "dofollow", + "=", + true + ], + "limit": 5, + "mode": "as_is", + "target": "forbes.com" + } + ], + "properties": { + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "custom_mode": { + "additionalProperties": { + "type": [ + "object", + "null" + ] + }, + "description": "<em>detailed results grouping type</em><br>optional field<br>use this object to get a specific number of backlinks per <code>field</code><br>if you use <code>custom_mode</code>, then <code>mode</code> will be ignored<br>example:<br><code>\"custom_mode\": {\"field\": \"domain\", \"value\": 100}</code>", + "type": [ + "object", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>regex</code>, <code>not_regex</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"80\"]</code><p><code>[[\"page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"dofollow\",\"=\",true]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"text_pre\",\"like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "mode": { + "description": "<em>results grouping type</em><br>optional field<br>possible grouping types:<br><code>as_is</code> - returns all backlinks<br><code>one_per_domain</code> - returns one backlink per domain<br><code>one_per_anchor</code> - returns one backlink per anchor<p>default value: <code>as_is</code>", + "type": [ + "string", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks;<br><strong>Note:</strong> the maximum value is <code>20,000</code>, use the <code>search_after_token</code> if you would like to offset more results", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "search_after_token": { + "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get backlinks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "custom_mode": { - "description": "detailed results grouping type optional field use this object to get a specific number of backlinks per field if you use custom_mode, then mode will be ignored example: \"custom_mode\": {\"field\": \"domain\", \"value\": 100}", - "properties": { - "field": { - "type": "string" - }, - "value": { - "type": "integer" - } - }, - "type": "object" - }, - "exclude_internal_backlinks": { - "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: =, , in, not_in, like, not_like, ilike, not_ilike, regex, not_regex, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"rank\",\">\",\"80\"] [[\"page_from_rank\",\">\",\"55\"], \"and\", [\"dofollow\",\"=\",true]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"text_pre\",\"like\",\"%seo%\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "limit": { - "description": "the maximum number of returned backlinks optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "mode": { - "description": "results grouping type optional field possible grouping types: as_is – returns all backlinks one_per_domain – returns one backlink per domain one_per_anchor – returns one backlink per anchor default value: as_is", - "type": "string" - }, - "offset": { - "description": "offset in the results array of the returned backlinks optional field default value: 0 if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks; Note: the maximum value is 20,000, use the search_after_token if you would like to offset more results", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"rank,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"domain_from_rank,desc\",\"page_from_rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "search_after_token": { - "description": "token for subsequent requests optional field provided in the identical filed of the response to each request; use this parameter to avoid timeouts while trying to obtain over 20,000 results in a single request; by specifying the unique search_after_token value from the response array, you will get the subsequent results of the initial task; search_after_token values are unique for each subsequent task ; Note: if the search_after_token is specified in the request, all other parameters should be identical to the previous request", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get backlinks for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_backlinks_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get the number of backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get the number of backlinks for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_new_lost_backlinks_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "date_from": "2026-09-12 05:48:19", + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "date_from": "2026-09-12 05:48:19", + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks;<br>the backlinks that appeared in our index after the specified date will be considered as new;<br>the backlinks that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get new & lost backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without `https://` and `www.` the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br> `\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "date_from": { - "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost backlinks; the backlinks that appeared in our index after the specified date will be considered as new; the backlinks that weren’t found after the specified date, but were present before, will be considered as lost; default value: today’s date -(minus) one month; e.g. if today is 2021-10-13, default date_from will be 2021-09-13. minimum value equals today’s date -(minus) one year; e.g. if today is 2021-10-13, minimum date_from will be 2020-10-13. date format: \"yyyy-mm-dd\" example: \"2021-01-01\"", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get new & lost backlinks for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_new_lost_ref_domains_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "datetime_from": "2026-48-12", + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "datetime_from": "2026-48-12", + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost referring domains;<br>the referring domains that appeared in our index after the specified date will be considered as new;<br>the referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get new & lost referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "date_from": { - "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost referring domains; the referring domains that appeared in our index after the specified date will be considered as new; the referring domains that weren’t found after the specified date, but were present before, will be considered as lost; default value: today’s date -(minus) one month; e.g. if today is 2021-10-13, default date_from will be 2021-09-13. minimum value equals today’s date -(minus) one year; e.g. if today is 2021-10-13, minimum date_from will be 2020-10-13. date format: \"yyyy-mm-dd\" example: \"2021-01-01\"", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get new & lost referring domains for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_pages_summary_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "targets": [ + "https://dataforseo.com/solutions", + "https://dataforseo.com/about-us" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "targets": [ + "https://dataforseo.com/solutions", + "https://dataforseo.com/about-us" + ] + } + ], + "properties": { + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>you can specify up to 1000 pages, domains, or subdomains in each request.<br><strong>note that the URLs you set in a single request cannot belong to more than 100 different domains</strong>.", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get summary data for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://) you can specify up to 1000 pages, domains, or subdomains in each request. note that the URLs you set in a single request cannot belong to more than 100 different domains.", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_ranks_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get rank for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_referring_domains_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get the number of referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get the number of referring domains for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_spam_score_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get rank for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_competitors_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "filters": [ + "rank", + ">", + 100 + ], + "limit": 5, + "order_by": [ + "rank,desc" + ], + "target": "dataforseo.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "filters": [ + "rank", + ">", + 100 + ], + "limit": 5, + "order_by": [ + "rank,desc" + ], + "target": "dataforseo.com" + } + ], + "properties": { + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "exclude_large_domains": { + "description": "<em>indicates whether large domain will appear in results</em><br>optional field<br>if set to <code>true</code>, the results from the large domain (google.com, amazon.com, etc.) will be omitted;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"100\"]</code><p><code>[[\"target\",\"like\",\"%forbes%\"],<br>\"and\",<br>[[\"rank\",\">\",\"100\"],\"or\",[\"intersections\",\">\",\"5\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "main_domain": { + "description": "<em>indicates if only main domain of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>true</code>, only the main domain will be included in search;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"intersections,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get competitor domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "exclude_internal_backlinks": { - "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results default value: true", - "type": "boolean" - }, - "exclude_large_domains": { - "description": "indicates whether large domain will appear in results optional field if set to true, the results from the large domain (google.com, amazon.com, etc.) will be omitted; default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"rank\",\">\",\"100\"] [[\"target\",\"like\",\"%forbes%\"], \"and\", [[\"rank\",\">\",\"100\"],\"or\",[\"intersections\",\">\",\"5\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "limit": { - "description": "the maximum number of returned domains optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "main_domain": { - "description": "indicates if only main domain of the target will be included in the search optional field if set to true, only the main domain will be included in search; default value: true", - "type": "boolean" - }, - "offset": { - "description": "offset in the results array of returned domains optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"rank,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"intersections,desc\",\"rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get competitor domains for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_domain_intersection_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "exclude_internal_backlinks": true, + "exclude_targets": [ + "semrush.com" + ], + "include_subdomains": false, + "limit": 5, + "order_by": [ + "1.backlinks,desc" + ], + "targets": { + "1": "moz.com", + "2": "ahrefs.com" + } + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "exclude_internal_backlinks": true, + "exclude_targets": [ + "semrush.com" + ], + "include_subdomains": false, + "limit": 5, + "order_by": [ + "1.backlinks,desc" + ], + "targets": { + "1": "moz.com", + "2": "ahrefs.com" + } + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be omitted and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "exclude_targets": { + "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can specify up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring domains that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"2.referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"1.backlinks\",\">\",\"10\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"2.target\",\"like\",\"%dataforseo.com%\"],\"or\",[\"1.referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "intersection_mode": { + "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified domains<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", + "type": [ + "string", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned results</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the array of returned results</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "additionalProperties": { + "type": [ + "string", + "null" + ] + }, + "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", + "type": [ + "object", + "null" + ] + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [[\"dofollow\", \"=\", true]]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your targets; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, the backlinks from subdomains of the target will be omitted and you won’t receive the same domain in the response; default value: true", - "type": "boolean" - }, - "exclude_targets": { - "description": "domains, subdomains or webpages you want to exclude optional field you can specify up to 10 domains, subdomains or webpages if you use this array, results will contain the referring domains that link to targets but don’t link to exclude_targets example: \"exclude_targets\": [ \"bbc.com\", \"https://www.apple.com/iphone/*\", \"https://dataforseo.com/apis/*\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"1.internal_links_count\",\">\",\"1\"] [[\"2.referring_pages\",\">\",\"2\"], \"and\", [\"1.backlinks\",\">\",\"10\"]] [[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"2.target\",\"like\",\"%dataforseo.com%\"],\"or\",[\"1.referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the targets will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "intersection_mode": { - "description": "indicates whether to intersect backlinks optional field use this field to intersect or merge results for the specified domains possible values: all, partial all – results are based on all backlinks; partial – results are based on the intersecting backlinks only; default value: all", - "type": "string" - }, - "limit": { - "description": "the maximum number of returned results optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "offset": { - "description": "offset in the array of returned results optional field default value: 0 if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "additionalProperties": { - "type": "string" - }, - "description": "domains, subdomains or webpages to get links for required field you can set up to 20 domains, subdomains or webpages a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://) example: \"targets\": { \"1\": \"http://planet.postgresql.org/\", \"2\": \"http://gborg.postgresql.org/\" }", - "type": "object" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_domain_pages_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "filters": [ + [ + "page_summary.backlinks", + ">", + 5 + ], + "and", + [ + "page", + "like", + "%sites%" + ] + ], + "limit": 5, + "target": "forbes.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "filters": [ + [ + "page_summary.backlinks", + ">", + 5 + ], + "and", + [ + "page", + "like", + "%sites%" + ] + ], + "limit": 5, + "target": "forbes.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"meta.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"meta.external_links_count\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_visited\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"title\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned pages</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned pages</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"page_summary.backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"page_summary.backlinks,desc\",\"page_summary.rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain or subdomain</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>forbes.com</code>", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [\"dofollow\", \"=\", true]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"meta.internal_links_count\",\">\",\"1\"] [[\"meta.external_links_count\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_visited\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"title\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "limit": { - "description": "the maximum number of returned pages optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "offset": { - "description": "offset in the results array of returned pages optional field default value: 0 if you specify the 10 value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"page_summary.backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"page_summary.backlinks,desc\",\"page_summary.rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain or subdomain required field a domain or a subdomain should be specified without https:// and www. example: forbes.com", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_domain_pages_summary_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "limit": 4, + "order_by": [ + "backlinks,desc" + ], + "target": "forbes.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "limit": 4, + "order_by": [ + "backlinks,desc" + ], + "target": "forbes.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, backlinks from the subdomains of the <code>target</code> domain will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> domain will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [[\"dofollow\", \"=\", true]]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, backlinks from the subdomains of the target domain will be ommited and you won’t receive the same domain in the response; default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"referring_links_types.anchors\",\">\",\"1\"] [[\"broken_pages\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target domain will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "limit": { - "description": "the maximum number of returned anchors optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "offset": { - "description": "offset in the results array of returned anchors optional field default value: 0 if you specify the 10 value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get summary data for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_history_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "date_from": "2020-01-01", + "date_to": "2021-01-01", + "target": "cnn.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "date_from": "2020-01-01", + "date_to": "2021-01-01", + "target": "cnn.com" + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>minimum value <code>2019-01-01</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "date_to": { + "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code>", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "date_from": { - "description": "starting date of the time range optional field minimum value 2019-01-01 if you don’t specify this field, the minimum value will be used by default date format: \"yyyy-mm-dd\" example: \"2019-01-15\"", - "type": "string" - }, - "date_to": { - "description": "ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default date format: \"yyyy-mm-dd\" example: \"2019-01-15\"", - "type": "string" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain required field a domain should be specified without https:// and www.", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_page_intersection_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "exclude_targets": [ + "skysports.com" + ], + "filters": [ + [ + "2.domain_from_rank", + ">", + 400 + ], + "and", + [ + "1.dofollow", + "=", + true + ] + ], + "limit": 5, + "order_by": [ + "1.rank,desc" + ], + "targets": { + "1": "football.com", + "2": "fifa.com" + } + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "exclude_targets": [ + "skysports.com" + ], + "filters": [ + [ + "2.domain_from_rank", + ">", + 400 + ], + "and", + [ + "1.dofollow", + "=", + true + ] + ], + "limit": 5, + "order_by": [ + "1.rank,desc" + ], + "targets": { + "1": "football.com", + "2": "fifa.com" + } + } + ], + "properties": { + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the result<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "exclude_targets": { + "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can set up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring pages that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.rank\",\">\",\"80\"]</code><p><code>[[\"2.page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"1.original\",\"=\",\"true\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"1.acnhor\",\"like\",\"%seo%\"],\"or\",[\"1.text_pre\",\"not_like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>targets</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>attributes</code><br><code>domain_from_platform_type</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "intersection_mode": { + "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified URLs<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", + "type": [ + "string", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "additionalProperties": { + "type": [ + "string", + "null" + ] + }, + "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", + "type": [ + "object", + "null" + ] + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your targets; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the result default value: true", - "type": "boolean" - }, - "exclude_targets": { - "description": "domains, subdomains or webpages you want to exclude optional field you can set up to 10 domains, subdomains or webpages if you use this array, results will contain the referring pages that link to targets but don’t link to exclude_targets example: \"exclude_targets\": [ \"bbc.com\", \"https://www.apple.com/iphone/*\", \"https://dataforseo.com/apis/*\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"1.rank\",\">\",\"80\"] [[\"2.page_from_rank\",\">\",\"55\"], \"and\", [\"1.original\",\"=\",\"true\"]] [[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"1.acnhor\",\"like\",\"%seo%\"],\"or\",[\"1.text_pre\",\"not_like\",\"%seo%\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the targets will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the targets will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: attributes domain_from_platform_type default value: 10 maximum value: 1000", - "type": "integer" - }, - "intersection_mode": { - "description": "indicates whether to intersect backlinks optional field use this field to intersect or merge results for the specified URLs possible values: all, partial all – results are based on all backlinks; partial – results are based on the intersecting backlinks only; default value: all", - "type": "string" - }, - "limit": { - "description": "the maximum number of returned backlinks optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "offset": { - "description": "offset in the results array of the returned backlinks optional field default value: 0 if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"rank,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"domain_from_rank,desc\",\"page_from_rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "additionalProperties": { - "type": "string" - }, - "description": "domains, subdomains or webpages to get links for required field you can set up to 20 domains, subdomains or webpages a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://) example: \"targets\": { \"1\": \"http://planet.postgresql.org/\", \"2\": \"http://gborg.postgresql.org/\" }", - "type": "object" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_referring_domains_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "exclude_internal_backlinks": true, + "filters": [ + "backlinks", + ">", + 100 + ], + "limit": 5, + "order_by": [ + "rank,desc" + ], + "target": "backlinko.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "exclude_internal_backlinks": true, + "filters": [ + "backlinks", + ">", + 100 + ], + "limit": 5, + "order_by": [ + "rank,desc" + ], + "target": "backlinko.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"domain\",\"like\",\"%dataforseo.com%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get referring domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [\"dofollow\", \"=\", true]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, the backlinks from subdomains of the target will be ommited and you won’t receive the same domain in the response; default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"referring_pages\",\">\",\"1\"] [[\"referring_pages\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"domain\",\"like\",\"%dataforseo.com%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "limit": { - "description": "the maximum number of returned domains optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "offset": { - "description": "offset in the results array of returned domains optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get referring domains for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_referring_networks_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "exclude_internal_backlinks": true, + "filters": [ + "backlinks", + ">", + 100 + ], + "limit": 5, + "network_address_type": "subnet", + "order_by": [ + "rank,desc" + ], + "target": "backlinko.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "exclude_internal_backlinks": true, + "filters": [ + "backlinks", + ">", + 100 + ], + "limit": 5, + "network_address_type": "subnet", + "order_by": [ + "rank,desc" + ], + "target": "backlinko.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"network_address\",\"like\",\"194.1.%\"],\"or\",[\"referring_ips\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned networks</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "network_address_type": { + "description": "<em>indicates the type of network to get data for</em><br>optional field<br>possible values: <code>ip</code>, <code>subnet</code><br>default value: <code>ip</code>", + "type": [ + "string", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned networks</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get referring networks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [[\"dofollow\", \"=\", true]]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, the backlinks from subdomains of the target will be ommited and you won’t receive the same domain in the response; default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"referring_pages\",\">\",\"1\"] [[\"referring_pages\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"network_address\",\"like\",\"194.1.%\"],\"or\",[\"referring_ips\",\">\",\"10\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "limit": { - "description": "the maximum number of returned networks optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "network_address_type": { - "description": "indicates the type of network to get data for optional field possible values: ip, subnet default value: ip", - "type": "string" - }, - "offset": { - "description": "offset in the results array of returned networks optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get referring networks for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_summary_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "backlinks_status_type": "all", + "include_subdomains": true, + "internal_list_limit": 10, + "target": "explodingtopics.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "backlinks_status_type": "all", + "include_subdomains": true, + "internal_list_limit": 10, + "target": "explodingtopics.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [\"dofollow\", \"=\", true]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results default value: true", - "type": "boolean" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get data for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_timeseries_new_lost_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "date_from": "2021-12-01", + "date_to": "2022-02-01", + "group_range": "month", + "target": "dataforseo.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "date_from": "2021-12-01", + "date_to": "2022-02-01", + "group_range": "month", + "target": "dataforseo.com" + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "date_to": { + "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "group_range": { + "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", + "type": [ + "string", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "date_from": { - "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains; the backlinks and referring domains that appeared in our index after the specified date will be considered as new; the backlinks and referring domains that weren’t found after the specified date, but were present before, will be considered as lost; minimum value: 2019-01-30 maximum value shouldn’t exceed the date specified in the date_to date format: \"yyyy-mm-dd\" example: \"2021-01-01\"", - "type": "string" - }, - "date_to": { - "description": "ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default minimum value shouldn’t preceed the date specified in the date_from maximum value: today’s date date format: \"yyyy-mm-dd\" example: \"2021-01-15\"", - "type": "string" - }, - "group_range": { - "description": "time range which will be used to group the results optional field default value: month possible values: day, week, month, year note: for day, we will return items corresponding to all dates between and including date_from and date_to; for week/month/year, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year for example, if you specify: \"group_range\": \"month\", \"date_from\": \"2022-03-23\", \"date_to\": \"2022-05-13\" we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: 2022-03-31, 2022-04-30, 2022-05-31 if there is no data for a certain day/week/month/year, we will return 0", - "type": "string" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain to get data for required field a domain should be specified without https:// and www. example: \"forbes.com\"", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_timeseries_summary_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "date_from": "2021-12-01", + "date_to": "2022-02-01", + "group_range": "month", + "target": "dataforseo.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "date_from": "2021-12-01", + "date_to": "2022-02-01", + "group_range": "month", + "target": "dataforseo.com" + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for summary data;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "date_to": { + "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "group_range": { + "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", + "type": [ + "string", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "date_from": { - "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for summary data; minimum value: 2019-01-30 maximum value shouldn’t exceed the date specified in the date_to date format: \"yyyy-mm-dd\" example: \"2021-01-01\"", - "type": "string" - }, - "date_to": { - "description": "ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default minimum value shouldn’t preceed the date specified in the date_from maximum value: today’s date date format: \"yyyy-mm-dd\" example: \"2021-01-15\"", - "type": "string" - }, - "group_range": { - "description": "time range which will be used to group the results optional field default value: month possible values: day, week, month, year note: for day, we will return items corresponding to all dates between and including date_from and date_to; for week/month/year, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year for example, if you specify: \"group_range\": \"month\", \"date_from\": \"2022-03-23\", \"date_to\": \"2022-05-13\" we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: 2022-03-31, 2022-04-30, 2022-05-31 if there is no data for a certain day/week/month/year, we will return 0", - "type": "string" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain to get data for required field a domain should be specified without https:// and www. example: \"forbes.com\"", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
search17 fields changed- added
Input schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / properties / category / anyOfRemoved value: -[ - { - "enum": [ - "seo", - "finance", - "social", - "search", - "sales", - "mail" - ], - "type": "string" - }, - { - "type": "null" - } -] - removed
Input schema / properties / category / defaultRemoved value: -null - changed
Input schema / properties / category / descriptionPrevious value: -"Restrict to one category (seo, finance, social, search, sales, mail). Omit to search everything."New value: +"Restrict retrieval to one category. Omit to search everything. (AIsa-only: tool-router has no equivalent.)" - added
Input schema / properties / category / enumAdded value: +[ + "seo", + "finance", + "social", + "search", + "sales", + "mail" +] - added
Input schema / properties / category / typeAdded value: +"string" - added
Input schema / properties / known_fieldsAdded value: +{ + "additionalProperties": true, + "default": {}, + "description": "Known values such as ticker, URL, provider, or identifier that improve retrieval.", + "type": "object" +} - changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum candidates, 1-10"New value: +"Maximum number of additional direct tool candidates." - added
Input schema / properties / limit / maximumAdded value: +20 - added
Input schema / properties / limit / minimumAdded value: +1 - added
Input schema / properties / provider_filtersAdded value: +{ + "default": [], + "description": "Optional exact catalog provider keys used to narrow retrieval (for example similarweb). Do not use display brands. Omit this field if the exact key is unknown.", + "items": { + "type": "string" + }, + "maxItems": 50, + "type": "array", + "uniqueItems": true +} - changed
Input schema / properties / query / descriptionPrevious value: -"What you need, in plain language, e.g. 'backlinks of a domain', 'recent tweets by a user', 'insider trades for AAPL'. English works best."New value: +"Natural-language capability or task to discover." - added
Input schema / properties / query / maxLengthAdded value: +2000 - added
Input schema / properties / query / minLengthAdded value: +1 - added
Input schema / properties / session_idAdded value: +{ + "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", + "maxLength": 128, + "pattern": "^[A-Za-z0-9_-]*$", + "type": "string" +} - added
Output schema / propertiesAdded value: +{ + "next_steps_guidance": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "plan": { + "additionalProperties": false, + "anyOf": [ + { + "type": "null" + }, + { + "type": "object" + } + ], + "properties": { + "canonical_use_case": { + "type": "string" + }, + "description": { + "type": "string" + }, + "known_pitfalls": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "plan_ref": { + "type": "string" + }, + "primary_tools": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "recommended_steps": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "related_tools": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + } + }, + "required": [ + "canonical_use_case", + "description", + "known_pitfalls", + "plan_ref", + "primary_tools", + "recommended_steps", + "related_tools" + ] + }, + "retrieval_mode": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "string" + } + ] + }, + "search_id": { + "type": "string" + }, + "session_id": { + "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", + "maxLength": 128, + "minLength": 1, + "pattern": "^[A-Za-z0-9_-]{1,128}$", + "type": "string" + }, + "tools": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "additionalProperties": false, + "properties": { + "arguments_schema": { + "additionalProperties": true, + "anyOf": [ + { + "type": "null" + }, + { + "type": "object" + } + ] + }, + "description": { + "type": "string" + }, + "execution_supported": { + "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.", + "type": "boolean" + }, + "execution_unsupported_reason": { + "description": "Why execution and quoting remain unavailable through this router.", + "type": "string" + }, + "has_full_schema": { + "type": "boolean" + }, + "match_reasons": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "price": { + "additionalProperties": true, + "type": "object" + }, + "retrieval_debug": { + "additionalProperties": false, + "anyOf": [ + { + "type": "null" + }, + { + "type": "object" + } + ], + "properties": { + "fused_rank": { + "type": "integer" + }, + "fused_score": { + "type": "number" + }, + "lexical_rank": { + "type": "integer" + }, + "lexical_score": { + "type": "number" + }, + "rerank_admission_rank": { + "type": "integer" + }, + "rerank_rank": { + "type": "integer" + }, + "rerank_score": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "number" + } + ] + }, + "runtime_availability": { + "type": "string" + }, + "vector_view_ranks": { + "additionalProperties": { + "type": "integer" + }, + "type": "object" + }, + "vector_view_scores": { + "additionalProperties": { + "type": "number" + }, + "type": "object" + } + }, + "required": [ + "fused_rank", + "fused_score", + "lexical_rank", + "lexical_score", + "rerank_admission_rank", + "rerank_rank", + "runtime_availability", + "vector_view_ranks", + "vector_view_scores" + ] + }, + "summary": { + "type": "string" + }, + "tool": { + "type": "string" + } + }, + "required": [ + "description", + "has_full_schema", + "price", + "summary", + "tool" + ], + "type": "object" + } + } +} - added
Output schema / requiredAdded value: +[ + "next_steps_guidance", + "search_id", + "session_id", + "tools" +]
- Changed
use1 field changed- changed
Input schema / properties / max_price_usd / descriptionPrevious value: -"Refuse the call before any spend if it would cost more than this many USD"New value: +"Refuse the call before any spend if its quoted price is above this many USD"
33 tool updates
- Removed
batch_get_schema - Removed
batch_quote - Changed
batch_use18 fields changed- removed
Input schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema" - added
Input schema / properties / calls / descriptionAdded value: +"Up to 20 items of {call_id, operation_id, arguments}; steps at the same execution_level of a plan go in one batch" - removed
Input schema / properties / calls / items / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema" - changed
Input schema / properties / calls / items / additionalPropertiesPrevious value: -falseNew value: +true - removed
Input schema / properties / calls / items / propertiesRemoved value: -{ - "arguments": { - "additionalProperties": true, - "description": "Strictly schema-compliant arguments using the exact field names and types from this tool's arguments_schema.", - "type": "object" - }, - "call_id": { - "description": "Caller-chosen identifier unique within this batch.", - "maxLength": 128, - "minLength": 1, - "type": "string" - }, - "tool": { - "description": "Exact tool name returned by search or batch_get_schema. Never invent a name.", - "minLength": 1, - "type": "string" - } -} - removed
Input schema / properties / calls / items / requiredRemoved value: -[ - "call_id", - "tool", - "arguments" -] - removed
Input schema / properties / calls / maxItemsRemoved value: -20 - removed
Input schema / properties / calls / minItemsRemoved value: -1 - added
Input schema / properties / max_price_usdAdded value: +{ + "anyOf": [ + { + "type": "number" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Per-call price cap applied to every item" +} - added
Input schema / properties / search_id / anyOfAdded value: +[ + { + "type": "string" + }, + { + "type": "null" + } +] - added
Input schema / properties / search_id / defaultAdded value: +null - changed
Input schema / properties / search_id / descriptionPrevious value: -"Optional search correlation identifier returned by search."New value: +"search_id from the search that found these operations" - removed
Input schema / properties / search_id / typeRemoved value: -"string" - removed
Input schema / properties / session_idRemoved value: -{ - "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", - "maxLength": 128, - "pattern": "^[A-Za-z0-9_-]*$", - "type": "string" -} - removed
Output schema / $defsRemoved value: -{ - "jsonValue": { - "anyOf": [ - { - "additionalProperties": { - "$ref": "#/$defs/jsonValue" - }, - "type": "object" - }, - { - "items": { - "$ref": "#/$defs/jsonValue" - }, - "type": "array" - }, - { - "type": "string" - }, - { - "type": "number" - }, - { - "type": "boolean" - }, - { - "type": "null" - } - ], - "description": "JSON value returned by the upstream tool." - } -} - removed
Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema" - removed
Output schema / propertiesRemoved value: -{ - "batch_id": { - "type": "string" - }, - "error_count": { - "minimum": 0, - "type": "integer" - }, - "next_steps_guidance": { - "description": "Deterministic next-step instructions derived from this result. Not an authorization grant.", - "items": { - "type": "string" - }, - "type": "array" - }, - "results": { - "items": { - "$schema": "https://json-schema.org/draft/2020-12/schema", - "additionalProperties": false, - "properties": { - "call_id": { - "type": "string" - }, - "customer_cost_micros_usd": { - "description": "Actual customer charge settled by AIsaServices, in micro-USD. Omitted when the upstream response does not report it.", - "minimum": 0, - "type": "integer" - }, - "data": { - "$ref": "#/$defs/jsonValue" - }, - "error": { - "anyOf": [ - { - "$schema": "https://json-schema.org/draft/2020-12/schema", - "additionalProperties": false, - "properties": { - "message": { - "type": "string" - }, - "retryable": { - "type": "boolean" - }, - "status": { - "type": "integer" - }, - "type": { - "enum": [ - "validation", - "authentication", - "payment", - "permission", - "rate_limit", - "upstream", - "timeout", - "internal" - ], - "type": "string" - } - }, - "required": [ - "type", - "status", - "retryable" - ], - "type": "object" - }, - { - "type": "null" - } - ] - }, - "request_id": { - "type": "string" - }, - "successful": { - "type": "boolean" - }, - "tool": { - "type": "string" - }, - "upstream_status": { - "description": "HTTP status returned by AIsaServices when a request was dispatched.", - "type": "integer" - } - }, - "required": [ - "call_id", - "tool", - "successful", - "request_id" - ], - "type": "object" - }, - "type": "array" - }, - "session_id": { - "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", - "maxLength": 128, - "minLength": 1, - "pattern": "^[A-Za-z0-9_-]*$", - "type": "string" - }, - "success_count": { - "minimum": 0, - "type": "integer" - }, - "total_count": { - "minimum": 1, - "type": "integer" - } -} - removed
Output schema / requiredRemoved value: -[ - "session_id", - "batch_id", - "total_count", - "success_count", - "error_count", - "results", - "next_steps_guidance" -]
- Changed
get_dataforseo_backlinks_index1 field changed- removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
get_details13 fields changed- removed
Input schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema" - added
Input schema / properties / argumentsAdded value: +{ + "anyOf": [ + { + "additionalProperties": true, + "type": "object" + }, + { + "type": "null" + } + ], + "default": null, + "description": "The arguments the operation would be called with, for a price that reflects them. Keyed by operation_id for a batch, or passed flat for a single operation_id. Routes whose required parameters are validated before pricing have no price without them." +} - removed
Input schema / properties / include_arguments_schemaRemoved value: -{ - "default": true, - "description": "Return the complete arguments_schema. Defaults to true.", - "type": "boolean" -} - changed
Input schema / properties / include_documentation / descriptionPrevious value: -"Return the complete immutable public OpenAPI operation, referenced declarations, provenance and scoped completeness. Documentation does not change execution support."New value: +"Include the complete native public OpenAPI document, reference closure and scoped completeness. Existing execution schemas remain unchanged." - removed
Input schema / properties / include_response_schemaRemoved value: -{ - "default": false, - "description": "Return the complete response_schema. Defaults to false.", - "type": "boolean" -} - added
Input schema / properties / operation_idAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "One operation_id from search" +} - added
Input schema / properties / operation_idsAdded value: +{ + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Up to 20 operation_ids, for a batch" +} - removed
Input schema / properties / session_idRemoved value: -{ - "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", - "maxLength": 128, - "pattern": "^[A-Za-z0-9_-]*$", - "type": "string" -} - removed
Input schema / properties / toolsRemoved value: -{ - "description": "Exact tool names returned by search whose complete contracts are needed. Never invent tool names.", - "items": { - "minLength": 1, - "pattern": "^\\S(?:.*\\S)?$", - "type": "string" - }, - "maxItems": 20, - "minItems": 1, - "type": "array", - "uniqueItems": true -} - added
Input schema / properties / with_quoteAdded value: +{ + "default": true, + "description": "Whether each operation is priced for this account before the answer. One round trip per operation; spends nothing.", + "type": "boolean" +} - removed
Input schema / requiredRemoved value: -[ - "tools" -] - removed
Output schema / propertiesRemoved value: -{ - "error_count": { - "type": "integer" - }, - "next_steps_guidance": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "array" - } - ], - "items": { - "type": "string" - } - }, - "session_id": { - "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", - "maxLength": 128, - "minLength": 1, - "pattern": "^[A-Za-z0-9_-]{1,128}$", - "type": "string" - }, - "success_count": { - "type": "integer" - }, - "tools": { - "additionalProperties": { - "additionalProperties": false, - "properties": { - "arguments_schema": { - "additionalProperties": true, - "anyOf": [ - { - "type": "null" - }, - { - "type": "object" - } - ] - }, - "canonical_operation_id": { - "type": "string" - }, - "documentation": { - "additionalProperties": true, - "type": "object" - }, - "error": { - "additionalProperties": false, - "anyOf": [ - { - "type": "null" - }, - { - "type": "object" - } - ], - "properties": { - "code": { - "type": "string" - }, - "message": { - "type": "string" - } - }, - "required": [ - "code", - "message" - ] - }, - "execution_supported": { - "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.", - "type": "boolean" - }, - "execution_unsupported_reason": { - "description": "Why execution and quoting remain unavailable through this router.", - "type": "string" - }, - "idempotent": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "boolean" - } - ] - }, - "known_pitfalls": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "array" - } - ], - "items": { - "type": "string" - } - }, - "read_only": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "boolean" - } - ] - }, - "response_schema": { - "additionalProperties": true, - "anyOf": [ - { - "type": "null" - }, - { - "type": "object" - } - ] - }, - "side_effects": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "array" - } - ], - "items": { - "type": "string" - } - }, - "successful": { - "type": "boolean" - } - }, - "required": [ - "successful" - ], - "type": "object" - }, - "type": "object" - }, - "total_count": { - "type": "integer" - } -} - removed
Output schema / requiredRemoved value: -[ - "error_count", - "next_steps_guidance", - "session_id", - "success_count", - "tools", - "total_count" -]
- Changed
get_semrush_backlink_anchors4 fields changed- added
Input schema / properties / target / descriptionAdded value: +"Target domain or URL." - added
Input schema / properties / target / exampleAdded value: +"ahrefs.com" - added
Input schema / properties / target_type / descriptionAdded value: +"One of `root_domain`, `domain`, or `url`." - added
Input schema / properties / target_type / exampleAdded value: +"root_domain"
- Changed
get_semrush_backlink_competitors4 fields changed- added
Input schema / properties / target / descriptionAdded value: +"Target domain or URL." - added
Input schema / properties / target / exampleAdded value: +"ahrefs.com" - added
Input schema / properties / target_type / descriptionAdded value: +"One of `root_domain`, `domain`, or `url`." - added
Input schema / properties / target_type / exampleAdded value: +"root_domain"
- Changed
get_semrush_backlinks4 fields changed- added
Input schema / properties / target / descriptionAdded value: +"Target domain or URL." - added
Input schema / properties / target / exampleAdded value: +"ahrefs.com" - added
Input schema / properties / target_type / descriptionAdded value: +"One of `root_domain`, `domain`, or `url`." - added
Input schema / properties / target_type / exampleAdded value: +"root_domain"
- Changed
get_semrush_backlinks_overview1 field changed- added
Input schema / properties / target / descriptionAdded value: +"Target root domain, e.g. `ahrefs.com`."
- Changed
get_semrush_indexed_pages4 fields changed- added
Input schema / properties / target / descriptionAdded value: +"Target domain or URL." - added
Input schema / properties / target / exampleAdded value: +"ahrefs.com" - added
Input schema / properties / target_type / descriptionAdded value: +"One of `root_domain`, `domain`, or `url`." - added
Input schema / properties / target_type / exampleAdded value: +"root_domain"
- Changed
get_semrush_referring_domains4 fields changed- added
Input schema / properties / target / descriptionAdded value: +"Target domain or URL." - added
Input schema / properties / target / exampleAdded value: +"ahrefs.com" - added
Input schema / properties / target_type / descriptionAdded value: +"One of `root_domain`, `domain`, or `url`." - added
Input schema / properties / target_type / exampleAdded value: +"root_domain"
- Changed
post_dataforseo_backlinks_anchors_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "filters": [ - "anchor", - "like", - "%news%" - ], - "limit": 4, - "order_by": [ - "backlinks,desc" - ], - "target": "forbes.com" - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "filters": [ - "anchor", - "like", - "%news%" - ], - "limit": 4, - "order_by": [ - "backlinks,desc" - ], - "target": "forbes.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get anchors for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "backlinks_filters": { + "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [[\"dofollow\", \"=\", true]]", + "items": {}, + "type": "array" + }, + "backlinks_status_type": { + "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", + "type": "string" + }, + "exclude_internal_backlinks": { + "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, the backlinks from subdomains of the target will be ommited and you won’t receive the same domain in the response; default value: true", + "type": "boolean" + }, + "filters": { + "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"referring_links_types.anchors\",\">\",\"1\"] [[\"broken_pages\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", + "items": {}, + "type": "array" + }, + "include_indirect_links": { + "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", + "type": "boolean" + }, + "include_subdomains": { + "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", + "type": "boolean" + }, + "internal_list_limit": { + "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", + "type": "integer" + }, + "limit": { + "description": "the maximum number of returned anchors optional field default value: 100 maximum value: 1000", + "type": "integer" + }, + "offset": { + "description": "offset in the results array of returned anchors optional field default value: 0 if you specify the 10 value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", + "type": "integer" + }, + "order_by": { + "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", + "items": { + "type": "string" + }, + "type": "array" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "target": { + "description": "domain, subdomain or webpage to get anchors for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", + "type": "string" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "target" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_backlinks_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "filters": [ - "dofollow", - "=", - true - ], - "limit": 5, - "mode": "as_is", - "target": "forbes.com" - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "filters": [ - "dofollow", - "=", - true - ], - "limit": 5, - "mode": "as_is", - "target": "forbes.com" - } - ], - "properties": { - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "custom_mode": { - "additionalProperties": { - "type": [ - "object", - "null" - ] - }, - "description": "<em>detailed results grouping type</em><br>optional field<br>use this object to get a specific number of backlinks per <code>field</code><br>if you use <code>custom_mode</code>, then <code>mode</code> will be ignored<br>example:<br><code>\"custom_mode\": {\"field\": \"domain\", \"value\": 100}</code>", - "type": [ - "object", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>regex</code>, <code>not_regex</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"80\"]</code><p><code>[[\"page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"dofollow\",\"=\",true]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"text_pre\",\"like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "mode": { - "description": "<em>results grouping type</em><br>optional field<br>possible grouping types:<br><code>as_is</code> - returns all backlinks<br><code>one_per_domain</code> - returns one backlink per domain<br><code>one_per_anchor</code> - returns one backlink per anchor<p>default value: <code>as_is</code>", - "type": [ - "string", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks;<br><strong>Note:</strong> the maximum value is <code>20,000</code>, use the <code>search_after_token</code> if you would like to offset more results", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "search_after_token": { - "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get backlinks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "backlinks_status_type": { + "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", + "type": "string" + }, + "custom_mode": { + "description": "detailed results grouping type optional field use this object to get a specific number of backlinks per field if you use custom_mode, then mode will be ignored example: \"custom_mode\": {\"field\": \"domain\", \"value\": 100}", + "properties": { + "field": { + "type": "string" + }, + "value": { + "type": "integer" + } + }, + "type": "object" + }, + "exclude_internal_backlinks": { + "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results default value: true", + "type": "boolean" + }, + "filters": { + "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: =, , in, not_in, like, not_like, ilike, not_ilike, regex, not_regex, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"rank\",\">\",\"80\"] [[\"page_from_rank\",\">\",\"55\"], \"and\", [\"dofollow\",\"=\",true]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"text_pre\",\"like\",\"%seo%\"]]] The full list of possible filters is available here.", + "items": {}, + "type": "array" + }, + "include_subdomains": { + "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", + "type": "boolean" + }, + "limit": { + "description": "the maximum number of returned backlinks optional field default value: 100 maximum value: 1000", + "type": "integer" + }, + "mode": { + "description": "results grouping type optional field possible grouping types: as_is – returns all backlinks one_per_domain – returns one backlink per domain one_per_anchor – returns one backlink per anchor default value: as_is", + "type": "string" + }, + "offset": { + "description": "offset in the results array of the returned backlinks optional field default value: 0 if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks; Note: the maximum value is 20,000, use the search_after_token if you would like to offset more results", + "type": "integer" + }, + "order_by": { + "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"rank,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"domain_from_rank,desc\",\"page_from_rank,asc\"]", + "items": { + "type": "string" + }, + "type": "array" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "search_after_token": { + "description": "token for subsequent requests optional field provided in the identical filed of the response to each request; use this parameter to avoid timeouts while trying to obtain over 20,000 results in a single request; by specifying the unique search_after_token value from the response array, you will get the subsequent results of the initial task; search_after_token values are unique for each subsequent task ; Note: if the search_after_token is specified in the request, all other parameters should be identical to the previous request", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "target": { + "description": "domain, subdomain or webpage to get backlinks for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", + "type": "string" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "target" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_bulk_backlinks_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get the number of backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "targets": { + "description": "domains, subdomains or webpages to get the number of backlinks for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", + "items": { + "type": "string" + }, + "type": "array" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "targets" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_bulk_new_lost_backlinks_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "date_from": "2026-08-31 11:12:35", - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "date_from": "2026-08-31 11:12:35", - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks;<br>the backlinks that appeared in our index after the specified date will be considered as new;<br>the backlinks that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get new & lost backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without `https://` and `www.` the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br> `\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "date_from": { + "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost backlinks; the backlinks that appeared in our index after the specified date will be considered as new; the backlinks that weren’t found after the specified date, but were present before, will be considered as lost; default value: today’s date -(minus) one month; e.g. if today is 2021-10-13, default date_from will be 2021-09-13. minimum value equals today’s date -(minus) one year; e.g. if today is 2021-10-13, minimum date_from will be 2020-10-13. date format: \"yyyy-mm-dd\" example: \"2021-01-01\"", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "targets": { + "description": "domains, subdomains or webpages to get new & lost backlinks for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", + "items": { + "type": "string" + }, + "type": "array" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "targets" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_bulk_new_lost_ref_domains_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "datetime_from": "2026-12-31", - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "datetime_from": "2026-12-31", - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost referring domains;<br>the referring domains that appeared in our index after the specified date will be considered as new;<br>the referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get new & lost referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "date_from": { + "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost referring domains; the referring domains that appeared in our index after the specified date will be considered as new; the referring domains that weren’t found after the specified date, but were present before, will be considered as lost; default value: today’s date -(minus) one month; e.g. if today is 2021-10-13, default date_from will be 2021-09-13. minimum value equals today’s date -(minus) one year; e.g. if today is 2021-10-13, minimum date_from will be 2020-10-13. date format: \"yyyy-mm-dd\" example: \"2021-01-01\"", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "targets": { + "description": "domains, subdomains or webpages to get new & lost referring domains for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", + "items": { + "type": "string" + }, + "type": "array" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "targets" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_bulk_pages_summary_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "targets": [ - "https://dataforseo.com/solutions", - "https://dataforseo.com/about-us" - ] - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "targets": [ - "https://dataforseo.com/solutions", - "https://dataforseo.com/about-us" - ] - } - ], - "properties": { - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>you can specify up to 1000 pages, domains, or subdomains in each request.<br><strong>note that the URLs you set in a single request cannot belong to more than 100 different domains</strong>.", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "include_subdomains": { + "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", + "type": "boolean" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "targets": { + "description": "domains, subdomains or webpages to get summary data for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://) you can specify up to 1000 pages, domains, or subdomains in each request. note that the URLs you set in a single request cannot belong to more than 100 different domains.", + "items": { + "type": "string" + }, + "type": "array" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "targets" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_bulk_ranks_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "targets": { + "description": "domains, subdomains or webpages to get rank for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", + "items": { + "type": "string" + }, + "type": "array" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "targets" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_bulk_referring_domains_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get the number of referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "targets": { + "description": "domains, subdomains or webpages to get the number of referring domains for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", + "items": { + "type": "string" + }, + "type": "array" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "targets" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_bulk_spam_score_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "targets": [ - "forbes.com", - "cnn.com", - "bbc.com", - "yelp.com", - "https://www.apple.com/iphone/", - "https://ahrefs.com/blog/", - "ibm.com", - "https://variety.com/", - "https://stackoverflow.com/", - "www.trustpilot.com" - ] - } - ], - "properties": { - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", - "items": { - "type": "string" - }, - "type": "array" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "targets": { + "description": "domains, subdomains or webpages to get rank for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", + "items": { + "type": "string" + }, + "type": "array" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "targets" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_competitors_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "filters": [ - "rank", - ">", - 100 - ], - "limit": 5, - "order_by": [ - "rank,desc" - ], - "target": "dataforseo.com" - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "filters": [ - "rank", - ">", - 100 - ], - "limit": 5, - "order_by": [ - "rank,desc" - ], - "target": "dataforseo.com" - } - ], - "properties": { - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "exclude_large_domains": { - "description": "<em>indicates whether large domain will appear in results</em><br>optional field<br>if set to <code>true</code>, the results from the large domain (google.com, amazon.com, etc.) will be omitted;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"100\"]</code><p><code>[[\"target\",\"like\",\"%forbes%\"],<br>\"and\",<br>[[\"rank\",\">\",\"100\"],\"or\",[\"intersections\",\">\",\"5\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "main_domain": { - "description": "<em>indicates if only main domain of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>true</code>, only the main domain will be included in search;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"intersections,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get competitor domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "exclude_internal_backlinks": { + "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results default value: true", + "type": "boolean" + }, + "exclude_large_domains": { + "description": "indicates whether large domain will appear in results optional field if set to true, the results from the large domain (google.com, amazon.com, etc.) will be omitted; default value: true", + "type": "boolean" + }, + "filters": { + "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"rank\",\">\",\"100\"] [[\"target\",\"like\",\"%forbes%\"], \"and\", [[\"rank\",\">\",\"100\"],\"or\",[\"intersections\",\">\",\"5\"]]] The full list of possible filters is available here.", + "items": {}, + "type": "array" + }, + "limit": { + "description": "the maximum number of returned domains optional field default value: 100 maximum value: 1000", + "type": "integer" + }, + "main_domain": { + "description": "indicates if only main domain of the target will be included in the search optional field if set to true, only the main domain will be included in search; default value: true", + "type": "boolean" + }, + "offset": { + "description": "offset in the results array of returned domains optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": "integer" + }, + "order_by": { + "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"rank,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"intersections,desc\",\"rank,asc\"]", + "items": { + "type": "string" + }, + "type": "array" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "target": { + "description": "domain, subdomain or webpage to get competitor domains for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", + "type": "string" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "target" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_domain_intersection_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "exclude_internal_backlinks": true, - "exclude_targets": [ - "semrush.com" - ], - "include_subdomains": false, - "limit": 5, - "order_by": [ - "1.backlinks,desc" - ], - "targets": { - "1": "moz.com", - "2": "ahrefs.com" - } - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "exclude_internal_backlinks": true, - "exclude_targets": [ - "semrush.com" - ], - "include_subdomains": false, - "limit": 5, - "order_by": [ - "1.backlinks,desc" - ], - "targets": { - "1": "moz.com", - "2": "ahrefs.com" - } - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be omitted and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "exclude_targets": { - "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can specify up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring domains that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"2.referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"1.backlinks\",\">\",\"10\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"2.target\",\"like\",\"%dataforseo.com%\"],\"or\",[\"1.referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "intersection_mode": { - "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified domains<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", - "type": [ - "string", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned results</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the array of returned results</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "additionalProperties": { - "type": [ - "string", - "null" - ] - }, - "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", - "type": [ - "object", - "null" - ] - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "backlinks_filters": { + "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [[\"dofollow\", \"=\", true]]", + "items": {}, + "type": "array" + }, + "backlinks_status_type": { + "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your targets; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", + "type": "string" + }, + "exclude_internal_backlinks": { + "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, the backlinks from subdomains of the target will be omitted and you won’t receive the same domain in the response; default value: true", + "type": "boolean" + }, + "exclude_targets": { + "description": "domains, subdomains or webpages you want to exclude optional field you can specify up to 10 domains, subdomains or webpages if you use this array, results will contain the referring domains that link to targets but don’t link to exclude_targets example: \"exclude_targets\": [ \"bbc.com\", \"https://www.apple.com/iphone/*\", \"https://dataforseo.com/apis/*\"]", + "items": { + "type": "string" + }, + "type": "array" + }, + "filters": { + "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"1.internal_links_count\",\">\",\"1\"] [[\"2.referring_pages\",\">\",\"2\"], \"and\", [\"1.backlinks\",\">\",\"10\"]] [[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"2.target\",\"like\",\"%dataforseo.com%\"],\"or\",[\"1.referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", + "items": {}, + "type": "array" + }, + "include_indirect_links": { + "description": "indicates if indirect links to the targets will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page if set to false, indirect links will be ignored default value: true", + "type": "boolean" + }, + "include_subdomains": { + "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", + "type": "boolean" + }, + "internal_list_limit": { + "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", + "type": "integer" + }, + "intersection_mode": { + "description": "indicates whether to intersect backlinks optional field use this field to intersect or merge results for the specified domains possible values: all, partial all – results are based on all backlinks; partial – results are based on the intersecting backlinks only; default value: all", + "type": "string" + }, + "limit": { + "description": "the maximum number of returned results optional field default value: 100 maximum value: 1000", + "type": "integer" + }, + "offset": { + "description": "offset in the array of returned results optional field default value: 0 if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", + "type": "integer" + }, + "order_by": { + "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", + "items": { + "type": "string" + }, + "type": "array" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "targets": { + "additionalProperties": { + "type": "string" + }, + "description": "domains, subdomains or webpages to get links for required field you can set up to 20 domains, subdomains or webpages a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://) example: \"targets\": { \"1\": \"http://planet.postgresql.org/\", \"2\": \"http://gborg.postgresql.org/\" }", + "type": "object" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "targets" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_domain_pages_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "filters": [ - [ - "page_summary.backlinks", - ">", - 5 - ], - "and", - [ - "page", - "like", - "%sites%" - ] - ], - "limit": 5, - "target": "forbes.com" - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "filters": [ - [ - "page_summary.backlinks", - ">", - 5 - ], - "and", - [ - "page", - "like", - "%sites%" - ] - ], - "limit": 5, - "target": "forbes.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"meta.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"meta.external_links_count\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_visited\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"title\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned pages</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned pages</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"page_summary.backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"page_summary.backlinks,desc\",\"page_summary.rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain or subdomain</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>forbes.com</code>", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "backlinks_filters": { + "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [\"dofollow\", \"=\", true]", + "items": {}, + "type": "array" + }, + "backlinks_status_type": { + "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", + "type": "string" + }, + "exclude_internal_backlinks": { + "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results default value: true", + "type": "boolean" + }, + "filters": { + "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"meta.internal_links_count\",\">\",\"1\"] [[\"meta.external_links_count\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_visited\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"title\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", + "items": {}, + "type": "array" + }, + "include_subdomains": { + "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", + "type": "boolean" + }, + "internal_list_limit": { + "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", + "type": "integer" + }, + "limit": { + "description": "the maximum number of returned pages optional field default value: 100 maximum value: 1000", + "type": "integer" + }, + "offset": { + "description": "offset in the results array of returned pages optional field default value: 0 if you specify the 10 value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages", + "type": "integer" + }, + "order_by": { + "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"page_summary.backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"page_summary.backlinks,desc\",\"page_summary.rank,asc\"]", + "items": { + "type": "string" + }, + "type": "array" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "target": { + "description": "domain or subdomain required field a domain or a subdomain should be specified without https:// and www. example: forbes.com", + "type": "string" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "target" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_domain_pages_summary_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "limit": 4, - "order_by": [ - "backlinks,desc" - ], - "target": "forbes.com" - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "limit": 4, - "order_by": [ - "backlinks,desc" - ], - "target": "forbes.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, backlinks from the subdomains of the <code>target</code> domain will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> domain will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "backlinks_filters": { + "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [[\"dofollow\", \"=\", true]]", + "items": {}, + "type": "array" + }, + "backlinks_status_type": { + "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", + "type": "string" + }, + "exclude_internal_backlinks": { + "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, backlinks from the subdomains of the target domain will be ommited and you won’t receive the same domain in the response; default value: true", + "type": "boolean" + }, + "filters": { + "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"referring_links_types.anchors\",\">\",\"1\"] [[\"broken_pages\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", + "items": {}, + "type": "array" + }, + "include_indirect_links": { + "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", + "type": "boolean" + }, + "include_subdomains": { + "description": "indicates if the subdomains of the target domain will be included in the search optional field if set to false, the subdomains will be ignored default value: true", + "type": "boolean" + }, + "internal_list_limit": { + "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", + "type": "integer" + }, + "limit": { + "description": "the maximum number of returned anchors optional field default value: 100 maximum value: 1000", + "type": "integer" + }, + "offset": { + "description": "offset in the results array of returned anchors optional field default value: 0 if you specify the 10 value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", + "type": "integer" + }, + "order_by": { + "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", + "items": { + "type": "string" + }, + "type": "array" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "target": { + "description": "domain, subdomain or webpage to get summary data for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", + "type": "string" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "target" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_history_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "date_from": "2020-01-01", - "date_to": "2021-01-01", - "target": "cnn.com" - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "date_from": "2020-01-01", - "date_to": "2021-01-01", - "target": "cnn.com" - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>minimum value <code>2019-01-01</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", - "type": [ - "string", - "null" - ] - }, - "date_to": { - "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", - "type": [ - "string", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code>", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "date_from": { + "description": "starting date of the time range optional field minimum value 2019-01-01 if you don’t specify this field, the minimum value will be used by default date format: \"yyyy-mm-dd\" example: \"2019-01-15\"", + "type": "string" + }, + "date_to": { + "description": "ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default date format: \"yyyy-mm-dd\" example: \"2019-01-15\"", + "type": "string" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "target": { + "description": "domain required field a domain should be specified without https:// and www.", + "type": "string" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "target" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_page_intersection_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "exclude_targets": [ - "skysports.com" - ], - "filters": [ - [ - "2.domain_from_rank", - ">", - 400 - ], - "and", - [ - "1.dofollow", - "=", - true - ] - ], - "limit": 5, - "order_by": [ - "1.rank,desc" - ], - "targets": { - "1": "football.com", - "2": "fifa.com" - } - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "exclude_targets": [ - "skysports.com" - ], - "filters": [ - [ - "2.domain_from_rank", - ">", - 400 - ], - "and", - [ - "1.dofollow", - "=", - true - ] - ], - "limit": 5, - "order_by": [ - "1.rank,desc" - ], - "targets": { - "1": "football.com", - "2": "fifa.com" - } - } - ], - "properties": { - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the result<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "exclude_targets": { - "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can set up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring pages that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.rank\",\">\",\"80\"]</code><p><code>[[\"2.page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"1.original\",\"=\",\"true\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"1.acnhor\",\"like\",\"%seo%\"],\"or\",[\"1.text_pre\",\"not_like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>targets</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>attributes</code><br><code>domain_from_platform_type</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "intersection_mode": { - "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified URLs<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", - "type": [ - "string", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "targets": { - "additionalProperties": { - "type": [ - "string", - "null" - ] - }, - "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", - "type": [ - "object", - "null" - ] - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "backlinks_status_type": { + "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your targets; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", + "type": "string" + }, + "exclude_internal_backlinks": { + "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the result default value: true", + "type": "boolean" + }, + "exclude_targets": { + "description": "domains, subdomains or webpages you want to exclude optional field you can set up to 10 domains, subdomains or webpages if you use this array, results will contain the referring pages that link to targets but don’t link to exclude_targets example: \"exclude_targets\": [ \"bbc.com\", \"https://www.apple.com/iphone/*\", \"https://dataforseo.com/apis/*\"]", + "items": { + "type": "string" + }, + "type": "array" + }, + "filters": { + "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"1.rank\",\">\",\"80\"] [[\"2.page_from_rank\",\">\",\"55\"], \"and\", [\"1.original\",\"=\",\"true\"]] [[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"1.acnhor\",\"like\",\"%seo%\"],\"or\",[\"1.text_pre\",\"not_like\",\"%seo%\"]]] The full list of possible filters is available here.", + "items": {}, + "type": "array" + }, + "include_indirect_links": { + "description": "indicates if indirect links to the targets will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page if set to false, indirect links will be ignored default value: true", + "type": "boolean" + }, + "include_subdomains": { + "description": "indicates if the subdomains of the targets will be included in the search optional field if set to false, the subdomains will be ignored default value: true", + "type": "boolean" + }, + "internal_list_limit": { + "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: attributes domain_from_platform_type default value: 10 maximum value: 1000", + "type": "integer" + }, + "intersection_mode": { + "description": "indicates whether to intersect backlinks optional field use this field to intersect or merge results for the specified URLs possible values: all, partial all – results are based on all backlinks; partial – results are based on the intersecting backlinks only; default value: all", + "type": "string" + }, + "limit": { + "description": "the maximum number of returned backlinks optional field default value: 100 maximum value: 1000", + "type": "integer" + }, + "offset": { + "description": "offset in the results array of the returned backlinks optional field default value: 0 if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", + "type": "integer" + }, + "order_by": { + "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"rank,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"domain_from_rank,desc\",\"page_from_rank,asc\"]", + "items": { + "type": "string" + }, + "type": "array" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "targets": { + "additionalProperties": { + "type": "string" + }, + "description": "domains, subdomains or webpages to get links for required field you can set up to 20 domains, subdomains or webpages a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://) example: \"targets\": { \"1\": \"http://planet.postgresql.org/\", \"2\": \"http://gborg.postgresql.org/\" }", + "type": "object" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "targets" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_referring_domains_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "backlinks_filters": [ - "dofollow", - "=", - true - ], - "exclude_internal_backlinks": true, - "filters": [ - "backlinks", - ">", - 100 - ], - "limit": 5, - "order_by": [ - "rank,desc" - ], - "target": "backlinko.com" - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "backlinks_filters": [ - "dofollow", - "=", - true - ], - "exclude_internal_backlinks": true, - "filters": [ - "backlinks", - ">", - 100 - ], - "limit": 5, - "order_by": [ - "rank,desc" - ], - "target": "backlinko.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"domain\",\"like\",\"%dataforseo.com%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get referring domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "backlinks_filters": { + "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [\"dofollow\", \"=\", true]", + "items": {}, + "type": "array" + }, + "backlinks_status_type": { + "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", + "type": "string" + }, + "exclude_internal_backlinks": { + "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, the backlinks from subdomains of the target will be ommited and you won’t receive the same domain in the response; default value: true", + "type": "boolean" + }, + "filters": { + "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"referring_pages\",\">\",\"1\"] [[\"referring_pages\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"domain\",\"like\",\"%dataforseo.com%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", + "items": {}, + "type": "array" + }, + "include_indirect_links": { + "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", + "type": "boolean" + }, + "include_subdomains": { + "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", + "type": "boolean" + }, + "internal_list_limit": { + "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", + "type": "integer" + }, + "limit": { + "description": "the maximum number of returned domains optional field default value: 100 maximum value: 1000", + "type": "integer" + }, + "offset": { + "description": "offset in the results array of returned domains optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": "integer" + }, + "order_by": { + "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", + "items": { + "type": "string" + }, + "type": "array" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "target": { + "description": "domain, subdomain or webpage to get referring domains for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", + "type": "string" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "target" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_referring_networks_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "backlinks_filters": [ - "dofollow", - "=", - true - ], - "exclude_internal_backlinks": true, - "filters": [ - "backlinks", - ">", - 100 - ], - "limit": 5, - "network_address_type": "subnet", - "order_by": [ - "rank,desc" - ], - "target": "backlinko.com" - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "backlinks_filters": [ - "dofollow", - "=", - true - ], - "exclude_internal_backlinks": true, - "filters": [ - "backlinks", - ">", - 100 - ], - "limit": 5, - "network_address_type": "subnet", - "order_by": [ - "rank,desc" - ], - "target": "backlinko.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "filters": { - "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"network_address\",\"like\",\"194.1.%\"],\"or\",[\"referring_ips\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "limit": { - "description": "<em>the maximum number of returned networks</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "network_address_type": { - "description": "<em>indicates the type of network to get data for</em><br>optional field<br>possible values: <code>ip</code>, <code>subnet</code><br>default value: <code>ip</code>", - "type": [ - "string", - "null" - ] - }, - "offset": { - "description": "<em>offset in the results array of returned networks</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": [ - "integer", - "null" - ] - }, - "order_by": { - "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", - "items": { - "type": "string" - }, - "type": [ - "array", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get referring networks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "backlinks_filters": { + "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [[\"dofollow\", \"=\", true]]", + "items": {}, + "type": "array" + }, + "backlinks_status_type": { + "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", + "type": "string" + }, + "exclude_internal_backlinks": { + "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, the backlinks from subdomains of the target will be ommited and you won’t receive the same domain in the response; default value: true", + "type": "boolean" + }, + "filters": { + "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"referring_pages\",\">\",\"1\"] [[\"referring_pages\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"network_address\",\"like\",\"194.1.%\"],\"or\",[\"referring_ips\",\">\",\"10\"]]] The full list of possible filters is available here.", + "items": {}, + "type": "array" + }, + "include_indirect_links": { + "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", + "type": "boolean" + }, + "include_subdomains": { + "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", + "type": "boolean" + }, + "internal_list_limit": { + "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", + "type": "integer" + }, + "limit": { + "description": "the maximum number of returned networks optional field default value: 100 maximum value: 1000", + "type": "integer" + }, + "network_address_type": { + "description": "indicates the type of network to get data for optional field possible values: ip, subnet default value: ip", + "type": "string" + }, + "offset": { + "description": "offset in the results array of returned networks optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": "integer" + }, + "order_by": { + "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", + "items": { + "type": "string" + }, + "type": "array" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "target": { + "description": "domain, subdomain or webpage to get referring networks for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", + "type": "string" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "target" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_summary_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "backlinks_filters": [ - "dofollow", - "=", - true - ], - "backlinks_status_type": "all", - "include_subdomains": true, - "internal_list_limit": 10, - "target": "explodingtopics.com" - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "backlinks_filters": [ - "dofollow", - "=", - true - ], - "backlinks_status_type": "all", - "include_subdomains": true, - "internal_list_limit": 10, - "target": "explodingtopics.com" - } - ], - "properties": { - "backlinks_filters": { - "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", - "items": { - "type": [ - "object", - "null" - ] - }, - "type": [ - "array", - "null" - ] - }, - "backlinks_status_type": { - "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", - "type": [ - "string", - "null" - ] - }, - "exclude_internal_backlinks": { - "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_indirect_links": { - "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "internal_list_limit": { - "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", - "type": [ - "integer", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain, subdomain or webpage to get data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "backlinks_filters": { + "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [\"dofollow\", \"=\", true]", + "items": {}, + "type": "array" + }, + "backlinks_status_type": { + "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", + "type": "string" + }, + "exclude_internal_backlinks": { + "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results default value: true", + "type": "boolean" + }, + "include_indirect_links": { + "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", + "type": "boolean" + }, + "include_subdomains": { + "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", + "type": "boolean" + }, + "internal_list_limit": { + "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", + "type": "integer" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "target": { + "description": "domain, subdomain or webpage to get data for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", + "type": "string" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "target" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_timeseries_new_lost_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "date_from": "2021-12-01", - "date_to": "2022-02-01", - "group_range": "month", - "target": "dataforseo.com" - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "date_from": "2021-12-01", - "date_to": "2022-02-01", - "group_range": "month", - "target": "dataforseo.com" - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", - "type": [ - "string", - "null" - ] - }, - "date_to": { - "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", - "type": [ - "string", - "null" - ] - }, - "group_range": { - "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", - "type": [ - "string", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "date_from": { + "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains; the backlinks and referring domains that appeared in our index after the specified date will be considered as new; the backlinks and referring domains that weren’t found after the specified date, but were present before, will be considered as lost; minimum value: 2019-01-30 maximum value shouldn’t exceed the date specified in the date_to date format: \"yyyy-mm-dd\" example: \"2021-01-01\"", + "type": "string" + }, + "date_to": { + "description": "ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default minimum value shouldn’t preceed the date specified in the date_from maximum value: today’s date date format: \"yyyy-mm-dd\" example: \"2021-01-15\"", + "type": "string" + }, + "group_range": { + "description": "time range which will be used to group the results optional field default value: month possible values: day, week, month, year note: for day, we will return items corresponding to all dates between and including date_from and date_to; for week/month/year, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year for example, if you specify: \"group_range\": \"month\", \"date_from\": \"2022-03-23\", \"date_to\": \"2022-05-13\" we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: 2022-03-31, 2022-04-30, 2022-05-31 if there is no data for a certain day/week/month/year, we will return 0", + "type": "string" + }, + "include_subdomains": { + "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", + "type": "boolean" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "target": { + "description": "domain to get data for required field a domain should be specified without https:// and www. example: \"forbes.com\"", + "type": "string" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "target" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
post_dataforseo_backlinks_timeseries_summary_live7 fields changed- removed
Input schema / properties / body / exampleRemoved value: -[ - { - "date_from": "2021-12-01", - "date_to": "2022-02-01", - "group_range": "month", - "target": "dataforseo.com" - } -] - removed
Input schema / properties / body / items / anyOfRemoved value: -[ - { - "example": [ - { - "date_from": "2021-12-01", - "date_to": "2022-02-01", - "group_range": "month", - "target": "dataforseo.com" - } - ], - "properties": { - "date_from": { - "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for summary data;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", - "type": [ - "string", - "null" - ] - }, - "date_to": { - "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", - "type": [ - "string", - "null" - ] - }, - "group_range": { - "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", - "type": [ - "string", - "null" - ] - }, - "include_subdomains": { - "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", - "type": [ - "boolean", - "null" - ] - }, - "rank_scale": { - "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", - "type": [ - "string", - "null" - ] - }, - "tag": { - "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", - "type": [ - "string", - "null" - ] - }, - "target": { - "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", - "type": "string" - } - }, - "type": "object" - } -] - added
Input schema / properties / body / items / propertiesAdded value: +{ + "date_from": { + "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for summary data; minimum value: 2019-01-30 maximum value shouldn’t exceed the date specified in the date_to date format: \"yyyy-mm-dd\" example: \"2021-01-01\"", + "type": "string" + }, + "date_to": { + "description": "ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default minimum value shouldn’t preceed the date specified in the date_from maximum value: today’s date date format: \"yyyy-mm-dd\" example: \"2021-01-15\"", + "type": "string" + }, + "group_range": { + "description": "time range which will be used to group the results optional field default value: month possible values: day, week, month, year note: for day, we will return items corresponding to all dates between and including date_from and date_to; for week/month/year, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year for example, if you specify: \"group_range\": \"month\", \"date_from\": \"2022-03-23\", \"date_to\": \"2022-05-13\" we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: 2022-03-31, 2022-04-30, 2022-05-31 if there is no data for a certain day/week/month/year, we will return 0", + "type": "string" + }, + "include_subdomains": { + "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", + "type": "boolean" + }, + "rank_scale": { + "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", + "type": "string" + }, + "tag": { + "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", + "type": "string" + }, + "target": { + "description": "domain to get data for required field a domain should be specified without https:// and www. example: \"forbes.com\"", + "type": "string" + } +} - added
Input schema / properties / body / items / requiredAdded value: +[ + "target" +] - changed
Input schema / properties / body / items / typePrevious value: -[ - "object", - "null" -]New value: +"object" - changed
Input schema / requiredPrevious value: -[]New value: +[ + "body" +] - removed
Output schema / x-fastmcp-wrap-resultRemoved value: -true
- Changed
search17 fields changed- removed
Input schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema" - added
Input schema / properties / category / anyOfAdded value: +[ + { + "enum": [ + "seo", + "finance", + "social", + "search", + "sales", + "mail" + ], + "type": "string" + }, + { + "type": "null" + } +] - added
Input schema / properties / category / defaultAdded value: +null - changed
Input schema / properties / category / descriptionPrevious value: -"Restrict retrieval to one category. Omit to search everything. (AIsa-only: tool-router has no equivalent.)"New value: +"Restrict to one category (seo, finance, social, search, sales, mail). Omit to search everything." - removed
Input schema / properties / category / enumRemoved value: -[ - "seo", - "finance", - "social", - "search", - "sales", - "mail" -] - removed
Input schema / properties / category / typeRemoved value: -"string" - removed
Input schema / properties / known_fieldsRemoved value: -{ - "additionalProperties": true, - "default": {}, - "description": "Known values such as ticker, URL, provider, or identifier that improve retrieval.", - "type": "object" -} - changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum number of additional direct tool candidates."New value: +"Maximum candidates, 1-10" - removed
Input schema / properties / limit / maximumRemoved value: -20 - removed
Input schema / properties / limit / minimumRemoved value: -1 - removed
Input schema / properties / provider_filtersRemoved value: -{ - "default": [], - "description": "Optional exact catalog provider keys used to narrow retrieval (for example similarweb). Do not use display brands. Omit this field if the exact key is unknown.", - "items": { - "type": "string" - }, - "maxItems": 50, - "type": "array", - "uniqueItems": true -} - changed
Input schema / properties / query / descriptionPrevious value: -"Natural-language capability or task to discover."New value: +"What you need, in plain language, e.g. 'backlinks of a domain', 'recent tweets by a user', 'insider trades for AAPL'. English works best." - removed
Input schema / properties / query / maxLengthRemoved value: -2000 - removed
Input schema / properties / query / minLengthRemoved value: -1 - removed
Input schema / properties / session_idRemoved value: -{ - "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", - "maxLength": 128, - "pattern": "^[A-Za-z0-9_-]*$", - "type": "string" -} - removed
Output schema / propertiesRemoved value: -{ - "next_steps_guidance": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "array" - } - ], - "items": { - "type": "string" - } - }, - "plan": { - "additionalProperties": false, - "anyOf": [ - { - "type": "null" - }, - { - "type": "object" - } - ], - "properties": { - "canonical_use_case": { - "type": "string" - }, - "description": { - "type": "string" - }, - "known_pitfalls": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "array" - } - ], - "items": { - "type": "string" - } - }, - "plan_ref": { - "type": "string" - }, - "primary_tools": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "array" - } - ], - "items": { - "type": "string" - } - }, - "recommended_steps": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "array" - } - ], - "items": { - "type": "string" - } - }, - "related_tools": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "array" - } - ], - "items": { - "type": "string" - } - } - }, - "required": [ - "canonical_use_case", - "description", - "known_pitfalls", - "plan_ref", - "primary_tools", - "recommended_steps", - "related_tools" - ] - }, - "retrieval_mode": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "string" - } - ] - }, - "search_id": { - "type": "string" - }, - "session_id": { - "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", - "maxLength": 128, - "minLength": 1, - "pattern": "^[A-Za-z0-9_-]{1,128}$", - "type": "string" - }, - "tools": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "array" - } - ], - "items": { - "additionalProperties": false, - "properties": { - "arguments_schema": { - "additionalProperties": true, - "anyOf": [ - { - "type": "null" - }, - { - "type": "object" - } - ] - }, - "description": { - "type": "string" - }, - "execution_supported": { - "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.", - "type": "boolean" - }, - "execution_unsupported_reason": { - "description": "Why execution and quoting remain unavailable through this router.", - "type": "string" - }, - "has_full_schema": { - "type": "boolean" - }, - "match_reasons": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "array" - } - ], - "items": { - "type": "string" - } - }, - "price": { - "additionalProperties": true, - "type": "object" - }, - "retrieval_debug": { - "additionalProperties": false, - "anyOf": [ - { - "type": "null" - }, - { - "type": "object" - } - ], - "properties": { - "fused_rank": { - "type": "integer" - }, - "fused_score": { - "type": "number" - }, - "lexical_rank": { - "type": "integer" - }, - "lexical_score": { - "type": "number" - }, - "rerank_admission_rank": { - "type": "integer" - }, - "rerank_rank": { - "type": "integer" - }, - "rerank_score": { - "anyOf": [ - { - "type": "null" - }, - { - "type": "number" - } - ] - }, - "runtime_availability": { - "type": "string" - }, - "vector_view_ranks": { - "additionalProperties": { - "type": "integer" - }, - "type": "object" - }, - "vector_view_scores": { - "additionalProperties": { - "type": "number" - }, - "type": "object" - } - }, - "required": [ - "fused_rank", - "fused_score", - "lexical_rank", - "lexical_score", - "rerank_admission_rank", - "rerank_rank", - "runtime_availability", - "vector_view_ranks", - "vector_view_scores" - ] - }, - "summary": { - "type": "string" - }, - "tool": { - "type": "string" - } - }, - "required": [ - "description", - "has_full_schema", - "price", - "summary", - "tool" - ], - "type": "object" - } - } -} - removed
Output schema / requiredRemoved value: -[ - "next_steps_guidance", - "search_id", - "session_id", - "tools" -]
- Changed
use1 field changed- changed
Input schema / properties / max_price_usd / descriptionPrevious value: -"Refuse the call before any spend if its quoted price is above this many USD"New value: +"Refuse the call before any spend if it would cost more than this many USD"
33 tool updates
- Added
batch_get_schema - Added
batch_quote - Changed
batch_use18 fields changed- added
Input schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / properties / calls / descriptionRemoved value: -"Up to 20 items of {call_id, operation_id, arguments}; steps at the same execution_level of a plan go in one batch" - added
Input schema / properties / calls / items / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema" - changed
Input schema / properties / calls / items / additionalPropertiesPrevious value: -trueNew value: +false - added
Input schema / properties / calls / items / propertiesAdded value: +{ + "arguments": { + "additionalProperties": true, + "description": "Strictly schema-compliant arguments using the exact field names and types from this tool's arguments_schema.", + "type": "object" + }, + "call_id": { + "description": "Caller-chosen identifier unique within this batch.", + "maxLength": 128, + "minLength": 1, + "type": "string" + }, + "tool": { + "description": "Exact tool name returned by search or batch_get_schema. Never invent a name.", + "minLength": 1, + "type": "string" + } +} - added
Input schema / properties / calls / items / requiredAdded value: +[ + "call_id", + "tool", + "arguments" +] - added
Input schema / properties / calls / maxItemsAdded value: +20 - added
Input schema / properties / calls / minItemsAdded value: +1 - removed
Input schema / properties / max_price_usdRemoved value: -{ - "anyOf": [ - { - "type": "number" - }, - { - "type": "null" - } - ], - "default": null, - "description": "Per-call price cap applied to every item" -} - removed
Input schema / properties / search_id / anyOfRemoved value: -[ - { - "type": "string" - }, - { - "type": "null" - } -] - removed
Input schema / properties / search_id / defaultRemoved value: -null - changed
Input schema / properties / search_id / descriptionPrevious value: -"search_id from the search that found these operations"New value: +"Optional search correlation identifier returned by search." - added
Input schema / properties / search_id / typeAdded value: +"string" - added
Input schema / properties / session_idAdded value: +{ + "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", + "maxLength": 128, + "pattern": "^[A-Za-z0-9_-]*$", + "type": "string" +} - added
Output schema / $defsAdded value: +{ + "jsonValue": { + "anyOf": [ + { + "additionalProperties": { + "$ref": "#/$defs/jsonValue" + }, + "type": "object" + }, + { + "items": { + "$ref": "#/$defs/jsonValue" + }, + "type": "array" + }, + { + "type": "string" + }, + { + "type": "number" + }, + { + "type": "boolean" + }, + { + "type": "null" + } + ], + "description": "JSON value returned by the upstream tool." + } +} - added
Output schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema" - added
Output schema / propertiesAdded value: +{ + "batch_id": { + "type": "string" + }, + "error_count": { + "minimum": 0, + "type": "integer" + }, + "next_steps_guidance": { + "description": "Deterministic next-step instructions derived from this result. Not an authorization grant.", + "items": { + "type": "string" + }, + "type": "array" + }, + "results": { + "items": { + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "call_id": { + "type": "string" + }, + "customer_cost_micros_usd": { + "description": "Actual customer charge settled by AIsaServices, in micro-USD. Omitted when the upstream response does not report it.", + "minimum": 0, + "type": "integer" + }, + "data": { + "$ref": "#/$defs/jsonValue" + }, + "error": { + "anyOf": [ + { + "$schema": "https://json-schema.org/draft/2020-12/schema", + "additionalProperties": false, + "properties": { + "message": { + "type": "string" + }, + "retryable": { + "type": "boolean" + }, + "status": { + "type": "integer" + }, + "type": { + "enum": [ + "validation", + "authentication", + "payment", + "permission", + "rate_limit", + "upstream", + "timeout", + "internal" + ], + "type": "string" + } + }, + "required": [ + "type", + "status", + "retryable" + ], + "type": "object" + }, + { + "type": "null" + } + ] + }, + "request_id": { + "type": "string" + }, + "successful": { + "type": "boolean" + }, + "tool": { + "type": "string" + }, + "upstream_status": { + "description": "HTTP status returned by AIsaServices when a request was dispatched.", + "type": "integer" + } + }, + "required": [ + "call_id", + "tool", + "successful", + "request_id" + ], + "type": "object" + }, + "type": "array" + }, + "session_id": { + "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", + "maxLength": 128, + "minLength": 1, + "pattern": "^[A-Za-z0-9_-]*$", + "type": "string" + }, + "success_count": { + "minimum": 0, + "type": "integer" + }, + "total_count": { + "minimum": 1, + "type": "integer" + } +} - added
Output schema / requiredAdded value: +[ + "session_id", + "batch_id", + "total_count", + "success_count", + "error_count", + "results", + "next_steps_guidance" +]
- Changed
get_dataforseo_backlinks_index1 field changed- added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
get_details13 fields changed- added
Input schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / properties / argumentsRemoved value: -{ - "anyOf": [ - { - "additionalProperties": true, - "type": "object" - }, - { - "type": "null" - } - ], - "default": null, - "description": "The arguments the operation would be called with, for a price that reflects them. Keyed by operation_id for a batch, or passed flat for a single operation_id. Routes whose required parameters are validated before pricing have no price without them." -} - added
Input schema / properties / include_arguments_schemaAdded value: +{ + "default": true, + "description": "Return the complete arguments_schema. Defaults to true.", + "type": "boolean" +} - changed
Input schema / properties / include_documentation / descriptionPrevious value: -"Include the complete native public OpenAPI document, reference closure and scoped completeness. Existing execution schemas remain unchanged."New value: +"Return the complete immutable public OpenAPI operation, referenced declarations, provenance and scoped completeness. Documentation does not change execution support." - added
Input schema / properties / include_response_schemaAdded value: +{ + "default": false, + "description": "Return the complete response_schema. Defaults to false.", + "type": "boolean" +} - removed
Input schema / properties / operation_idRemoved value: -{ - "anyOf": [ - { - "type": "string" - }, - { - "type": "null" - } - ], - "default": null, - "description": "One operation_id from search" -} - removed
Input schema / properties / operation_idsRemoved value: -{ - "anyOf": [ - { - "items": { - "type": "string" - }, - "type": "array" - }, - { - "type": "null" - } - ], - "default": null, - "description": "Up to 20 operation_ids, for a batch" -} - added
Input schema / properties / session_idAdded value: +{ + "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", + "maxLength": 128, + "pattern": "^[A-Za-z0-9_-]*$", + "type": "string" +} - added
Input schema / properties / toolsAdded value: +{ + "description": "Exact tool names returned by search whose complete contracts are needed. Never invent tool names.", + "items": { + "minLength": 1, + "pattern": "^\\S(?:.*\\S)?$", + "type": "string" + }, + "maxItems": 20, + "minItems": 1, + "type": "array", + "uniqueItems": true +} - removed
Input schema / properties / with_quoteRemoved value: -{ - "default": true, - "description": "Whether each operation is priced for this account before the answer. One round trip per operation; spends nothing.", - "type": "boolean" -} - added
Input schema / requiredAdded value: +[ + "tools" +] - added
Output schema / propertiesAdded value: +{ + "error_count": { + "type": "integer" + }, + "next_steps_guidance": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "session_id": { + "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", + "maxLength": 128, + "minLength": 1, + "pattern": "^[A-Za-z0-9_-]{1,128}$", + "type": "string" + }, + "success_count": { + "type": "integer" + }, + "tools": { + "additionalProperties": { + "additionalProperties": false, + "properties": { + "arguments_schema": { + "additionalProperties": true, + "anyOf": [ + { + "type": "null" + }, + { + "type": "object" + } + ] + }, + "canonical_operation_id": { + "type": "string" + }, + "documentation": { + "additionalProperties": true, + "type": "object" + }, + "error": { + "additionalProperties": false, + "anyOf": [ + { + "type": "null" + }, + { + "type": "object" + } + ], + "properties": { + "code": { + "type": "string" + }, + "message": { + "type": "string" + } + }, + "required": [ + "code", + "message" + ] + }, + "execution_supported": { + "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.", + "type": "boolean" + }, + "execution_unsupported_reason": { + "description": "Why execution and quoting remain unavailable through this router.", + "type": "string" + }, + "idempotent": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "boolean" + } + ] + }, + "known_pitfalls": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "read_only": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "boolean" + } + ] + }, + "response_schema": { + "additionalProperties": true, + "anyOf": [ + { + "type": "null" + }, + { + "type": "object" + } + ] + }, + "side_effects": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "successful": { + "type": "boolean" + } + }, + "required": [ + "successful" + ], + "type": "object" + }, + "type": "object" + }, + "total_count": { + "type": "integer" + } +} - added
Output schema / requiredAdded value: +[ + "error_count", + "next_steps_guidance", + "session_id", + "success_count", + "tools", + "total_count" +]
- Changed
get_semrush_backlink_anchors4 fields changed- removed
Input schema / properties / target / descriptionRemoved value: -"Target domain or URL." - removed
Input schema / properties / target / exampleRemoved value: -"ahrefs.com" - removed
Input schema / properties / target_type / descriptionRemoved value: -"One of `root_domain`, `domain`, or `url`." - removed
Input schema / properties / target_type / exampleRemoved value: -"root_domain"
- Changed
get_semrush_backlink_competitors4 fields changed- removed
Input schema / properties / target / descriptionRemoved value: -"Target domain or URL." - removed
Input schema / properties / target / exampleRemoved value: -"ahrefs.com" - removed
Input schema / properties / target_type / descriptionRemoved value: -"One of `root_domain`, `domain`, or `url`." - removed
Input schema / properties / target_type / exampleRemoved value: -"root_domain"
- Changed
get_semrush_backlinks4 fields changed- removed
Input schema / properties / target / descriptionRemoved value: -"Target domain or URL." - removed
Input schema / properties / target / exampleRemoved value: -"ahrefs.com" - removed
Input schema / properties / target_type / descriptionRemoved value: -"One of `root_domain`, `domain`, or `url`." - removed
Input schema / properties / target_type / exampleRemoved value: -"root_domain"
- Changed
get_semrush_backlinks_overview1 field changed- removed
Input schema / properties / target / descriptionRemoved value: -"Target root domain, e.g. `ahrefs.com`."
- Changed
get_semrush_indexed_pages4 fields changed- removed
Input schema / properties / target / descriptionRemoved value: -"Target domain or URL." - removed
Input schema / properties / target / exampleRemoved value: -"ahrefs.com" - removed
Input schema / properties / target_type / descriptionRemoved value: -"One of `root_domain`, `domain`, or `url`." - removed
Input schema / properties / target_type / exampleRemoved value: -"root_domain"
- Changed
get_semrush_referring_domains4 fields changed- removed
Input schema / properties / target / descriptionRemoved value: -"Target domain or URL." - removed
Input schema / properties / target / exampleRemoved value: -"ahrefs.com" - removed
Input schema / properties / target_type / descriptionRemoved value: -"One of `root_domain`, `domain`, or `url`." - removed
Input schema / properties / target_type / exampleRemoved value: -"root_domain"
- Changed
post_dataforseo_backlinks_anchors_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "filters": [ + "anchor", + "like", + "%news%" + ], + "limit": 4, + "order_by": [ + "backlinks,desc" + ], + "target": "forbes.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "filters": [ + "anchor", + "like", + "%news%" + ], + "limit": 4, + "order_by": [ + "backlinks,desc" + ], + "target": "forbes.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get anchors for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [[\"dofollow\", \"=\", true]]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, the backlinks from subdomains of the target will be ommited and you won’t receive the same domain in the response; default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"referring_links_types.anchors\",\">\",\"1\"] [[\"broken_pages\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "limit": { - "description": "the maximum number of returned anchors optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "offset": { - "description": "offset in the results array of returned anchors optional field default value: 0 if you specify the 10 value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get anchors for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_backlinks_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "filters": [ + "dofollow", + "=", + true + ], + "limit": 5, + "mode": "as_is", + "target": "forbes.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "filters": [ + "dofollow", + "=", + true + ], + "limit": 5, + "mode": "as_is", + "target": "forbes.com" + } + ], + "properties": { + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "custom_mode": { + "additionalProperties": { + "type": [ + "object", + "null" + ] + }, + "description": "<em>detailed results grouping type</em><br>optional field<br>use this object to get a specific number of backlinks per <code>field</code><br>if you use <code>custom_mode</code>, then <code>mode</code> will be ignored<br>example:<br><code>\"custom_mode\": {\"field\": \"domain\", \"value\": 100}</code>", + "type": [ + "object", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>regex</code>, <code>not_regex</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"80\"]</code><p><code>[[\"page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"dofollow\",\"=\",true]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"text_pre\",\"like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "mode": { + "description": "<em>results grouping type</em><br>optional field<br>possible grouping types:<br><code>as_is</code> - returns all backlinks<br><code>one_per_domain</code> - returns one backlink per domain<br><code>one_per_anchor</code> - returns one backlink per anchor<p>default value: <code>as_is</code>", + "type": [ + "string", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks;<br><strong>Note:</strong> the maximum value is <code>20,000</code>, use the <code>search_after_token</code> if you would like to offset more results", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "search_after_token": { + "description": "<em>token for subsequent requests</em><br>optional field<br>provided in the identical filed of the response to each request;<br>use this parameter to avoid timeouts while trying to obtain over <code>20,000</code> results in a single request;<br>by specifying the unique <code>search_after_token</code> value from the response array, you will get the subsequent results of the initial task;<br><code>search_after_token</code> values are unique for each subsequent task ;<br><strong>Note:</strong> if the <code>search_after_token</code> is specified in the request, all other parameters should be identical to the previous request", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get backlinks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "custom_mode": { - "description": "detailed results grouping type optional field use this object to get a specific number of backlinks per field if you use custom_mode, then mode will be ignored example: \"custom_mode\": {\"field\": \"domain\", \"value\": 100}", - "properties": { - "field": { - "type": "string" - }, - "value": { - "type": "integer" - } - }, - "type": "object" - }, - "exclude_internal_backlinks": { - "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: =, , in, not_in, like, not_like, ilike, not_ilike, regex, not_regex, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"rank\",\">\",\"80\"] [[\"page_from_rank\",\">\",\"55\"], \"and\", [\"dofollow\",\"=\",true]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"text_pre\",\"like\",\"%seo%\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "limit": { - "description": "the maximum number of returned backlinks optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "mode": { - "description": "results grouping type optional field possible grouping types: as_is – returns all backlinks one_per_domain – returns one backlink per domain one_per_anchor – returns one backlink per anchor default value: as_is", - "type": "string" - }, - "offset": { - "description": "offset in the results array of the returned backlinks optional field default value: 0 if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks; Note: the maximum value is 20,000, use the search_after_token if you would like to offset more results", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"rank,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"domain_from_rank,desc\",\"page_from_rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "search_after_token": { - "description": "token for subsequent requests optional field provided in the identical filed of the response to each request; use this parameter to avoid timeouts while trying to obtain over 20,000 results in a single request; by specifying the unique search_after_token value from the response array, you will get the subsequent results of the initial task; search_after_token values are unique for each subsequent task ; Note: if the search_after_token is specified in the request, all other parameters should be identical to the previous request", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get backlinks for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_backlinks_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get the number of backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get the number of backlinks for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_new_lost_backlinks_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "date_from": "2026-08-31 11:12:35", + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "date_from": "2026-08-31 11:12:35", + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks;<br>the backlinks that appeared in our index after the specified date will be considered as new;<br>the backlinks that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get new & lost backlinks for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without `https://` and `www.` the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br> `\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "date_from": { - "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost backlinks; the backlinks that appeared in our index after the specified date will be considered as new; the backlinks that weren’t found after the specified date, but were present before, will be considered as lost; default value: today’s date -(minus) one month; e.g. if today is 2021-10-13, default date_from will be 2021-09-13. minimum value equals today’s date -(minus) one year; e.g. if today is 2021-10-13, minimum date_from will be 2020-10-13. date format: \"yyyy-mm-dd\" example: \"2021-01-01\"", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get new & lost backlinks for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_new_lost_ref_domains_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "datetime_from": "2026-12-31", + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "datetime_from": "2026-12-31", + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost referring domains;<br>the referring domains that appeared in our index after the specified date will be considered as new;<br>the referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>default value: today's date -(minus) one month;<br>e.g. if today is <code>2021-10-13</code>, default <code>date_from</code> will be <code>2021-09-13</code>.<br><strong>minimum value equals today's date -(minus) one year;</strong><br>e.g. if today is <code>2021-10-13</code>, minimum <code>date_from</code> will be <code>2020-10-13</code>.<p>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get new & lost referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "date_from": { - "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost referring domains; the referring domains that appeared in our index after the specified date will be considered as new; the referring domains that weren’t found after the specified date, but were present before, will be considered as lost; default value: today’s date -(minus) one month; e.g. if today is 2021-10-13, default date_from will be 2021-09-13. minimum value equals today’s date -(minus) one year; e.g. if today is 2021-10-13, minimum date_from will be 2020-10-13. date format: \"yyyy-mm-dd\" example: \"2021-01-01\"", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get new & lost referring domains for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_pages_summary_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "targets": [ + "https://dataforseo.com/solutions", + "https://dataforseo.com/about-us" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "targets": [ + "https://dataforseo.com/solutions", + "https://dataforseo.com/about-us" + ] + } + ], + "properties": { + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>you can specify up to 1000 pages, domains, or subdomains in each request.<br><strong>note that the URLs you set in a single request cannot belong to more than 100 different domains</strong>.", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get summary data for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://) you can specify up to 1000 pages, domains, or subdomains in each request. note that the URLs you set in a single request cannot belong to more than 100 different domains.", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_ranks_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get rank for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_referring_domains_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get the number of referring domains for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get the number of referring domains for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_bulk_spam_score_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "targets": [ + "forbes.com", + "cnn.com", + "bbc.com", + "yelp.com", + "https://www.apple.com/iphone/", + "https://ahrefs.com/blog/", + "ibm.com", + "https://variety.com/", + "https://stackoverflow.com/", + "www.trustpilot.com" + ] + } + ], + "properties": { + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "description": "<em>domains, subdomains or webpages to get <code>rank</code> for</em><br><strong>required field</strong><br>you can set up to 1000 domains, subdomains or webpages<br>the domain or subdomain should be specified without <code>https://</code> and <code>www.</code><br>the page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": [<br> \"forbes.com\",<br> \"cnn.com\",<br> \"bbc.com\",<br> \"yelp.com\",<br> \"https://www.apple.com/iphone/\",<br> \"https://ahrefs.com/blog/\",<br> \"ibm.com\",<br> \"https://variety.com/\",<br> \"https://stackoverflow.com/\",<br> \"www.trustpilot.com\"<br>]`", + "items": { + "type": "string" + }, + "type": "array" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "description": "domains, subdomains or webpages to get rank for required field you can set up to 1000 domains, subdomains or webpages the domain or subdomain should be specified without https:// and www. the page should be specified with absolute URL (including http:// or https://) example: \"targets\": [ \"forbes.com\", \"cnn.com\", \"bbc.com\", \"yelp.com\", \"https://www.apple.com/iphone/\", \"https://ahrefs.com/blog/\", \"ibm.com\", \"https://variety.com/\", \"https://stackoverflow.com/\", \"www.trustpilot.com\" ]", - "items": { - "type": "string" - }, - "type": "array" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_competitors_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "filters": [ + "rank", + ">", + 100 + ], + "limit": 5, + "order_by": [ + "rank,desc" + ], + "target": "dataforseo.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "filters": [ + "rank", + ">", + 100 + ], + "limit": 5, + "order_by": [ + "rank,desc" + ], + "target": "dataforseo.com" + } + ], + "properties": { + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "exclude_large_domains": { + "description": "<em>indicates whether large domain will appear in results</em><br>optional field<br>if set to <code>true</code>, the results from the large domain (google.com, amazon.com, etc.) will be omitted;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"rank\",\">\",\"100\"]</code><p><code>[[\"target\",\"like\",\"%forbes%\"],<br>\"and\",<br>[[\"rank\",\">\",\"100\"],\"or\",[\"intersections\",\">\",\"5\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "main_domain": { + "description": "<em>indicates if only main domain of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>true</code>, only the main domain will be included in search;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"intersections,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get competitor domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "exclude_internal_backlinks": { - "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results default value: true", - "type": "boolean" - }, - "exclude_large_domains": { - "description": "indicates whether large domain will appear in results optional field if set to true, the results from the large domain (google.com, amazon.com, etc.) will be omitted; default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"rank\",\">\",\"100\"] [[\"target\",\"like\",\"%forbes%\"], \"and\", [[\"rank\",\">\",\"100\"],\"or\",[\"intersections\",\">\",\"5\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "limit": { - "description": "the maximum number of returned domains optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "main_domain": { - "description": "indicates if only main domain of the target will be included in the search optional field if set to true, only the main domain will be included in search; default value: true", - "type": "boolean" - }, - "offset": { - "description": "offset in the results array of returned domains optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"rank,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"intersections,desc\",\"rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get competitor domains for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_domain_intersection_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "exclude_internal_backlinks": true, + "exclude_targets": [ + "semrush.com" + ], + "include_subdomains": false, + "limit": 5, + "order_by": [ + "1.backlinks,desc" + ], + "targets": { + "1": "moz.com", + "2": "ahrefs.com" + } + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "exclude_internal_backlinks": true, + "exclude_targets": [ + "semrush.com" + ], + "include_subdomains": false, + "limit": 5, + "order_by": [ + "1.backlinks,desc" + ], + "targets": { + "1": "moz.com", + "2": "ahrefs.com" + } + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be omitted and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "exclude_targets": { + "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can specify up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring domains that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"2.referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"1.backlinks\",\">\",\"10\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"2.target\",\"like\",\"%dataforseo.com%\"],\"or\",[\"1.referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "intersection_mode": { + "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified domains<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", + "type": [ + "string", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned results</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the array of returned results</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "additionalProperties": { + "type": [ + "string", + "null" + ] + }, + "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", + "type": [ + "object", + "null" + ] + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [[\"dofollow\", \"=\", true]]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your targets; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, the backlinks from subdomains of the target will be omitted and you won’t receive the same domain in the response; default value: true", - "type": "boolean" - }, - "exclude_targets": { - "description": "domains, subdomains or webpages you want to exclude optional field you can specify up to 10 domains, subdomains or webpages if you use this array, results will contain the referring domains that link to targets but don’t link to exclude_targets example: \"exclude_targets\": [ \"bbc.com\", \"https://www.apple.com/iphone/*\", \"https://dataforseo.com/apis/*\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"1.internal_links_count\",\">\",\"1\"] [[\"2.referring_pages\",\">\",\"2\"], \"and\", [\"1.backlinks\",\">\",\"10\"]] [[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"2.target\",\"like\",\"%dataforseo.com%\"],\"or\",[\"1.referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the targets will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "intersection_mode": { - "description": "indicates whether to intersect backlinks optional field use this field to intersect or merge results for the specified domains possible values: all, partial all – results are based on all backlinks; partial – results are based on the intersecting backlinks only; default value: all", - "type": "string" - }, - "limit": { - "description": "the maximum number of returned results optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "offset": { - "description": "offset in the array of returned results optional field default value: 0 if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "additionalProperties": { - "type": "string" - }, - "description": "domains, subdomains or webpages to get links for required field you can set up to 20 domains, subdomains or webpages a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://) example: \"targets\": { \"1\": \"http://planet.postgresql.org/\", \"2\": \"http://gborg.postgresql.org/\" }", - "type": "object" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_domain_pages_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "filters": [ + [ + "page_summary.backlinks", + ">", + 5 + ], + "and", + [ + "page", + "like", + "%sites%" + ] + ], + "limit": 5, + "target": "forbes.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "filters": [ + [ + "page_summary.backlinks", + ">", + 5 + ], + "and", + [ + "page", + "like", + "%sites%" + ] + ], + "limit": 5, + "target": "forbes.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"meta.internal_links_count\",\">\",\"1\"]</code><p><code>[[\"meta.external_links_count\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_visited\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"title\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned pages</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned pages</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"page_summary.backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"page_summary.backlinks,desc\",\"page_summary.rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain or subdomain</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>forbes.com</code>", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [\"dofollow\", \"=\", true]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"meta.internal_links_count\",\">\",\"1\"] [[\"meta.external_links_count\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_visited\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"title\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "limit": { - "description": "the maximum number of returned pages optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "offset": { - "description": "offset in the results array of returned pages optional field default value: 0 if you specify the 10 value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"page_summary.backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"page_summary.backlinks,desc\",\"page_summary.rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain or subdomain required field a domain or a subdomain should be specified without https:// and www. example: forbes.com", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_domain_pages_summary_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "limit": 4, + "order_by": [ + "backlinks,desc" + ], + "target": "forbes.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "limit": 4, + "order_by": [ + "backlinks,desc" + ], + "target": "forbes.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live/\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, backlinks from the subdomains of the <code>target</code> domain will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_links_types.anchors\",\">\",\"1\"]</code><p><code>[[\"broken_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> domain will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned anchors</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned anchors</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get summary data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [[\"dofollow\", \"=\", true]]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, backlinks from the subdomains of the target domain will be ommited and you won’t receive the same domain in the response; default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"referring_links_types.anchors\",\">\",\"1\"] [[\"broken_pages\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"anchor\",\"like\",\"%seo%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target domain will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "limit": { - "description": "the maximum number of returned anchors optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "offset": { - "description": "offset in the results array of returned anchors optional field default value: 0 if you specify the 10 value, the first ten anchors in the results array will be omitted and the data will be provided for the successive anchors", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get summary data for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_history_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "date_from": "2020-01-01", + "date_to": "2021-01-01", + "target": "cnn.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "date_from": "2020-01-01", + "date_to": "2021-01-01", + "target": "cnn.com" + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>minimum value <code>2019-01-01</code><br>if you don't specify this field, the minimum value will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "date_to": { + "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2019-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code>", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "date_from": { - "description": "starting date of the time range optional field minimum value 2019-01-01 if you don’t specify this field, the minimum value will be used by default date format: \"yyyy-mm-dd\" example: \"2019-01-15\"", - "type": "string" - }, - "date_to": { - "description": "ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default date format: \"yyyy-mm-dd\" example: \"2019-01-15\"", - "type": "string" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain required field a domain should be specified without https:// and www.", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_page_intersection_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "exclude_targets": [ + "skysports.com" + ], + "filters": [ + [ + "2.domain_from_rank", + ">", + 400 + ], + "and", + [ + "1.dofollow", + "=", + true + ] + ], + "limit": 5, + "order_by": [ + "1.rank,desc" + ], + "targets": { + "1": "football.com", + "2": "fifa.com" + } + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "exclude_targets": [ + "skysports.com" + ], + "filters": [ + [ + "2.domain_from_rank", + ">", + 400 + ], + "and", + [ + "1.dofollow", + "=", + true + ] + ], + "limit": 5, + "order_by": [ + "1.rank,desc" + ], + "targets": { + "1": "football.com", + "2": "fifa.com" + } + } + ], + "properties": { + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>targets</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the result<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "exclude_targets": { + "description": "<em>domains, subdomains or webpages you want to exclude</em><br>optional field<br>you can set up to 10 domains, subdomains or webpages<br>if you use this array, results will contain the referring pages that link to <code>targets</code> but don't link to <code>exclude_targets</code><br>example:<br>`\"exclude_targets\": [<br>\"bbc.com\",<br>\"https://www.apple.com/iphone/*\",<br>\"https://dataforseo.com/apis/*\"]`", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"1.rank\",\">\",\"80\"]</code><p><code>[[\"2.page_from_rank\",\">\",\"55\"],<br>\"and\",<br>[\"1.original\",\"=\",\"true\"]]</code><p><code>[[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"1.acnhor\",\"like\",\"%seo%\"],\"or\",[\"1.text_pre\",\"not_like\",\"%seo%\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>targets</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>targets</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>attributes</code><br><code>domain_from_platform_type</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "intersection_mode": { + "description": "<em>indicates whether to intersect backlinks</em><br>optional field<br>use this field to intersect or merge results for the specified URLs<br>possible values: <code>all</code>, <code>partial</code><br><code>all</code> - results are based on all backlinks;<br><code>partial</code> - results are based on the intersecting backlinks only;<br>default value: <code>all</code>", + "type": [ + "string", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned backlinks</em><br>optional field<p>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of the returned backlinks</em><br>optional field<p>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"rank,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"domain_from_rank,desc\",\"page_from_rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "targets": { + "additionalProperties": { + "type": [ + "string", + "null" + ] + }, + "description": "<em>domains, subdomains or webpages to get links for</em><br><strong>required field</strong><br>you can set up to 20 domains, subdomains or webpages<br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)<br>example:<br>`\"targets\": {<br>\"1\": \"http://planet.postgresql.org/\",<br>\"2\": \"http://gborg.postgresql.org/\"<br>}`", + "type": [ + "object", + "null" + ] + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your targets; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the result default value: true", - "type": "boolean" - }, - "exclude_targets": { - "description": "domains, subdomains or webpages you want to exclude optional field you can set up to 10 domains, subdomains or webpages if you use this array, results will contain the referring pages that link to targets but don’t link to exclude_targets example: \"exclude_targets\": [ \"bbc.com\", \"https://www.apple.com/iphone/*\", \"https://dataforseo.com/apis/*\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"1.rank\",\">\",\"80\"] [[\"2.page_from_rank\",\">\",\"55\"], \"and\", [\"1.original\",\"=\",\"true\"]] [[\"1.first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"1.acnhor\",\"like\",\"%seo%\"],\"or\",[\"1.text_pre\",\"not_like\",\"%seo%\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the targets will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the targets will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: attributes domain_from_platform_type default value: 10 maximum value: 1000", - "type": "integer" - }, - "intersection_mode": { - "description": "indicates whether to intersect backlinks optional field use this field to intersect or merge results for the specified URLs possible values: all, partial all – results are based on all backlinks; partial – results are based on the intersecting backlinks only; default value: all", - "type": "string" - }, - "limit": { - "description": "the maximum number of returned backlinks optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "offset": { - "description": "offset in the results array of the returned backlinks optional field default value: 0 if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"rank,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"domain_from_rank,desc\",\"page_from_rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "targets": { - "additionalProperties": { - "type": "string" - }, - "description": "domains, subdomains or webpages to get links for required field you can set up to 20 domains, subdomains or webpages a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://) example: \"targets\": { \"1\": \"http://planet.postgresql.org/\", \"2\": \"http://gborg.postgresql.org/\" }", - "type": "object" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "targets" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_referring_domains_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "exclude_internal_backlinks": true, + "filters": [ + "backlinks", + ">", + 100 + ], + "limit": 5, + "order_by": [ + "rank,desc" + ], + "target": "backlinko.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "exclude_internal_backlinks": true, + "filters": [ + "backlinks", + ">", + 100 + ], + "limit": 5, + "order_by": [ + "rank,desc" + ], + "target": "backlinko.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"domain\",\"like\",\"%dataforseo.com%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned domains</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned domains</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get referring domains for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [\"dofollow\", \"=\", true]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, the backlinks from subdomains of the target will be ommited and you won’t receive the same domain in the response; default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"referring_pages\",\">\",\"1\"] [[\"referring_pages\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"domain\",\"like\",\"%dataforseo.com%\"],\"or\",[\"referring_domains\",\">\",\"10\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "limit": { - "description": "the maximum number of returned domains optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "offset": { - "description": "offset in the results array of returned domains optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get referring domains for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_referring_networks_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "exclude_internal_backlinks": true, + "filters": [ + "backlinks", + ">", + 100 + ], + "limit": 5, + "network_address_type": "subnet", + "order_by": [ + "rank,desc" + ], + "target": "backlinko.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "exclude_internal_backlinks": true, + "filters": [ + "backlinks", + ">", + 100 + ], + "limit": 5, + "network_address_type": "subnet", + "order_by": [ + "rank,desc" + ], + "target": "backlinko.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [[\"dofollow\", \"=\", true]]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates whether the backlinks from subdomains of the <code>target</code> are excluded</em><br>optional field<br>if set to <code>false</code>, the backlinks from subdomains of the <code>target</code> will be ommited and you won't receive the same domain in the response;<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "filters": { + "description": "<em>array of results filtering parameters</em><br>optional field<br><strong>you can add several filters at once (8 filters maximum)</strong><br>you should set a logical operator <code>and</code>, <code>or</code> between the conditions<br>the following operators are supported:<br><code>regex</code>, <code>not_regex</code>, <code>=</code>, <code><></code>, <code>in</code>, <code>not_in</code>, <code>like</code>, <code>not_like</code>, <code>ilike</code>, <code>not_ilike</code>, <code>match</code>, <code>not_match</code><br>you can use the <code>%</code> operator with <code>like</code> and <code>not_like</code> to match any string of zero or more characters<br>example:<br><code>[\"referring_pages\",\">\",\"1\"]</code><p><code>[[\"referring_pages\",\">\",\"2\"],<br>\"and\",<br>[\"backlinks\",\">\",\"10\"]]</code><p><code>[[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"],<br>\"and\",<br>[[\"network_address\",\"like\",\"194.1.%\"],\"or\",[\"referring_ips\",\">\",\"10\"]]]</code><p>The full list of possible filters is available <a href=\"/v3/backlinks/filters/?bash\" rel=\"noopener noreferrer\" target=\"_blank\">here.</a>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "limit": { + "description": "<em>the maximum number of returned networks</em><br>optional field<br>default value: <code>100</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "network_address_type": { + "description": "<em>indicates the type of network to get data for</em><br>optional field<br>possible values: <code>ip</code>, <code>subnet</code><br>default value: <code>ip</code>", + "type": [ + "string", + "null" + ] + }, + "offset": { + "description": "<em>offset in the results array of returned networks</em><br>optional field<br>default value: <code>0</code><br>if you specify the <code>10</code> value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", + "type": [ + "integer", + "null" + ] + }, + "order_by": { + "description": "<em>results sorting rules</em><br>optional field<br>you can use the same values as in the <code>filters</code> array to sort the results<br>possible sorting types:<br><code>asc</code> - results will be sorted in the ascending order<br><code>desc</code> - results will be sorted in the descending order<br>you should use a comma to set up a sorting type<br>example:<br><code>[\"backlinks,desc\"]</code><br><strong>note that you can set no more than three sorting rules in a single request</strong><br>you should use a comma to separate several sorting rules<br>example:<br><code>[\"backlinks,desc\",\"rank,asc\"]</code>", + "items": { + "type": "string" + }, + "type": [ + "array", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get referring networks for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [[\"dofollow\", \"=\", true]]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates whether the backlinks from subdomains of the target are excluded optional field if set to false, the backlinks from subdomains of the target will be ommited and you won’t receive the same domain in the response; default value: true", - "type": "boolean" - }, - "filters": { - "description": "array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: [\"referring_pages\",\">\",\"1\"] [[\"referring_pages\",\">\",\"2\"], \"and\", [\"backlinks\",\">\",\"10\"]] [[\"first_seen\",\">\",\"2017-10-23 11:31:45 +00:00\"], \"and\", [[\"network_address\",\"like\",\"194.1.%\"],\"or\",[\"referring_ips\",\">\",\"10\"]]] The full list of possible filters is available here.", - "items": {}, - "type": "array" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "limit": { - "description": "the maximum number of returned networks optional field default value: 100 maximum value: 1000", - "type": "integer" - }, - "network_address_type": { - "description": "indicates the type of network to get data for optional field possible values: ip, subnet default value: ip", - "type": "string" - }, - "offset": { - "description": "offset in the results array of returned networks optional field default value: 0 if you specify the 10 value, the first ten domains in the results array will be omitted and the data will be provided for the successive pages", - "type": "integer" - }, - "order_by": { - "description": "results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc – results will be sorted in the ascending order desc – results will be sorted in the descending order you should use a comma to set up a sorting type example: [\"backlinks,desc\"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: [\"backlinks,desc\",\"rank,asc\"]", - "items": { - "type": "string" - }, - "type": "array" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get referring networks for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_summary_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "backlinks_status_type": "all", + "include_subdomains": true, + "internal_list_limit": 10, + "target": "explodingtopics.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "backlinks_filters": [ + "dofollow", + "=", + true + ], + "backlinks_status_type": "all", + "include_subdomains": true, + "internal_list_limit": 10, + "target": "explodingtopics.com" + } + ], + "properties": { + "backlinks_filters": { + "description": "<em>filter the backlinks of your <code>target</code></em><br>optional field<br>you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your <code>target</code><br>you can filter the backlinks by all fields available in the response of <a href=\"/v3/backlinks/backlinks/live\">this endpoint</a><br>using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for<br>example:<br><code>\"backlinks_filters\": [\"dofollow\", \"=\", true]</code>", + "items": { + "type": [ + "object", + "null" + ] + }, + "type": [ + "array", + "null" + ] + }, + "backlinks_status_type": { + "description": "<em>set what backlinks to return and count</em><br>optional field<br>you can use this field to choose what backlinks will be returned and used for aggregated metrics for your <code>target</code>;<br>possible values: <br><code>all</code> - all backlinks will be returned and counted;<br><code>live</code> - backlinks found during the last check will be returned and counted;<br><code>lost</code> - lost backlinks will be returned and counted;<p>default value: <code>live</code>", + "type": [ + "string", + "null" + ] + }, + "exclude_internal_backlinks": { + "description": "<em>indicates if internal backlinks from subdomains to the <code>target</code> will be excluded from the results</em><br>optional field<br>if set to <code>true</code>, the results will not include data on internal backlinks from subdomains of the same domain as <code>target</code><br>if set to <code>false</code>, internal links will be included in the results<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_indirect_links": { + "description": "<em>indicates if indirect links to the <code>target</code> will be included in the results</em><br>optional field<br>if set to <code>true</code>, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page<br>if set to <code>false</code>, indirect links will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "internal_list_limit": { + "description": "<em>maximum number of elements within internal arrays</em><br>optional field<br>you can use this field to limit the number of elements within the following arrays:<br><code>referring_links_tld</code><br><code>referring_links_types</code><br><code>referring_links_attributes</code><br><code>referring_links_platform_types</code><br><code>referring_links_semantic_locations</code><p>default value: <code>10</code><br>maximum value: <code>1000</code>", + "type": [ + "integer", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain, subdomain or webpage to get data for</em><br><strong>required field</strong><br>a domain or a subdomain should be specified without <code>https://</code> and <code>www.</code><br>a page should be specified with absolute URL (including <code>http://</code> or <code>https://</code>)", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "backlinks_filters": { - "description": "filter the backlinks of your target optional field you can use this field to filter the initial backlinks that will be included in the dataset for aggregated metrics for your target you can filter the backlinks by all fields available in the response of this endpoint using this parameter, you can include only dofollow backlinks in the response and create a flexible backlinks dataset to calculate the metrics for example: \"backlinks_filters\": [\"dofollow\", \"=\", true]", - "items": {}, - "type": "array" - }, - "backlinks_status_type": { - "description": "set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your target; possible values: all – all backlinks will be returned and counted; live – backlinks found during the last check will be returned and counted; lost – lost backlinks will be returned and counted; default value: live", - "type": "string" - }, - "exclude_internal_backlinks": { - "description": "indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to false, internal links will be included in the results default value: true", - "type": "boolean" - }, - "include_indirect_links": { - "description": "indicates if indirect links to the target will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to the target, or points to a canonical page if set to false, indirect links will be ignored default value: true", - "type": "boolean" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "internal_list_limit": { - "description": "maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: referring_links_tld referring_links_types referring_links_attributes referring_links_platform_types referring_links_semantic_locations default value: 10 maximum value: 1000", - "type": "integer" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain, subdomain or webpage to get data for required field a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (including http:// or https://)", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_timeseries_new_lost_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "date_from": "2021-12-01", + "date_to": "2022-02-01", + "group_range": "month", + "target": "dataforseo.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "date_from": "2021-12-01", + "date_to": "2022-02-01", + "group_range": "month", + "target": "dataforseo.com" + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains;<br>the backlinks and referring domains that appeared in our index after the specified date will be considered as new;<br>the backlinks and referring domains that weren't found after the specified date, but were present before, will be considered as lost;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "date_to": { + "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "group_range": { + "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", + "type": [ + "string", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "date_from": { - "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for new and lost backlinks and referring domains; the backlinks and referring domains that appeared in our index after the specified date will be considered as new; the backlinks and referring domains that weren’t found after the specified date, but were present before, will be considered as lost; minimum value: 2019-01-30 maximum value shouldn’t exceed the date specified in the date_to date format: \"yyyy-mm-dd\" example: \"2021-01-01\"", - "type": "string" - }, - "date_to": { - "description": "ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default minimum value shouldn’t preceed the date specified in the date_from maximum value: today’s date date format: \"yyyy-mm-dd\" example: \"2021-01-15\"", - "type": "string" - }, - "group_range": { - "description": "time range which will be used to group the results optional field default value: month possible values: day, week, month, year note: for day, we will return items corresponding to all dates between and including date_from and date_to; for week/month/year, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year for example, if you specify: \"group_range\": \"month\", \"date_from\": \"2022-03-23\", \"date_to\": \"2022-05-13\" we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: 2022-03-31, 2022-04-30, 2022-05-31 if there is no data for a certain day/week/month/year, we will return 0", - "type": "string" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain to get data for required field a domain should be specified without https:// and www. example: \"forbes.com\"", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
post_dataforseo_backlinks_timeseries_summary_live7 fields changed- added
Input schema / properties / body / exampleAdded value: +[ + { + "date_from": "2021-12-01", + "date_to": "2022-02-01", + "group_range": "month", + "target": "dataforseo.com" + } +] - added
Input schema / properties / body / items / anyOfAdded value: +[ + { + "example": [ + { + "date_from": "2021-12-01", + "date_to": "2022-02-01", + "group_range": "month", + "target": "dataforseo.com" + } + ], + "properties": { + "date_from": { + "description": "<em>starting date of the time range</em><br>optional field<br>this field indicates the date which will be used as a threshold for summary data;<p>minimum value: <code>2019-01-30</code><br>maximum value shouldn't exceed the date specified in the <code>date_to</code><br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-01\"</code>", + "type": [ + "string", + "null" + ] + }, + "date_to": { + "description": "<em>ending date of the time range</em><br>optional field<br>if you don't specify this field, the today's date will be used by default<br>minimum value shouldn't preceed the date specified in the <code>date_from</code><br>maximum value: today's date<br>date format: <code>\"yyyy-mm-dd\"</code><br>example:<br><code>\"2021-01-15\"</code>", + "type": [ + "string", + "null" + ] + }, + "group_range": { + "description": "<em>time range which will be used to group the results</em><br>optional field<br>default value: <code>month</code><br>possible values: <code>day</code>, <code>week</code>, <code>month</code>, <code>year</code><p><strong>note:</strong> for <code>day</code>, we will return items corresponding to all dates between and including <code>date_from</code> and <code>date_to</code>;<br>for <code>week</code>/<code>month</code>/<code>year</code>, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year<p>for example, if you specify: <br><code>\"group_range\": \"month\",<br>\"date_from\": \"2022-03-23\",<br>\"date_to\": \"2022-05-13\"</code><br>we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: <code>2022-03-31</code>, <code>2022-04-30</code>, <code>2022-05-31</code><p>if there is no data for a certain <code>day</code>/<code>week</code>/<code>month</code>/<code>year</code>, we will return <code>0</code>", + "type": [ + "string", + "null" + ] + }, + "include_subdomains": { + "description": "<em>indicates if the subdomains of the <code>target</code> will be included in the search</em><br>optional field<br>if set to <code>false</code>, the subdomains will be ignored<br>default value: <code>true</code>", + "type": [ + "boolean", + "null" + ] + }, + "rank_scale": { + "description": "<em>defines the scale used for calculating and displaying the <code>rank</code>, <code>domain_from_rank</code>, and <code>page_from_rank</code> values</em><br>optional field<p>you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale<p>possible values:<br><code>one_hundred</code> — rank values are displayed on a 0–100 scale<br><code>one_thousand</code> — rank values are displayed on a 0–1000 scale<p>default value: <code>one_thousand</code><p>learn more about how this parameter works and how ranking metrics are calculated in <a href=\"https://dataforseo.com/help-center/what_is_rank_in_backlinks_api#rank_scale\">this Help Center article</a>", + "type": [ + "string", + "null" + ] + }, + "tag": { + "description": "<em>user-defined task identifier</em><br>optional field<br><em>the character limit is 255</em><br>you can use this parameter to identify the task and match it with the result<br>you will find the specified <code>tag</code> value in the <code>data</code> object of the response", + "type": [ + "string", + "null" + ] + }, + "target": { + "description": "<em>domain to get data for</em><br><strong>required field</strong><br>a domain should be specified without <code>https://</code> and <code>www.</code><br>example:<br><code>\"forbes.com\"</code>", + "type": "string" + } + }, + "type": "object" + } +] - removed
Input schema / properties / body / items / propertiesRemoved value: -{ - "date_from": { - "description": "starting date of the time range optional field this field indicates the date which will be used as a threshold for summary data; minimum value: 2019-01-30 maximum value shouldn’t exceed the date specified in the date_to date format: \"yyyy-mm-dd\" example: \"2021-01-01\"", - "type": "string" - }, - "date_to": { - "description": "ending date of the time range optional field if you don’t specify this field, the today’s date will be used by default minimum value shouldn’t preceed the date specified in the date_from maximum value: today’s date date format: \"yyyy-mm-dd\" example: \"2021-01-15\"", - "type": "string" - }, - "group_range": { - "description": "time range which will be used to group the results optional field default value: month possible values: day, week, month, year note: for day, we will return items corresponding to all dates between and including date_from and date_to; for week/month/year, we will return items corresponding to full weeks/months/years, where each item will indicate the last day of the week/month/year for example, if you specify: \"group_range\": \"month\", \"date_from\": \"2022-03-23\", \"date_to\": \"2022-05-13\" we will return items falling between 2022-03-01 and 2022-05-31, namely, three items corresponding to the following dates: 2022-03-31, 2022-04-30, 2022-05-31 if there is no data for a certain day/week/month/year, we will return 0", - "type": "string" - }, - "include_subdomains": { - "description": "indicates if the subdomains of the target will be included in the search optional field if set to false, the subdomains will be ignored default value: true", - "type": "boolean" - }, - "rank_scale": { - "description": "defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional field you can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scale possible values: one_hundred — rank values are displayed on a 0–100 scale one_thousand — rank values are displayed on a 0–1000 scale default value: one_thousand learn more about how this parameter works and how ranking metrics are calculated in this Help Center article", - "type": "string" - }, - "tag": { - "description": "user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response", - "type": "string" - }, - "target": { - "description": "domain to get data for required field a domain should be specified without https:// and www. example: \"forbes.com\"", - "type": "string" - } -} - removed
Input schema / properties / body / items / requiredRemoved value: -[ - "target" -] - changed
Input schema / properties / body / items / typePrevious value: -"object"New value: +[ + "object", + "null" +] - changed
Input schema / requiredPrevious value: -[ - "body" -]New value: +[] - added
Output schema / x-fastmcp-wrap-resultAdded value: +true
- Changed
search17 fields changed- added
Input schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema" - removed
Input schema / properties / category / anyOfRemoved value: -[ - { - "enum": [ - "seo", - "finance", - "social", - "search", - "sales", - "mail" - ], - "type": "string" - }, - { - "type": "null" - } -] - removed
Input schema / properties / category / defaultRemoved value: -null - changed
Input schema / properties / category / descriptionPrevious value: -"Restrict to one category (seo, finance, social, search, sales, mail). Omit to search everything."New value: +"Restrict retrieval to one category. Omit to search everything. (AIsa-only: tool-router has no equivalent.)" - added
Input schema / properties / category / enumAdded value: +[ + "seo", + "finance", + "social", + "search", + "sales", + "mail" +] - added
Input schema / properties / category / typeAdded value: +"string" - added
Input schema / properties / known_fieldsAdded value: +{ + "additionalProperties": true, + "default": {}, + "description": "Known values such as ticker, URL, provider, or identifier that improve retrieval.", + "type": "object" +} - changed
Input schema / properties / limit / descriptionPrevious value: -"Maximum candidates, 1-10"New value: +"Maximum number of additional direct tool candidates." - added
Input schema / properties / limit / maximumAdded value: +20 - added
Input schema / properties / limit / minimumAdded value: +1 - added
Input schema / properties / provider_filtersAdded value: +{ + "default": [], + "description": "Optional exact catalog provider keys used to narrow retrieval (for example similarweb). Do not use display brands. Omit this field if the exact key is unknown.", + "items": { + "type": "string" + }, + "maxItems": 50, + "type": "array", + "uniqueItems": true +} - changed
Input schema / properties / query / descriptionPrevious value: -"What you need, in plain language, e.g. 'backlinks of a domain', 'recent tweets by a user', 'insider trades for AAPL'. English works best."New value: +"Natural-language capability or task to discover." - added
Input schema / properties / query / maxLengthAdded value: +2000 - added
Input schema / properties / query / minLengthAdded value: +1 - added
Input schema / properties / session_idAdded value: +{ + "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", + "maxLength": 128, + "pattern": "^[A-Za-z0-9_-]*$", + "type": "string" +} - added
Output schema / propertiesAdded value: +{ + "next_steps_guidance": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "plan": { + "additionalProperties": false, + "anyOf": [ + { + "type": "null" + }, + { + "type": "object" + } + ], + "properties": { + "canonical_use_case": { + "type": "string" + }, + "description": { + "type": "string" + }, + "known_pitfalls": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "plan_ref": { + "type": "string" + }, + "primary_tools": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "recommended_steps": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "related_tools": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + } + }, + "required": [ + "canonical_use_case", + "description", + "known_pitfalls", + "plan_ref", + "primary_tools", + "recommended_steps", + "related_tools" + ] + }, + "retrieval_mode": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "string" + } + ] + }, + "search_id": { + "type": "string" + }, + "session_id": { + "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.", + "maxLength": 128, + "minLength": 1, + "pattern": "^[A-Za-z0-9_-]{1,128}$", + "type": "string" + }, + "tools": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "additionalProperties": false, + "properties": { + "arguments_schema": { + "additionalProperties": true, + "anyOf": [ + { + "type": "null" + }, + { + "type": "object" + } + ] + }, + "description": { + "type": "string" + }, + "execution_supported": { + "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.", + "type": "boolean" + }, + "execution_unsupported_reason": { + "description": "Why execution and quoting remain unavailable through this router.", + "type": "string" + }, + "has_full_schema": { + "type": "boolean" + }, + "match_reasons": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "array" + } + ], + "items": { + "type": "string" + } + }, + "price": { + "additionalProperties": true, + "type": "object" + }, + "retrieval_debug": { + "additionalProperties": false, + "anyOf": [ + { + "type": "null" + }, + { + "type": "object" + } + ], + "properties": { + "fused_rank": { + "type": "integer" + }, + "fused_score": { + "type": "number" + }, + "lexical_rank": { + "type": "integer" + }, + "lexical_score": { + "type": "number" + }, + "rerank_admission_rank": { + "type": "integer" + }, + "rerank_rank": { + "type": "integer" + }, + "rerank_score": { + "anyOf": [ + { + "type": "null" + }, + { + "type": "number" + } + ] + }, + "runtime_availability": { + "type": "string" + }, + "vector_view_ranks": { + "additionalProperties": { + "type": "integer" + }, + "type": "object" + }, + "vector_view_scores": { + "additionalProperties": { + "type": "number" + }, + "type": "object" + } + }, + "required": [ + "fused_rank", + "fused_score", + "lexical_rank", + "lexical_score", + "rerank_admission_rank", + "rerank_rank", + "runtime_availability", + "vector_view_ranks", + "vector_view_scores" + ] + }, + "summary": { + "type": "string" + }, + "tool": { + "type": "string" + } + }, + "required": [ + "description", + "has_full_schema", + "price", + "summary", + "tool" + ], + "type": "object" + } + } +} - added
Output schema / requiredAdded value: +[ + "next_steps_guidance", + "search_id", + "session_id", + "tools" +]
- Changed
use1 field changed- changed
Input schema / properties / max_price_usd / descriptionPrevious value: -"Refuse the call before any spend if it would cost more than this many USD"New value: +"Refuse the call before any spend if its quoted price is above this many USD"
1 tool update
- Changed
get_details1 field changed- added
Input schema / properties / include_documentationAdded value: +{ + "default": false, + "description": "Include the complete native public OpenAPI document, reference closure and scoped completeness. Existing execution schemas remain unchanged.", + "type": "boolean" +}
32 tool updates
- First observed
batch_use - First observed
get_dataforseo_backlinks_index - First observed
get_details - First observed
get_semrush_backlink_anchors - First observed
get_semrush_backlink_competitors - First observed
get_semrush_backlinks - First observed
get_semrush_backlinks_overview - First observed
get_semrush_indexed_pages - First observed
get_semrush_referring_domains - First observed
list_categories - First observed
post_dataforseo_backlinks_anchors_live - First observed
post_dataforseo_backlinks_backlinks_live - First observed
post_dataforseo_backlinks_bulk_backlinks_live - First observed
post_dataforseo_backlinks_bulk_new_lost_backlinks_live - First observed
post_dataforseo_backlinks_bulk_new_lost_ref_domains_live - First observed
post_dataforseo_backlinks_bulk_pages_summary_live - First observed
post_dataforseo_backlinks_bulk_ranks_live - First observed
post_dataforseo_backlinks_bulk_referring_domains_live - First observed
post_dataforseo_backlinks_bulk_spam_score_live - First observed
post_dataforseo_backlinks_competitors_live - First observed
post_dataforseo_backlinks_domain_intersection_live - First observed
post_dataforseo_backlinks_domain_pages_live - First observed
post_dataforseo_backlinks_domain_pages_summary_live - First observed
post_dataforseo_backlinks_history_live - First observed
post_dataforseo_backlinks_page_intersection_live - First observed
post_dataforseo_backlinks_referring_domains_live - First observed
post_dataforseo_backlinks_referring_networks_live - First observed
post_dataforseo_backlinks_summary_live - First observed
post_dataforseo_backlinks_timeseries_new_lost_live - First observed
post_dataforseo_backlinks_timeseries_summary_live - First observed
search - First observed
use
Publisher details
- Operator
- AIsa · Publisher source
- Operator website
- https://aisa.one
- Vendor relationship
- Independent
- Documentation
- https://mcp.aisa.one/servers
- Trust center
- Not available
- Restrictions
- No paid plan, admin approval, regional limit or custom OAuth app is needed to connect. Sign-in is OAuth against auth.aisa.one with dynamic client registration (RFC 7591), or an Authorization: Bearer AIsa API key. search, get_details and list_categories are free. use and batch_use are billed per call to the caller's own AIsa key, and max_price_usd refuses anything above a cap before any spend. Some operations are subscription-only on the gateway and answer 402 without the Hive GTM Growth plan.
Related MCP Connectors
Your agent needs the derived numbers — domain authority, what a site ranks for, related and relevant keywords, search intent, and who the real competitors are — for Google, Amazon and the app stores. **What you can ask for** • "What is this domain's authority, and how has its rank history moved?" • "Which keywords does this site rank for, and with what intent?" • "Who are this domain's organic competitors, and where do we overlap?" • "Which keywords does this Amazon product rank for?" • "Compare these two domains keyword by keyword." **How to use it** Point any MCP client at https://mcp.aisa.one/seo-labs/mcp and sign in with OAuth — there is no key to create or paste. 46 tools: ranked, related and relevant keywords, keyword ideas and intent, domain authority and rank history, competitor and intersection analysis, bulk metrics, plus the same shapes for Amazon products and Apple and Google Play apps. **Why this rather than the source** Ahrefs domain rating, Semrush rank history and DataForSEO Labs answering the same questions side by side. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Size the competitor here, then ask the same agent for their traffic mix or their contacts — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
Your agent needs the whole search picture — what you rank for, who outranks you, who links to them, what is broken on the site, and whether ChatGPT names you at all. Normally that is three SEO vendors and three subscriptions. **What you can ask for** • "What does this domain rank for, and which competitors take the same keywords?" • "Who links to my competitor and not to me?" • "Crawl this site and list the pages with broken tags or duplicate content." • "Does Perplexity cite us when asked about this category?" • "How hard is this keyword, and what does the SERP look like today?" **How to use it** Point any MCP client at https://mcp.aisa.one/seo/mcp and sign in with OAuth — there is no key to create or paste. 60 tools spanning DataForSEO, Semrush and Ahrefs: SERPs, keywords and difficulty, backlinks and referring domains, on-page crawling, domain authority, and answers from ChatGPT, Claude, Gemini and Perplexity. **Why this rather than the source** Three indexes behind one account, so you can cross-check a number instead of trusting one vendor's version of it. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Check the ranking here, then ask the same agent for that competitor's traffic mix, its ad spend, or the person to email — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** Narrower endpoints: https://mcp.aisa.one/seo-serp/mcp · /seo-keywords/mcp · /seo-backlinks/mcp · /seo-onpage/mcp · /seo-labs/mcp · /seo-ai-visibility/mcp · /seo-content/mcp · /seo-domains/mcp · /seo-business/mcp · /seo-merchant/mcp · /seo-apps/mcp · /seo-serp-other-engines/mcp
Your agent needs to know what people actually search — volume, ideas, how hard the term is, and whether interest is rising or was a spike last March. **What you can ask for** • "What is the monthly volume and difficulty for these 200 keywords?" • "Give me keyword ideas around this seed, with questions people ask." • "Which keywords does this competitor rank for that we do not?" • "Is interest in this term growing, and where?" • "What does this page already rank for?" **How to use it** Point any MCP client at https://mcp.aisa.one/seo-keywords/mcp and sign in with OAuth — there is no key to create or paste. 49 tools: Google and Bing volume and suggestions, keywords for a site or a URL, clickstream volumes, Google Trends and Ads traffic estimates, plus Semrush difficulty, question keywords, broad match and paid keywords, and Similarweb's keyword and landing page sets. **Why this rather than the source** Three sources for the same number, so a suspicious volume can be checked rather than believed. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Size the demand here, then ask the same agent who ranks for it and who links to them — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
Your agent needs marketplace data — what a product costs on Amazon and Google Shopping, who the sellers are, what reviewers actually complain about. **What you can ask for** • "What is this ASIN's price history, rating and seller list?" • "Who else sells this product, and at what price?" • "Pull the reviews for this product and group the complaints." • "What comes up on Google Shopping for this query in the UK?" • "Compare these products across both marketplaces." **How to use it** Point any MCP client at https://mcp.aisa.one/seo-merchant/mcp and sign in with OAuth — there is no key to create or paste. 22 tools: Amazon products, ASIN detail and sellers; Google Shopping products, product info, sellers and reviews; live and queued forms, with raw HTML where you need it. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Price the product here, then ask the same agent what the brand's site traffic or ad spend looks like — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
Related MCP Servers
- AlicenseAqualityAmaintenanceThe MCP server for SEO. Find prospects, draft outreach, and monitor backlinks from your AI agent.14MIT
- AlicenseAqualityBmaintenanceMCP server for the CrawlGraph backlink-intelligence API. Gives any MCP client - Claude Desktop, Claude Code, Cursor, Cline, Zed, Windsurf - backlink lookups and competitor gap analysis built on the public Common Crawl webgraph (4.4B edges, 120M domains).410 npm6MIT
- AlicenseAqualityDmaintenanceFind backlink opportunities, analyze competitors, discover similar domains with AI embeddings, and manage prospecting projects directly from any MCP client.15MIT
- AlicenseNot gradedqualityFmaintenanceClassic SEO suites charge heavily for link indexes. This MCP gives individuals and agencies a free, automatable path to: surface pages that mention a brand (linked or not), narrow guest-post and resource-page angles, see who links to competitors, verify whether a page links to you, and pull contact signals for outreach—all orchestrated by Claude or Cursor through typed tools instead of brittle copMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.