SShortSingh.
Back to feed

Developer Builds Node.js Workaround for eBay's Missing Sold Listings API

0
·2 views

eBay's public Browse API only returns active listings, leaving developers without access to actual transaction prices paid by buyers. The author, who owns a third-party service called CompSniper, demonstrates how to retrieve completed sold listings using a single GET request in Node.js 20 or newer. The tutorial covers filtering by marketplace, item condition, and price range across eight supported eBay regional sites including the US, UK, and Germany. It also addresses error handling, distinguishing between temporary rate limits and quota exhaustion to avoid unnecessary retry loops. A free tier offering 100 monthly requests is available for developers who want to test the integration against live sold-listing data.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

OpenAI's GPT-6 Astra Rated 'Critical' for Cyber Risk as Prompt Injection Threat Persists

OpenAI launched GPT-6 Astra on September 3, 2026, marking it as the first of its models to reach the 'Critical' cybersecurity capability level under the company's own Preparedness Framework, meaning it can autonomously discover and exploit unknown security flaws across hardened systems. The model's system card, citing external evaluations, reports a prompt-injection attack success rate of 8.5%, down from 27% for its predecessor Sol, though security researchers note that improvement is not the same as elimination of the threat. At scale, even an 8.5% success rate across thousands of daily tool-using agent sessions — where attacker-controlled text can enter via uploaded files, emails, or third-party APIs — translates into a meaningful real-world risk. Third-party evaluator Artificial Analysis ranks Astra 14th among 202 tracked models with an Intelligence Index of 60, offering a more measured view than OpenAI's own benchmark figures. Developers building agentic systems are being urged to treat prompt injection as a structural architecture problem rather than a model-level issue, since no lab has yet published a complete fix for the vulnerability class.

0
ProgrammingHacker News ·

Study of 17,000 AI Coding Agent Runs Reveals Tool Preferences of Claude, Codex and Cursor

A study conducted by Armature Tech analyzed approximately 17,000 runs across three major AI coding agents — Claude, Codex, and Cursor — to determine which tools each system prefers to install and use. The research aimed to provide empirical data on the real-world behavior of these agents during coding tasks. Findings were published on the Armature Tech blog, offering developers insight into the default tendencies of popular AI coding tools. Such data can help engineering teams make more informed decisions when choosing or configuring AI-assisted development environments.

0
ProgrammingDEV Community ·

Developer releases fetch-sentinel alpha to block prompt injection in AI web agents

A developer has published fetch-sentinel v0.1-alpha, an open-source, CPU-only local firewall designed to protect AI agent context windows from indirect prompt injection attacks during web fetches. The tool intercepts external web content before it reaches a large language model's context, separating data from potential malicious instructions using four mandatory layers including isolated fetching, structural detection, privilege separation, and signed traceability. The project is backed by 161 passing tests and uses only standard library dependencies plus two lightweight packages, with no native dependencies. The release is explicitly presented as an alpha repository, not production-ready, as an independent audit identified two unresolved structural vulnerabilities — KI-10 and KI-11 — that require a major refactor before the codebase can be considered stable. The tool is licensed under AGPL-3.0 and targets a known attack surface where adversaries embed hidden instructions in HTML comments, Unicode codepoints, or manipulated metadata to hijack autonomous AI agents.

0
ProgrammingDEV Community ·

Flutter Release Build Silently Blanks Widgets Where Debug Mode Would Throw an Error

A Flutter web developer discovered a critical layout bug after deploying eight card and casino games to Firebase Hosting in a single commit, where a roulette betting grid rendered as a completely blank space on the live site. The cause was a single line — CrossAxisAlignment.stretch on a Row nested inside a horizontal SingleChildScrollView — which violates Flutter's layout constraints. In debug mode, the framework throws a clear, descriptive error for this violation, but release builds strip out those assertions entirely, causing the framework to compute with infinite dimensions and paint nothing. With CanvasKit rendering, there is no DOM to inspect, no console error, and no widget inspector available in release mode, leaving developers with only a screenshot and an empty browser console to diagnose the issue. The developer now advocates for mandatory release-mode verification as part of deployment discipline, since static analysis tools cannot detect layout contract violations of this kind.