Validate NDJSON

Overview

You send NDJSON text, or a reference to a file of it, and we read every non-blank line as its own JSON value. Anything that will not parse, or that turns out to be an array rather than a record, is reported with the line it sits on. Hand us a JSON Schema as well and we check every record against it in the 2020-12 dialect, so one bad row out of a hundred thousand is easy to find. Each record must be on a single line; a pretty-printed document spread over many lines is not NDJSON.

Logs, exports, and streaming APIs all speak NDJSON, and a whole-file parse tells you only that something somewhere is broken. Line-scoped checking tells you which record to fix.

When to use it

Scope

Non-goals

• We never repair or rewrite a record — that is schema.repair_json
• We never pull in another document, so send a self-contained schema
• We never treat a multi-line document as one value; that is schema.validate_json

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

File limits

Constraints this skill applies to your input and generated files. The “Limited by” column shows the static source of each cap; none of these can be raised by upgrading your plan.

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"schema.validate_ndjson","input":{"content":"{\"id\":1}\n{\"id\":2}\n"}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("schema.validate_ndjson", {"content":"{\"id\":1}\n{\"id\":2}\n"});

Errors

Other limits

Limitations

• We never repair or rewrite a record — that is schema.repair_json
• We never pull in another document, so send a self-contained schema
• We never treat a multi-line document as one value; that is schema.validate_json
• A single pretty-printed JSON document (schema.validate_json)
• Records that legitimately span several lines

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "schema.validate_ndjson",
  "input": {
    "content": "{\"id\":1}\n{\"id\":2}\n"
  }
}

Examples

{
  "content": "{\"id\":1}\n{\"id\":2}\n"
}

{
  "errorCount": 0,
  "valid": true,
  "recordCount": 2,
  "errors": [],
  "schemaValidated": false
}

{
  "content": "{\"id\":1}\nnot-json\n"
}

{
  "errorCount": 1,
  "valid": false,
  "recordCount": 2,
  "errors": [
    {
      "code": "PARSE_ERROR",
      "line": 2,
      "message": "Invalid JSON on line."
    }
  ],
  "schemaValidated": false
}

Recommended use cases

• Check a log or export file before you load it anywhere
• Preflight a streaming payload one record at a time
• Find the handful of bad rows in a large generated file

Avoid for

• A single pretty-printed JSON document (schema.validate_json)
• Records that legitimately span several lines

Related skills

Composable with

Safety & privacy

• Runs without calling any external service.
• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags