#json

Convert between .env (dotenv) files and JSON, in both directions. The parse endpoint reads .env text into a clean JSON object: it skips blank lines and # comments, honours an optional leading export, unquotes single- and double-quoted values (interpreting \n, \t and \" escapes inside double quotes), strips inline comments after unquoted values, supports values that span several lines inside quotes, and can optionally expand ${VAR} and $VAR references against the variables already defined earlier in the same file — while leaving single-quoted values strictly literal. The stringify endpoint turns a JSON object back into a valid .env file, quoting only the values that actually need it and optionally prefixing every line with export for shell sourcing. Everything is computed locally and deterministically, so it is instant and private — your secrets never leave the request. Ideal for config tooling and migrations, CI/CD pipelines, converting .env to JSON for apps that want structured config (and back), and validating environment files. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This handles the dotenv format; for INI files with [sections] use an INI API, and for YAML or TOML use those APIs.

api.oanor.com/dotenv-api

Deep-merge JSON objects — the operation every config and settings system needs. The merge endpoint recursively merges two objects (the second overrides the first), or a whole list of objects merged left-to-right, combining nested objects key by key rather than replacing them wholesale, with a choice of array strategy: replace (default), concat, union (concatenate and de-duplicate) or merge_index (merge element by element). A null in the overriding object can either overwrite the existing value or be ignored, so you can patch only the fields you mean to. The defaults endpoint is the inverse and just as useful: it fills in only the keys your data is missing from a defaults object, so your existing values always win — exactly how you layer a user's settings over default configuration. Everything is computed locally and deterministically, with no schema required. Ideal for configuration and feature-flag layering, settings and preference merges, combining API responses or partial updates, environment overrides, and template defaults. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This merges documents; to diff or patch them (RFC 6902) use a JSON-diff API, to flatten them use a flatten API, and to address values use a JSON-Pointer API.

api.oanor.com/jsonmerge-api

Render tabular data as an HTML table, and parse an HTML table back into data. The render endpoint turns a JSON array (of objects, or of arrays) or CSV into a clean, semantic <table> with <thead>/<tbody>, an optional caption and CSS class — every cell HTML-escaped so it is safe to embed. The parse endpoint does the reverse: give it any HTML containing a table and get back the headers, the rows and a ready-to-use JSON array of objects, with entities decoded and tags stripped from each cell. Perfect for emails and reports, dashboards and admin screens, and scraping or migrating tabular content. Pure local computation — no key, no third-party service, instant; up to 2 MB via POST. Live, nothing stored. 3 endpoints. Distinct from Markdown/ASCII table rendering and from generic HTML extraction.

api.oanor.com/htmltable-api

Work with NDJSON / JSON Lines — the one-JSON-value-per-line format used by application and audit logs, streaming and LLM responses, jq, BigQuery, Elasticsearch bulk and many data pipelines. The to-array endpoint parses an NDJSON stream into a regular JSON array; to-ndjson does the reverse, turning a JSON array into NDJSON (one compact value per line); and validate checks every line independently, reporting which lines are valid and the exact parse error for any that are not. Blank lines are ignored. Perfect for log processing, ETL, data import/export and stream debugging. Pure local computation — no key, no third-party service, instant; up to 4 MB via POST. Live, nothing stored. 4 endpoints. Distinct from JSON validation/formatting and from CSV tooling.

api.oanor.com/ndjson-api

Address values inside a JSON document by JSON Pointer (RFC 6901) — the /a/b/0 path syntax used by JSON Patch (RFC 6902), JSON Schema and OpenAPI $ref. The get endpoint resolves the value at a pointer (and tells you whether it exists); set writes a value at a pointer and returns the modified document (use - as the final array token to append); and list enumerates every pointer in a document, optionally only the leaf values. Token escaping (~0 for ~, ~1 for /) is handled for you. Perfect for surgically reading and patching deep JSON, building config and form tooling, and walking API responses. Pure local computation — no key, no third-party service, instant; up to 2 MB via POST. Live, nothing stored. 4 endpoints. Distinct from JSONPath querying, JSON diff/patch and dot-notation flattening.

api.oanor.com/jsonpointer-api

Convert between INI configuration files and JSON, in both directions. The parse endpoint reads INI text — sections ([section]), nested sections ([database.replica]), key=value pairs, comments and repeated keys (arrays) — into a clean JSON object; the stringify endpoint turns a JSON object back into a properly formatted INI file. INI is the config format used by Git (.gitconfig), PHP (php.ini), systemd units, desktop entries, tox/setup.cfg, many CLI tools and Windows software. Perfect for editing config programmatically, migrating settings between formats, and reading config in environments that only speak JSON. Pure local computation — no key, no third-party service, instant; send large files via POST. Live, nothing stored. 3 endpoints. Complements the YAML, TOML, CSV and XML converters and is distinct from each.

api.oanor.com/ini-api

Flatten and unflatten JSON. Turn a deeply nested JSON object into a single-level map of dot-notation keys (a.b.c → value, arrays become a.0, a.1), and turn a flat dot-notation map back into the original nested structure. Choose the delimiter (dot, slash, anything), limit the depth, or keep arrays intact. Perfect for environment variables, i18n/translation keys, preparing JSON for CSV or spreadsheet export, analytics event properties, config diffing and form serialisation. Pure local processing — no key, no third-party service, instant. Live. 3 endpoints. Distinct from JSON validation/formatting, JSONPath querying and type inference.

