---
title: "Receive a NovoLogix prior authorization payload"
method: POST
path: "/api/v1/novologix/prior_auth"
tags: ["NovoLogix"]
---

# Receive a NovoLogix prior authorization payload

`POST /api/v1/novologix/prior_auth`

Receive a prior authorization payload from NovoLogix.

Requires scope: novologix:write

Only the envelope and member id are modeled (see ``NovologixPriorAuthRequest``);
the auth-level body is not mapped yet. We log the *raw* request body — not
``payload.dict()`` — so unmodeled fields are captured for inspection, since
Ninja's schema drops keys it doesn't declare even with ``extra="allow"``.
Downstream processing will be added later.

## Request body

- NovologixPriorAuthRequest — Request schema for the NovoLogix prior authorization endpoint. Models the envelope and member id of NovoLogix's native authorization extract format. Kept lenient (fields optional, extra keys allowed) because NovoLogix populates fields based on available data and future additions go through their standard enhancement process — neither should reject an otherwise valid payload.
  - `data` NovologixPriorAuthData — The ``data`` envelope of a NovoLogix prior authorization payload.
    - `cagmId` string, nullable
    - `operationType` string, nullable
    - `updatePAStatus` NovologixPAStatusUpdate[], nullable
      - `patient` NovologixPatient — Patient block — only the member identifier is modeled for now.
        - `beneficiaryId` string, nullable
    - `isMedicalPA` boolean, nullable
    - `paRequestType` string, nullable

## Response `202`

Accepted

- AcceptedResponse — Response schema for endpoints that accept a payload for later processing.
  - `status` 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)