DataBlue
// Changelog

What We Shipped.

Product notes written for users: what changed, why it matters, and where it helps when you are testing or integrating DataBlue APIs.

DashboardNEW

Scraper Pool now shows runnable API context

The dashboard now helps users understand and run each Data API without jumping back and forth between pages.

  • Each API page shows the live endpoint weight from the catalog before a request is run.
  • A cURL command is generated from the current form values so users can copy the exact request they are testing.
  • The docs link stays available for deeper reference, while the dashboard keeps the common run path close to the form.
CreditsIMPROVED

Cleaner credit language across product surfaces

Pricing, docs, and dashboard copy now avoid blanket credit claims and point users toward endpoint-specific weights.

  • Removed broad "1 request = 1 credit" messaging where endpoint weights can differ.
  • Credit wording now explains that usage is based on the selected API and the live catalog weight.
  • Google SERP Lite and Advanced copy was separated so users can see the cost difference before choosing a mode.
RunnerFIXED

API result viewer made easier to inspect

The runner output is focused on the response users need to evaluate, copy, and compare after each request.

  • JSON responses open in a readable tree view instead of forcing users through a raw blob first.
  • Copy stays available on the result so successful responses can move directly into debugging or integration work.
  • The full-result detour was removed from the compact runner because the response is already visible in place.
DocsNEW

Docs navigation cleaned up for API users

The API reference now puts navigation, brand context, and endpoint pages in a simpler flow.

  • The docs sidebar was tightened so the product logo, sections, and endpoint links take less attention away from the content.
  • The main docs header keeps the back-to-site action in one place instead of duplicating it in the sidebar.
  • Endpoint pages were cleaned to focus on stable facts, request examples, response shape, and billing notes.
CatalogIMPROVED

Data API catalog grouped by real user tasks

The catalog is organized around the way teams search, compare, and collect web data.

  • Google, e-commerce, quick commerce, ads, apps, and social APIs are grouped in the dashboard catalog.
  • API pages use constrained fields where possible so users do not have to guess valid countries, modes, or result limits.
  • Docs and dashboard labels now use the same endpoint names so users can move between testing and reference without translation.

Older entries archived in our GitHub history.