Unflatten JSON
data.unflatten_json
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
Non-goals
- Does not fetch remote data
- Does not validate against an external schema
- Does not coerce value types
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.
| Limit | Value | Limited by |
|---|---|---|
| Maximum size per input file | 2 MiB | Skill maximum |
How we handle your data
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.
Input schema
| Field | Type | Required | Description |
|---|---|---|---|
| entries | array | No | Bounded array of 0 through 200000 path/value entries used to rebuild the document; omit it when file_ref is the source. |
| file_ref | string | No | Tenant-scoped uploaded entries reference. Omit it to use the required inline entries; never send both. |
| pathStyle | string | No | Path notation; omit it for dot. |
| conflictPolicy | string | No | How duplicate paths are handled; omit it for error. |
| maxDepth | integer | No | Nesting ceiling; omit it for 64. |
Output schema
| Field | Type | Required | Description |
|---|---|---|---|
| json | object | Yes | Rebuilt nested JSON document whose additional properties preserve the reconstructed members — unconstrained RFC 8259 JSON items. |
| entryCount | integer | Yes | How many entries actually landed in the result. |
| conflicts | array | Yes | Bounded array of 0 through 200000 skipped path conflicts; empty under error policy. |
API contract
POST /v1/executecurl -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"}]}}'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
| Code | HTTP | Retryable | Description |
|---|---|---|---|
| VALIDATION_ERROR | 400 | No | The request payload failed schema validation. |
| UNAUTHORIZED | 401 | No | Missing or invalid API key. |
| SKILL_NOT_ACCESSIBLE | 403 | No | The API key is not granted access to this skill. |
| SKILL_NOT_AVAILABLE_FOR_PLAN | 403 | No | This skill is not included in your current plan. |
| PLAN_ELIGIBILITY_UNAVAILABLE | 503 | Yes | Plan eligibility could not be decided. Retry after backoff. |
| SKILL_NOT_FOUND | 404 | No | The requested skill or version does not exist. |
| TENANT_RATE_LIMITED | 429 | Yes | Request rate limit exceeded. Retry after backoff. |
| QUOTA_EXCEEDED | 429 | Yes | Plan quota exhausted. Retryable once the quota period resets. |
| EXECUTION_TIMEOUT | 504 | Yes | Execution exceeded the allowed time budget. |
Other limits
| Limit | Value |
|---|---|
| Recommended inline bytes | 32 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)
{
"skillKey": "data.unflatten_json",
"input": {
"entries": [
{
"value": "Alice",
"path": "customer.name"
}
]
}
}Examples
Rebuild nested customer object
{
"entries": [
{
"value": "Alice",
"path": "customer.name"
}
]
}{
"json": {
"customer": {
"name": "Alice"
}
},
"conflicts": [],
"entryCount": 1
}Dot path with numeric leaf
{
"entries": [
{
"value": 1,
"path": "a.b"
}
]
}{
"json": {
"a": {
"b": 1
}
},
"conflicts": [],
"entryCount": 1
}Recommended use cases
- 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
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.