Public Json Normalizer avatar

Public Json Normalizer

Pricing

$0.01 / actor start

Go to Apify Store
Public Json Normalizer

Public Json Normalizer

Pricing

$0.01 / actor start

Rating

0.0

(0)

Developer

Eichan Jolly

Eichan Jolly

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Categories

Features

Limited permissions

Share

Public JSON Endpoint Normalizer

What it does

Download one public JSON URL, turn its top-level JSON object or list of objects into clean Apify Dataset rows, and flatten nested objects using dot-separated keys. A small maxItems setting prevents accidental huge datasets. No login, API key, or Apify SDK.

Who it is for

Anyone who needs a repeatable snapshot from a public JSON API for CSV exports, dashboards, automation, or scheduled public-data tracking.

Input example (real public test API)

{
"url": "https://jsonplaceholder.typicode.com/users",
"maxItems": 3
}

The prefilled /users endpoint is a public JSONPlaceholder sample response containing a top-level list of 10 user objects; the example emits just 3 dataset records. url is required; maxItems defaults to 3 and accepts 1–100.

Output example (one sample row; output contains more keys)

{
"sourceUrl": "https://jsonplaceholder.typicode.com/users",
"recordIndex": 1,
"checkedAt": "2026-11-01T05:05:10Z",
"record.id": 1,
"record.name": "Leanne Graham",
"record.username": "Bret",
"record.address.street": "Kulas Light",
"record.address.city": "Gwenborough",
"record.address.geo.lat": "-37.3159",
"record.company.name": "Romaguera-Crona"
}

All leaf keys are placed at the row's top level under record.* (e.g. record.address.city). sourceUrl, recordIndex (1-based index within returned rows), and checkedAt (ISO 8601 UTC) are stable metadata fields. Lists nested inside objects remain JSON arrays; empty objects remain {}. When the JSON root is an object, exactly one row is produced. An empty array produces zero rows.

Use in Apify

  1. Create an Actor from this folder; .actor/actor.json points to the correct Dockerfile, README, and input schema.
  2. Supply the direct URL of an openly accessible JSON endpoint; one working example is prefilled.
  3. Choose a row cap (3 initially). Run and export the Dataset as CSV or JSON.
  4. Schedule a daily snapshot of a stable public JSON endpoint. Each run produces a new snapshot; no previous-run deduplication or stored history is built in.

Local run / tests

Requires Python 3.12 or newer. From the Actor folder:

ACTOR_INPUT_JSON='{"url":"https://jsonplaceholder.typicode.com/users","maxItems":3}' python src/main.py
python -m unittest discover -s tests -p 'test_*.py' -v
python tests/smoke_run.py

Local output is in storage/datasets/default/*.json (or APIFY_LOCAL_STORAGE_DIR). Apify cloud automatically supplies a runtime token and default storage IDs, used directly through Apify's REST API without installing its SDK. No external key is required.

Limits and error behavior

  • Only public HTTP(S) endpoints that respond with JSON. No authentication, HTML scraping, JavaScript rendering, or multi-page API pagination.
  • GET request timeout: 15 seconds. Response cap: 1 MB. Up to 100 rows are saved; the response is still downloaded in full within 1 MB before applying maxItems.
  • The top-level value must be an object or an array of objects. A top-level scalar or a list containing scalars within the selected rows fails with a clear error.
  • Nesting in objects is limited to 20 levels. Object keys containing a period (.) or empty keys are rejected to avoid ambiguous flattened columns; nested arrays remain arrays.
  • Unauthenticated endpoints can still rate-limit, change schemas, or block requests. Only use sources that permit automated access.
  • URLs with credentials, private/loopback IP destinations, nonstandard ports, or redirects to such destinations are refused (except an explicit local-only test fixture; never allowed in cloud). DNS rebinding during a request is not fully preventable by application-level validation alone; deploy only with a restricted egress policy for stronger network isolation.
  • Malformed HTTP responses, invalid JSON, and HTML pages returned instead of JSON produce plain-language errors without tracebacks.
  • External DNS was blocked in the verification environment, so smoke evidence uses a local fixture, not a live public request. Apify cloud build/run remains unverified.

Store placement and suggested pricing

Store categories: AUTOMATION, DEVELOPER_TOOLS. Suggested price: US $0.005 per run (advisory; no billing configured). See store_metadata.json.