Skip to main content

Squillify development is paused indefinitely. Read why, and discover what this experiment achieved. Read the story

MicroSkills Reference

Unflatten JSON

data.unflatten_json

ProductionBounded custom (Class B)Deterministicverifiablefastv1.0.0
File inputNo network

Overview

When you send flattened {path, value} entries, we reconstruct a nested JSON object using dot, JSON Pointer, or bracket notation. You choose how duplicate or conflicting paths are handled. Inverse of data.flatten_json for compatible settings. Do not use this when paths conflict and error policy is unacceptable. Accepts file input via file_ref — no need to extract file content first.

Deterministic reconstruction avoids silent data loss when nesting flattened fields.

Reliability

VERIFIABLE and deterministic when paths do not conflict (or policy handles them). Provide exactly one of entries or file_ref. Validation errors (not retryable — fix input): AMBIGUOUS_RESULT on duplicate path, container type conflict, or root type conflict when conflictPolicy is error; entries over 200,000; invalid path or maxDepth exceeded; array index too large.

Context footprint

Returns json, entryCount, and conflicts. A successful call costs 1 execution credit.

When to use it

After flattening, CSV import, or config mapping with compatible pathStyle.

When paths may conflict and you cannot choose a conflictPolicy.

Scope

Note
Rebuilds nested JSON from flattened path/value entries.

Non-goals

  • Does not fetch remote data
  • Does not validate against an external schema
  • Does not coerce value types

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

data-transformation

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input2 MBMax file size2 MB

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.

LimitValueLimited by
Maximum size per input file2 MiBSkill maximum

How we handle your data

Sensitive output possible
What this means

This skill may receive sensitive content and may return submitted, transformed, extracted, or reformatted content.

Squillify guarantees
  • Runs inside Squillify
  • This skill runs inside Squillify.
  • Payloads are not sent to an external service by this skill.
  • Squillify does not permanently store submitted payloads.
  • Telemetry records metadata only, not submitted content.
  • Submitted payloads are not used for training.
  • Submitted payloads are not reviewed by humans.
  • This skill does not target sensitive data.
  • The response may contain submitted or transformed content.
Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

FieldTypeRequiredDescription
entriesarrayNoBounded array of 0 through 200000 path/value entries used to rebuild the document; omit it when file_ref is the source.
file_refstringNoTenant-scoped uploaded entries reference. Omit it to use the required inline entries; never send both.
pathStylestringNoPath notation; omit it for dot.
conflictPolicystringNoHow duplicate paths are handled; omit it for error.
maxDepthintegerNoNesting ceiling; omit it for 64.

Output schema

FieldTypeRequiredDescription
jsonobjectYesRebuilt nested JSON document whose additional properties preserve the reconstructed members — unconstrained RFC 8259 JSON items.
entryCountintegerYesHow many entries actually landed in the result.
conflictsarrayYesBounded array of 0 through 200000 skipped path conflicts; empty under error policy.

API contract

POST /v1/execute
curl
curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"data.unflatten_json","input":{"entries":[{"path":"customer.name","value":"Alice"}]}}'
Integrations
TypeScript SDK
import { Squillify } from "@squillify/sdk";

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

const { output } = await sq.execute("data.unflatten_json", {"entries":[{"value":"Alice","path":"customer.name"}]});

Errors

CodeHTTPRetryableDescription
VALIDATION_ERROR400NoThe request payload failed schema validation.
UNAUTHORIZED401NoMissing or invalid API key.
SKILL_NOT_ACCESSIBLE403NoThe API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN403NoThis skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE503YesPlan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND404NoThe requested skill or version does not exist.
TENANT_RATE_LIMITED429YesRequest rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED429YesPlan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT504YesExecution exceeded the allowed time budget.

Other limits

LimitValue
Recommended inline bytes32 KiB

Limitations

  • Does not fetch remote data
  • Does not validate against an external schema
  • Does not coerce value types
  • Ambiguous or conflicting path sets when error policy cannot be used

How to call

POST /v1/execute (requires authentication)

Request bodyjson
{
  "skillKey": "data.unflatten_json",
  "input": {
    "entries": [
      {
        "value": "Alice",
        "path": "customer.name"
      }
    ]
  }
}

Examples

Rebuild nested customer object

Inputjson
{
  "entries": [
    {
      "value": "Alice",
      "path": "customer.name"
    }
  ]
}
Expected outputjson
{
  "json": {
    "customer": {
      "name": "Alice"
    }
  },
  "conflicts": [],
  "entryCount": 1
}

Dot path with numeric leaf

Inputjson
{
  "entries": [
    {
      "value": 1,
      "path": "a.b"
    }
  ]
}
Expected outputjson
{
  "json": {
    "a": {
      "b": 1
    }
  },
  "conflicts": [],
  "entryCount": 1
}
  • Round-trip after data.flatten_json
  • CSV import field mapping
  • Config transformation from flat key/value lists

Avoid for

  • Ambiguous or conflicting path sets when error policy cannot be used

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

jsontransformationdata