#json

Converti tra file .env (dotenv) e JSON, in entrambe le direzioni. L'endpoint parse legge il testo .env in un oggetto JSON pulito: salta le righe vuote e i commenti #, rispetta un export iniziale opzionale, rimuove le virgolette singole e doppie (interpretando le sequenze di escape \n, \t e \" all'interno delle virgolette doppie), rimuove i commenti inline dopo valori non quotati, supporta valori che si estendono su più righe all'interno di virgolette, e può opzionalmente espandere i riferimenti ${VAR} e $VAR rispetto alle variabili già definite nello stesso file — lasciando i valori tra virgolette singole rigorosamente letterali. L'endpoint stringify trasforma un oggetto JSON in un file .env valido, quotando solo i valori che ne hanno effettivamente bisogno e opzionalmente prefissando ogni riga con export per il sourcing nella shell. Tutto viene calcolato localmente e deterministicamente, quindi è istantaneo e privato — i tuoi segreti non lasciano mai la richiesta. Ideale per strumenti di configurazione e migrazioni, pipeline CI/CD, conversione di .env in JSON per app che vogliono una configurazione strutturata (e viceversa), e validazione di file di ambiente. Calcolo locale puro — nessuna chiave, nessun servizio di terze parti, istantaneo. Live, nulla viene memorizzato. 3 endpoint. Gestisce il formato dotenv; per file INI con [sezioni] usa un'API INI, e per YAML o TOML usa quelle API.

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

JSON Pointer (RFC 6901) を使用して JSON ドキュメント内の値にアクセスします — JSON Patch (RFC 6902)、JSON Schema、OpenAPI $ref で使用される /a/b/0 パス構文です。get エンドポイントはポインターの値を解決し（存在するかどうかを通知します）。set はポインターに値を書き込み、変更されたドキュメントを返します（最後の配列トークンとして - を使用して追加します）。list はドキュメント内のすべてのポインターを列挙し、オプションでリーフ値のみを対象とします。トークンのエスケープ（~0 は ~、~1 は /）は自動処理されます。深い JSON の外科的な読み取りやパッチ適用、設定やフォームツールの構築、API レスポンスのウォークに最適です。純粋なローカル計算 — キー不要、サードパーティサービス不要、即時。POST で最大 2 MB。ライブ、保存なし。4 つのエンドポイント。JSONPath クエリ、JSON diff/patch、ドット記法フラット化とは異なります。

api.oanor.com/jsonpointer-api

Converti tra file di configurazione INI e JSON, in entrambe le direzioni. L'endpoint parse legge testo INI — sezioni ([section]), sezioni annidate ([database.replica]), coppie chiave=valore, commenti e chiavi ripetute (array) — in un oggetto JSON pulito; l'endpoint stringify trasforma un oggetto JSON in un file INI correttamente formattato. INI è il formato di configurazione utilizzato da Git (.gitconfig), PHP (php.ini), unità systemd, voci desktop, tox/setup.cfg, molti strumenti CLI e software Windows. Perfetto per modificare la configurazione a livello di programmazione, migrare impostazioni tra formati e leggere configurazioni in ambienti che supportano solo JSON. Calcolo puramente locale — nessuna chiave, nessun servizio di terze parti, istantaneo; invia file grandi tramite POST. Live, nulla viene memorizzato. 3 endpoint. Completa i convertitori YAML, TOML, CSV e XML ed è distinto da ciascuno.

api.oanor.com/ini-api

Achate e desachate JSON. Transforme um objeto JSON profundamente aninhado em um mapa de nível único com chaves em notação de ponto (a.b.c → valor, arrays tornam-se a.0, a.1) e transforme um mapa de notação de ponto plano de volta para a estrutura aninhada original. Escolha o delimitador (ponto, barra, qualquer coisa), limite a profundidade ou mantenha arrays intactos. Perfeito para variáveis de ambiente, chaves de tradução i18n, preparar JSON para exportação CSV ou planilha, propriedades de eventos de análise, diff de configuração e serialização de formulários. Processamento local puro — sem chave, sem serviço de terceiros, instantâneo. Ao vivo. 3 endpoints. Distinto de validação/formatação JSON, consulta JSONPath e inferência de tipo.

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

Un toolkit XML rápido y completamente local: convierte XML a JSON y JSON a XML con manejo configurable de atributos, valida la buena formación de XML con detalles de error de línea y columna, y embellece XML preservando el orden de los elementos. Cada endpoint acepta entrada a través de la cadena de consulta o el cuerpo de la solicitud, hasta 2 MB. Cómputo puro del lado del servidor, sin terceros ascendentes, por lo que las respuestas son instantáneas y siempre están disponibles. Ideal para integraciones de sistemas, interoperabilidad SOAP y heredada, procesamiento de RSS y sitemaps, herramientas de configuración y tuberías de datos.

api.oanor.com/xml-api

Un kit d'outils JSON et CSV rapide et entièrement local : validez du JSON (avec un message d'erreur clair, type et taille), affichez-le et formatez-le joliment (avec tri profond optionnel des clés), minifiez-le (en signalant les octets économisés), et convertissez entre CSV et JSON — analyse CSV RFC-4180 avec typage automatique des valeurs, et tableaux JSON vers CSV. Chaque point d'accès accepte l'entrée via la chaîne de requête ou le corps de la requête (jusqu'à 1 Mo). Calcul pur côté serveur, sans tiers en amont, donc les réponses sont instantanées et toujours disponibles. Idéal pour les pipelines de données, ETL, webhooks, outils de configuration et utilitaires pour développeurs.

api.oanor.com/json-api