> ## 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. # Accept an edge proposal > Accept a proposal: promote it to a real KG edge. Writes the edge exactly as the dashboard accept does -- the proposal moves into `graph_edges` (`edge_id = proposal_id`, `is_approved = TRUE`, all cross-domain fields preserved) and the proposal row is deleted, atomically in one transaction. The edge carries `created_by = api:` for audit. A proposal id that is not the subject's (cross-org, cross-user, or already consumed) returns 404 `proposal_not_found`. Acceptance SUPERSEDES a prior rejection: any `proposal_rejections` row for this pair (either direction) is cleared in the same transaction, so a pair you once rejected and later accepted is not silently blocked from being re-suggested if the edge is removed again. Brain staleness is not stamped on `brain_metadata`: its `status` CHECK allows only `none|queued|training|ready|failed` (no `stale`) and writing it would also corrupt the in-flight-train guard. The new edge instead changes the org's live `graph_edges` count, which the ExoBrain compares against its exported N/E on every query -- so `/v1/retrieve` honestly flips to `degradationReason="brain_stale"` on the next call, no metadata flag needed. ## Authorization This route requires the `write` scope. 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` | Honoured | Makes a retry safe. The same key with the same body replays the original response instead of acting twice. See [Idempotency](/platform/idempotency). | | `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. | Beyond the shared statuses, this route can answer with [`proposal_not_found`](/errors/proposal_not_found), [`idempotency_in_flight`](/errors/idempotency_in_flight), [`idempotency_key_reuse`](/errors/idempotency_key_reuse). Every problem body names its own `code`, and the `type` URI always resolves to the matching page. 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). ## OpenAPI ````yaml openapi.json POST /v1/proposals/{proposal_id}/accept 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/proposals/{proposal_id}/accept: post: tags: - insights summary: Accept an edge proposal description: >- Accept a proposal: promote it to a real KG edge. Writes the edge exactly as the dashboard accept does -- the proposal moves into ``graph_edges`` (``edge_id = proposal_id``, ``is_approved = TRUE``, all cross-domain fields preserved) and the proposal row is deleted, atomically in one transaction. The edge carries ``created_by = api:`` for audit (spec section 6). A proposal id that is not the subject's (cross-org, cross-user, or already consumed) returns 404 ``proposal_not_found``. Acceptance SUPERSEDES a prior rejection: any ``proposal_rejections`` row for this pair (either direction) is cleared in the same transaction, so a pair you once rejected and later accepted is not silently blocked from being re-suggested if the edge is removed again. Brain staleness is NOT stamped on ``brain_metadata``: its ``status`` CHECK allows only ``none|queued|training|ready|failed`` (no ``stale``) and writing it would also corrupt the in-flight-train guard. The new edge instead changes the org's live ``graph_edges`` count, which the ExoBrain compares against its exported N/E on every query -- so ``/v1/retrieve`` honestly flips to ``degradationReason="brain_stale"`` on the next call, no metadata flag needed. operationId: acceptProposal parameters: - description: The proposal id from GET /v1/proposals. in: path name: proposal_id required: true schema: description: The proposal id from GET /v1/proposals. title: Proposal Id type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/ProposalDecision' 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 proposal for this 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: ProposalDecision: description: >- The outcome of an accept/reject on a proposal. ``decision`` is ``accepted`` or ``rejected``. ``edgeId`` is the id of the edge created by an accept (equal to the proposal id); null on reject. ``rejectionRecorded`` reports whether the reject was written to the durable rejection ledger, i.e. whether this pair is now permanently excluded from re-suggestion rather than merely removed from the queue. It is null on accept (which has nothing to record) and false only on a deployment whose schema predates the ledger. properties: decision: title: Decision type: string edgeId: anyOf: - type: string - type: 'null' title: Edgeid proposalId: title: Proposalid type: string rejectionRecorded: anyOf: - type: boolean - type: 'null' title: Rejectionrecorded required: - proposalId - decision title: ProposalDecision 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 ````