api.oanor.com/flatten-api

Convert and validate TOML — the config format behind Cargo.toml, pyproject.toml, Netlify and many tools. Turn TOML into JSON, turn JSON back into clean spec-compliant TOML 1.0, and validate any TOML with a precise error message (line and column) when it is malformed. Tables, arrays of tables, inline tables, typed values and datetimes are all handled. Input via the query string or the request body (up to 4 MB). Pure local processing — no key, no third-party service, instant. Live. 4 endpoints. Completes the oanor config-format family alongside the JSON, YAML, XML and CSV APIs — built for build tooling, config editors, CI and data pipelines.

api.oanor.com/toml-api

Infer a schema or types from a sample JSON document — the fastest way to get a contract out of an example API response. Pass a JSON sample and the schema endpoint returns a JSON Schema (Draft 2020-12) with detected types, required keys, array item schemas merged across elements, and recognised string formats (email, uri, uuid, date-time, date, ipv4); the typescript endpoint returns ready-to-paste TypeScript interfaces with named nested interfaces, typed arrays, unions for mixed-shape array elements and structural de-duplication. Supply the sample inline via ?json=, as a query parameter, or as a request body. Everything is computed locally with no network calls, so it is fast and deterministic. Built for scaffolding types from real API responses, generating validation schemas, documentation, contract testing and code generation. A JSON type/schema inferer — distinct from JSON-Schema validation (jsonschema), JSON pretty-printing and conversion (json), and JSON diff/patch (jsondiff). No upstream key, no cache.

api.oanor.com/jsontypes-api

Compare and patch JSON documents to RFC standards. Pass two documents and the service returns whether they are equal, an RFC 6902 JSON Patch (the precise add/remove/replace operations that turn the first into the second, using RFC 6901 JSON-Pointer paths), a change summary, and an RFC 7386 JSON Merge Patch. The patch endpoint goes the other way: apply an RFC 6902 patch (add, remove, replace, move, copy and test operations) or an RFC 7386 merge patch to a document and get the result. Documents can be sent inline or as a JSON body. Everything is computed locally with no network calls, so it is fast and deterministic. Built for configuration and state management, API change detection, audit trails and change logs, optimistic-concurrency checks and data-sync pipelines. A JSON diff/patch engine — distinct from text diffing (textdiff), JSONPath querying (jsonpath), JSON validation and pretty-printing (json) and JSON-Schema validation (jsonschema). No upstream key, no cache.

api.oanor.com/jsondiff-api

Query and extract from JSON with JSONPath, server-side. Run any JSONPath expression — wildcards, recursive descent, array slices and filter expressions like [?(@.price>10)] — against a JSON document and get back the matched values, the normalized paths and JSON Pointers of every match, or just the first match. Filter expressions are evaluated in a safe sandbox with no access to globals, and inputs can be sent as a JSON POST body or a query parameter. Pure local compute with no third-party upstream, so responses are instant and the service is always available. Ideal for no-code and automation platforms, ETL and data pipelines, API integrations, testing and config extraction.

api.oanor.com/jsonpath-api

Convert, validate and tidy YAML through a fast, fully-local API. Turn YAML into JSON (including multi-document streams) or JSON into clean YAML with optional key sorting and custom indentation, validate a document and get the exact line and column of any syntax error with a context snippet, or reformat and normalize existing YAML. Inputs can be sent as a raw text/plain body, a JSON field or a query parameter; outputs are tidy JSON. Pure server-side compute with no third-party upstream, so responses are instant and the service is always available. Ideal for DevOps and CI/CD, configuration and infrastructure-as-code tooling, no-code platforms, editors and data pipelines.

api.oanor.com/yaml-api

Validate JSON against JSON Schema, server-side. Check any data against a schema (Draft-07 or 2020-12) and get a clear pass/fail plus a detailed list of every error with its instance path, failing keyword and message; verify that a schema itself is well-formed; or infer a starter JSON Schema automatically from a sample document, complete with detected formats like email, URI and date. Built on the battle-tested Ajv engine with full format validation. Every endpoint accepts GET (JSON-encoded parameters) or a JSON POST body and runs entirely locally with no third-party upstream, so responses are instant and the service is always available. Ideal for API request/response validation, form and data-entry checks, ETL and data-quality pipelines, no-code platforms and contract testing.

api.oanor.com/jsonschema-api

A fast, fully-local XML toolkit: convert XML to JSON and JSON to XML with configurable attribute handling, validate XML well-formedness with line and column error details, and pretty-print XML while preserving element order. Every endpoint accepts input via the query string or the request body, up to 2 MB. Pure server-side compute, no third-party upstream, so responses are instant and always available. Ideal for system integrations, SOAP and legacy interop, RSS and sitemap processing, config tooling and data pipelines.

api.oanor.com/xml-api

A fast, fully-local JSON and CSV toolkit: validate JSON (with a clear error message, type and size), pretty-print and format it (with optional deep key-sorting), minify it (reporting bytes saved), and convert between CSV and JSON — RFC-4180 CSV parsing with automatic value typing, and JSON arrays to CSV. Every endpoint accepts input via the query string or the request body (up to 1 MB). Pure server-side compute, no third-party upstream, so responses are instant and always available. Ideal for data pipelines, ETL, webhooks, config tooling and developer utilities.

api.oanor.com/json-api