How Authorizations Work
A prior authorization ties a payer's approval (an auth number) to a patient, for either a product or one or more HCPCS codes, with an approved period, units, and amount.
When invoices are created for that patient, payer, and product or HCPCS, NikoHealth can apply the authorization automatically and release invoices that are on hold waiting for an authorization.
Before You Start: Lookups
What you need | Endpoint |
Patient ID |
|
Payer |
|
Product (product authorizations) |
|
Create an Authorization
POST /v1/authorizations
Fields
Field | Required | Notes |
| ✅ | Numeric patient ID, sent as a number, e.g. |
| ✅ | From |
|
| The payer's authorization number |
|
|
|
|
| When |
|
| When |
|
| Price option type: |
|
| Approved date range, |
|
| Approved units |
|
| Approved amount |
|
|
|
|
| Free text |
Invoice Automation Options
Field | What it does when |
| Stops this authorization from being applied to invoices automatically |
| Updates invoices on hold for Authorization Required with this authorization |
| Updates invoices on hold for Authorization Expired with this authorization |
Example: product authorization
POST /v1/authorizations
{
"PatientId": 10000105,
"PayerId": "d0bd30210e89f1745e45c3b14d0440512c5a8234",
"AuthNumber": "CPM123456789",
"AuthorizationType": "Product",
"ProductId": "X98HS36WD42EJ57YT25L",
"TypeId": "Purchase",
"Period": { "From": "2026-11-01", "To": "2027-01-31" },
"Units": 24,
"UpdateInvoicesOnHoldForAuthorizationRequired": true
}
Example: HCPCS authorization
{
"PatientId": 10000105,
"PayerId": "d0bd30210e89f1745e45c3b14d0440512c5a8234",
"AuthNumber": "AUTH-55512",
"AuthorizationType": "Hcpcs",
"Hcpcs": ["E0601"],
"TypeId": "Rental",
"Period": { "From": "2026-11-01", "To": "2027-10-31" },
"Modifiers": { "Level1": "RR" }
}
Response: 201 Created
{ "Id": "02564fe731dbaa0b6e2132435a15c0e5adfa6ad9" }
Search Authorizations
GET /v1/authorizations
Filter | Notes |
|
|
|
|
|
|
| e.g. active or expired |
| Expiry date range |
|
|
|
|
| Paging |
{
"Count": 1,
"Items": [
{
"Id": "02564fe731dbaa0b6e2132435a15c0e5adfa6ad9",
"AuthNumber": "CPM123456789",
"AuthorizationType": { "Id": "Product", "Name": "Product" },
"Status": { "Id": "2", "Name": "Expired" },
"ExpiryDate": "2026-11-21T00:00:00",
"Patient": { "Id": 10000105, "Name": { "FirstName": "Jane", "LastName": "Doe" } },
"Payer": { "Id": "d0bd30210e89f1745e45c3b14d0440512c5a8234", "Name": "Example Payer" },
"Product": { "Id": "X98HS36WD42EJ57YT25L", "Name": "Foam Dressing 6x6" },
"DoNotAutoApplyOnInvoices": false,
"Archived": false
}
]
}
Get one authorization: GET /v1/authorizations/{id}. Also returns Units, Amount, Period, Modifiers, and Notes.
The API can create and view authorizations, but it has no update or delete endpoint. Make those changes in the NikoHealth UI.
Authorizations on Invoices
You can also send prior auth numbers directly on an invoice, at the claim level (Options.PriorAuthorizations) or the service-line level (ServiceLines[].PriorAuthorizations).
See Invoices via API.
Common Errors
Code | Meaning |
| Invalid request, e.g. a missing |
| Token missing, expired, or invalid |
| You don't have permission to access this resource |
| Authorization, patient, payer, or product not found |
| Too many requests |
