---
title: "Receive a NovoLogix note payload"
method: POST
path: "/api/v1/novologix/notes"
tags: ["NovoLogix"]
---

# Receive a NovoLogix note payload

`POST /api/v1/novologix/notes`

Receive a note from NovoLogix.

Requires scope: novologix:write

Notes are sent on a channel separate from the prior authorization payload
(NovoLogix's recommended best practice). Like ``receive_prior_auth``, we log
the *raw* request body — not ``payload.dict()`` — so any unmodeled fields are
captured for inspection. Downstream processing will be added later.

## Request body

- NovologixNoteRequest — Request schema for the NovoLogix notes endpoint. Models NovoLogix's confirmed note contract (PA number, note type/visibility, text, and authorship). Kept lenient (fields optional, extra keys allowed) for the same reasons as the prior authorization payload: NovoLogix populates fields based on available data and future additions go through their standard enhancement process — neither should reject an otherwise valid payload.
  - `data` NovologixNoteData — The ``data`` envelope of a NovoLogix note payload.
    - `paNumber` string, nullable
    - `noteType` string, nullable
    - `noteVisibility` string, nullable
    - `noteText` string, nullable
    - `createdDate` string, nullable
    - `createdBy` NovologixNoteAuthor — Author block for a note (``createdBy``).
      - `userId` string, nullable
      - `name` string, nullable
    - `source` 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)