---
title: "Receive an OptumRx NRT pharmacy accumulator transaction"
method: POST
path: "/api/v1/optumrx/pharmacy_txn"
tags: ["OptumRx NRT"]
---

# Receive an OptumRx NRT pharmacy accumulator transaction

`POST /api/v1/optumrx/pharmacy_txn`

Receive a pharmacy accumulator transaction from OptumRx (RxCLAIM).

Requires scope: optumrx:write

The transaction is persisted idempotently and committed, then a pharmacy
acknowledgement is sent back to OptumRx. The synchronous handshake below only
confirms receipt; if the outbound ack fails it is left pending and retried
when OptumRx resends (which reuses the same stored row — no duplicate).

## Request body

- OptumRxPharmacyTransactionRequest — Request schema for the OptumRx NRT pharmacy accumulator transaction. Mirrors the OptumRx ``DefaultPharmacyTransaction`` envelope but keeps each section as an open dict rather than a fully typed model: the payload is persisted verbatim rather than validated, so we can capture real OptumRx traffic before pinning the inner schema. The two top-level keys are the fixed contract; their contents pass through untouched.
  - `requestContext` object
  - `pharmacyTransactionContent` object

## Response `202`

Accepted

- OptumRxHandshakeResponse — Synchronous handshake returned to OptumRx (OptumRx ``HandshakeResponse``). Mirrors the OptumRx NRT contract: a ``responseCode``/``responseStatus`` plus a ``partnerCorrelationId`` that ties our stored record to OptumRx's request.
  - `responseCode` string, required
  - `responseStatus` string, required
  - `partnerCorrelationId` string, required

---

[API](https://skmtc.net/cloverhealth/apis/clover-api.md) · [All operations](https://skmtc.net/cloverhealth/apis/clover-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cloverhealth/clover-api/revisions/28797307aae6/schema)