> ## Documentation Index > Fetch the complete documentation index at: https://docs.get-exo.com/llms.txt > Use this file to discover all available pages before exploring further. # Edit a node > Edit a node's content and/or metadata for the effective subject. `content` triggers a Voyage re-embed and collapses the node to one fresh chunk (multi-chunk re-segmentation stays the ingest pipeline's job). `metadata` merges into the frontmatter; `title` replaces the title. A node not owned by the effective subject is 404. ## Authorization This route requires the `graph:write` scope. A key carrying `memory:forget` or `write` also qualifies. A missing or invalid credential returns 401 [`authentication_error`](/errors/authentication_error). A valid credential without the scope returns 403 [`permission_denied`](/errors/permission_denied), and the problem body names the exact scope required. ## Headers These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below. | Header | Applies | What it does | | ----------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | `X-Exo-API-Key` | Required | Your Exo API key, `exo__`. `Authorization: Bearer exo_...` is accepted as an alternate. | | `X-Exo-Subject` | Optional | Acts for a provisioned subject instead of the key owner. An unprovisioned id returns 403 [`subject_not_provisioned`](/errors/subject_not_provisioned). | | `Idempotency-Key` | Not applicable | The replay engine covers POST requests only. | | `X-Request-Id` | Response | Returned on every response, including `204`s. Quote it in a support request. | ## Success responses | Status | Meaning | | ------ | ------------------- | | `200` | Successful Response | ## Errors | Status | Code | When | | ------ | ------------------------------------------------------ | -------------------------------------------------------------- | | `400` | [`invalid_request`](/errors/invalid_request) | Malformed request, for example an invalid cursor. | | `401` | [`authentication_error`](/errors/authentication_error) | Missing or invalid credentials. | | `403` | [`permission_denied`](/errors/permission_denied) | Missing scope, or an unprovisioned subject selector. | | `404` | [`not_found`](/errors/not_found) | The resource does not exist, or is not visible to this caller. | | `409` | [`conflict`](/errors/conflict) | A conflict with the current state of the resource. | | `422` | [`validation_error`](/errors/validation_error) | The request was understood but failed field validation. | | `429` | [`rate_limit_exceeded`](/errors/rate_limit_exceeded) | Rate limit exceeded. Retry after the Retry-After interval. | | `503` | [`service_degraded`](/errors/service_degraded) | A dependency is temporarily unavailable. Safe to retry. | Every error is an RFC 9457 `application/problem+json` body carrying a stable `code`, a `requestId`, and a `suggestedAction` where Exo has one. See [Errors](/platform/errors). ## Notes * **Editing `content` re-embeds the node** and collapses it to one fresh chunk. Re-segmenting into several chunks stays the ingest pipeline's job. * **`metadata` merges, `title` replaces.** Send only what you want to change. ## OpenAPI ````yaml openapi.json PATCH /v1/graph/nodes/{node_id} openapi: 3.1.0 info: contact: name: Exo url: https://get-exo.com/ description: >- The Exo public developer API: ingest content, retrieve identity-conditioned context, and read the knowledge graph. Authenticate every request with an Exo API key, either as the X-Exo-API-Key header or as Authorization: Bearer exo_... . Errors follow RFC 9457 problem+json with a stable snake_case code on every body. title: Exo API version: 1.0.0 servers: - url: https://api.get-exo.com security: - ApiKeyHeader: [] - BearerAuth: [] tags: - name: retrieve x-group: Retrieval - name: search x-group: Search - name: ingest x-group: Ingestion - name: jobs x-group: Jobs - name: subjects x-group: Subjects - name: recall x-group: Recall - name: graph x-group: Graph - name: insights x-group: Contradictions and proposals - name: condition x-group: Condition - name: brain x-group: Brain - name: sessions x-group: Coding sessions - name: connectors x-group: Connectors - name: events x-group: Events and webhooks - name: meta x-group: Identity - name: keys x-group: Keys and sandbox - name: usage x-group: Usage - name: settings x-group: Settings - name: exports x-group: Exports - name: team x-group: Team - name: admin x-group: Account and purge paths: /v1/graph/nodes/{node_id}: patch: tags: - graph summary: Edit a node description: >- Edit a node's content and/or metadata for the effective subject. ``content`` triggers a Voyage re-embed and collapses the node to one fresh chunk (multi-chunk re-segmentation stays the ingest pipeline's job). ``metadata`` merges into the frontmatter; ``title`` replaces the title. A node not owned by the effective subject is 404. Scope: ``graph:write`` (a ``write`` key also qualifies). operationId: editNode parameters: - description: The knowledge-graph node id. in: path name: node_id required: true schema: description: The knowledge-graph node id. title: Node Id type: string requestBody: content: application/json: schema: $ref: '#/components/schemas/NodePatchRequest' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/GraphNodeMutationResult' description: Successful Response '400': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: Malformed request, for example an invalid cursor. '401': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: Missing or invalid credentials '403': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: Missing scope or unprovisioned subject '404': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: No such node owned by the effective subject '409': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: Conflict, for example a duplicate in-flight idempotent request. '422': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: Validation Error '429': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: Rate limit exceeded '503': content: application/problem+json: schema: $ref: '#/components/schemas/Problem' description: A dependency is unavailable components: schemas: NodePatchRequest: description: >- Body for PATCH /v1/graph/nodes/{id}. Every field is optional; a request that sets ``content`` triggers a Voyage re-embed, ``metadata`` merges into the node frontmatter, ``title`` replaces the display title. properties: content: anyOf: - maxLength: 100000 type: string - type: 'null' title: Content metadata: anyOf: - additionalProperties: true type: object - type: 'null' title: Metadata title: anyOf: - maxLength: 2000 type: string - type: 'null' title: Title title: NodePatchRequest type: object GraphNodeMutationResult: description: >- A knowledge-graph node as it stands after a mutation. Returned by PATCH /v1/graph/nodes/{id}. ``updatedAt`` is the moment the edit was applied; ``authorityLevel`` is the node's influence on retrieval. properties: authorityLevel: anyOf: - type: number - type: 'null' title: Authoritylevel id: title: Id type: string nodeType: title: Nodetype type: string origin: anyOf: - type: string - type: 'null' title: Origin title: anyOf: - type: string - type: 'null' title: Title updatedAt: anyOf: - format: date-time type: string - type: 'null' title: Updatedat required: - id - nodeType title: GraphNodeMutationResult type: object Problem: description: |- RFC 9457 problem+json envelope (spec D9), documented in OpenAPI. Invariant: ``code`` equals the tail of the ``type`` URI (``https://docs.get-exo.com/errors/``). properties: code: title: Code type: string detail: title: Detail type: string documentationUrl: anyOf: - type: string - type: 'null' title: Documentationurl errors: anyOf: - items: $ref: '#/components/schemas/FieldViolation' type: array - type: 'null' title: Errors requestId: default: '' title: Requestid type: string status: title: Status type: integer suggestedAction: anyOf: - type: string - type: 'null' title: Suggestedaction title: title: Title type: string type: title: Type type: string required: - type - title - status - detail - code title: Problem type: object FieldViolation: description: A single field-level violation inside a Problem ``errors[]`` list. properties: code: title: Code type: string field: title: Field type: string message: title: Message type: string pointer: title: Pointer type: string required: - pointer - field - code - message title: FieldViolation type: object securitySchemes: ApiKeyHeader: description: An Exo API key (exo_...) sent as the X-Exo-API-Key header. in: header name: X-Exo-API-Key type: apiKey BearerAuth: description: The same Exo API key (exo_...) sent as an Authorization bearer token. scheme: bearer type: http ````