dataforseo-merchant-api_skill

This skill helps monitor marketplace prices, track sellers, and fetch product insights using DataForSEO Merchant API for competitive intelligence.

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill leonardo-picciani/dataforseo-agent-skills --skill dataforseo-merchant-api

  • SKILL.md5.0 KB

Overview

This skill collects marketplace and product intelligence using the DataForSEO Merchant API to support price monitoring, product research, and seller analysis. It provides task-based and live retrieval modes, returning normalized summaries plus raw payloads for debugging. Use it to pull Google Shopping and Amazon marketplace data, reviews, and seller-level metrics.

How this skill works

The skill either issues live queries or creates task-based jobs (task_post → tasks_ready → task_get) depending on volume and latency needs. It authenticates with HTTP Basic (login:password), validates top-level status_code and each task status, stores tasks[].id for resumption, and prefers postback/pingback webhooks over polling when available. Results are normalized into concise summaries and the raw API response is included for troubleshooting.

When to use it

  • Monitor competitor prices and price changes across marketplaces on a schedule
  • Research product availability, attributes, and listings for assortment planning
  • Analyze seller competition, seller counts, and reseller activity over time
  • Fetch and track product reviews and reputation signals at the SKU level
  • Pull Google Shopping or Amazon product feeds for visibility and benchmarking

Best practices

  • Choose live mode for single interactive queries and task-based mode for high-volume or scheduled jobs
  • Always include location and language where required by the source to avoid incomplete results
  • Store tasks[].id and use tasks_ready + task_get or webhooks to reliably resume jobs
  • Validate status_code == 20000 and surface status_message for any failures
  • Return both a normalized summary for decision-making and the raw payload for debugging

Example use cases

  • Weekly price-monitoring job that posts product tasks and polls tasks_ready to collect price deltas
  • One-off Google Shopping query to compare our visibility vs top competitors for a search query
  • Daily Amazon ASIN extraction to populate SKU attributes and detect listing changes
  • Seller analysis report that aggregates seller presence, counts, and top listings across a category
  • Review trend detector that fetches recent reviews and summarizes recurring complaints

FAQ

It uses HTTP Basic Auth with your DataForSEO login and password (Authorization: Basic base64(login:password)).

Should I poll or use webhooks for task-based jobs?

Prefer postback_url/pingback_url webhooks when available; otherwise poll tasks_ready and then fetch results with task_get, storing tasks[].id to resume.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
dataforseo-merchant-api skill by leonardo-picciani/dataforseo-agent-skills | VeilStrat