<div class="endpoint"><span class="method">POST</span><code>/api/v1/workspaces/&#123;workspaceId&#125;/rips-packages/&#123;packageId&#125;/reconciliations</code></div>

**Operation ID:** `ripsPackages.reconcile` · **Access:** PAT with `send` scope and authorized workspace where applicable · **Effect:** `external`.

:::caution[Production action]
This operation can send data to an external service. Use a new idempotency key for each new intent. A timeout does not prove that the action failed.
:::

An `Idempotency-Key` is **required**. Retry the same intent with the same key and the same request bytes. [Read the retry rules](/guides/errors-and-retries/).

Read the [rips packages workflow](/guides/rips-lifecycle/) before this operation.

Supply the uncertain attempt ID and a known ministry CUV. The server verifies the evidence; it does not discover a CUV from an invoice number.

## Parameters

| Name | In | Required | Type / allowed values |
| --- | --- | --- | --- |
| `workspaceId` | path | Yes | string |
| `packageId` | path | Yes | string |
| `idempotency-key` | header | Yes | string |

## Request body

**Content type:** `application/json` · **Required:** yes.

Schema: [ReconcileDispatchInput](/reference/schemas/reconcile-dispatch-input/). [Browse schema fields](/reference/schemas/).

<details>
<summary>Example: knownCuv</summary>

Synthetic contract example. Replace identifiers and clinical data with authorized values. This example does not prove ministry acceptance.

[Download JSON](/examples/rips-packages-reconcile-knownCuv.json)

```json
{
  "attemptId": "attempt-demo-001",
  "evidence": {
    "cuv": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
  }
}
```

</details>

## Responses

| HTTP | Content | Schema |
| --- | --- | --- |
| 200 | `application/json` | [RipsDispatchResult](/reference/schemas/rips-dispatch-result/) |
| 400 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 401 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 403 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 404 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 409 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 413 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 415 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 422 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 428 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 500 | `application/json` | [ApiError](/reference/schemas/api-error/) |
| 503 | `application/json` | [ApiError](/reference/schemas/api-error/) |

Use `error.code`, `error.issues`, and `requestId` for JSON errors. [Error and recovery guide](/guides/errors-and-retries/).

## cURL

Set the connection variables from the [quickstart](/guides/quickstart/). Set each path variable to an authorized identifier or an allowed parameter value from the table above.

Save your authorized JSON input as `request.json`. Use the request schema and examples above; replace synthetic data before use.

Set `IDEMPOTENCY_KEY` to a unique key for this intent. Preserve it and the exact request for retries.

```bash
curl --fail-with-body --request POST \
  "$RIPSCLOUD_BASE_URL/api/v1/workspaces/$WORKSPACE_ID/rips-packages/$PACKAGE_ID/reconciliations" \
  --header "Authorization: Bearer $RIPSCLOUD_TOKEN" \
  --header 'Accept: application/json' \
  --header "Idempotency-Key: $IDEMPOTENCY_KEY" \
  --header 'Content-Type: application/json' \
  --data-binary @request.json
```