---
title: "Resolve Route"
method: POST
path: "/v1/resolve"
tags: ["resolve"]
---

# Resolve Route

`POST /v1/resolve`

## Request

- Base URL: `https://api.june.januraine.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.june.januraine.ai/v1/resolve`
- Auth: none declared

## Headers

- `X-Canvas` string, nullable
- `X-API-Key` string, nullable
- `Authorization` string, nullable

## Request body

- ResolveIn
  - `strong_only` boolean
  - `min_confidence` number

## Response `200`

Successful Response

- ResolveOut
  - `same_as_written` integer, required
  - `groups` integer, required
  - `candidates` integer, required
  - `created` IngestReceipt: CH-2a mutation receipt — what THIS call did to the graph, by id. The created/updated split is the undo contract: a write can be reversed by tombstoning ``node_ids`` (its own creations) and never touches ``updated_node_ids`` (pre-existing knowledge it merely merged into). Canonical home (2026-08-08) — ``ingest_route`` re-exports it, so the file/sql routes' existing imports keep working.
    - `node_ids` string[]
    - `updated_node_ids` string[]
    - `edge_ids` string[]
  - `notes` string[]

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/januraine/apis/june-ai.md) · [All operations](https://skmtc.dev/januraine/apis/june-ai/llms.txt) · [OpenAPI document](https://skmtc.dev/januraine/apis/june-ai/revisions/097b95b163c7?raw)