Skip to content
ScrapeField

14–20 September 2026

What changed that week, dated, in the order it happened.

  1. API

    Async jobs, signed webhooks and an MCP server

    curl -X POST https://api.scrapefield.com/v1/jobs \
      -H "Authorization: Bearer $SCRAPEFIELD_KEY" \
      -d '{"endpoint":"tiktok/profile","inputs":[{"username":"a"},{"username":"b"}]}'

    New

    • POST /v1/jobs runs up to 10,000 inputs of one endpoint. Credits are reserved up front and every failed input is refunded as it fails.
    • Results come back as NDJSON in the order you sent the inputs, one line per input, so a half-failed run is still a usable file.
    • Webhooks on completion, signed with HMAC-SHA256 over the timestamp and body, and retried.
    • An MCP server with every endpoint as a tool. Without a key it answers in demo mode, so an agent can try it before anyone signs up.
  2. API

    Eighteen endpoints, one schema

    curl "https://api.scrapefield.com/v1/google-maps/places?query=coffee+in+Brooklyn&demo=true"

    New

    • Eighteen endpoints across Google Maps, LinkedIn, Instagram and TikTok, every one a GET with query parameters.
    • One response shape on every surface. Platform-specific extras live in platform_fields and are never required.
    • A published credit cost per endpoint, in the docs, the OpenAPI spec and every response.
    • A usage ledger: one row per call, and a failed call reversed as a row of its own.
    • Add demo=true to any endpoint to try it with no key and no account.

The weeks around it