---
title: "Retrieve NOP Waiver Authorisation Status"
method: POST
path: "/customs/uk-notice-of-presentation-waiver/authorisations"
tags: ["Endpoints"]
---

# Retrieve NOP Waiver Authorisation Status

`POST /customs/uk-notice-of-presentation-waiver/authorisations`

Use this endpoint to request the NOP waiver authorisation status of between 1 and 3000 EORI numbers.

## Headers

- `Accept` 'application/vnd.hmrc.1.0+json', required
- `Content-Type` 'application/json', required

## Request body

- object
  - `eoris` string[], required — An identifier for the business, unique to the customer.

## Response `200`

Success - Authorised. A list of EORI numbers provided with their authorised status as boolean 'true' or 'false'.

- object
  - `date` string, date-time
  - `eoris` object[]
    - `eori` string
    - `authorised` boolean

## Other responses

- `400` — Validation failure. The server cannot or will not process the request due to something that is perceived to be a client error. Possible causes could be: <ul> <li>unsupported country code in EORI number (GB and XI are supported)</li> <li>invalid format for EORI number</li> </ul>
- `401` — Authentication failure. Commonly a client side error, typically generated when authentication information is not provided, possibly by omitting a bearer token.
- `403` — Forbidden. The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server. Other possible causes could be: <ul> <li>Authentication token expired</li> <li>Missing authentication token</li> </ul>
- `406` — Not acceptable. This response is sent when the incoming request desires an accept header for a content we cannot support. Primary way to fix 406 errors is as follows: <ul> <li>Check Accept header</li> <li>Check Request and Response headers</li> </ul>
- `413` — Request entity too large. The request was rejected because the payload is too large. This API allows a maximum limit of 100KB for request bodies. Please reduce the size of the request payload and try again.
- `429` — Request in excess of rate limit. The user has sent too many requests in a given amount of time.
- `500` — Internal Server Error. The server has encountered a situation it does not know how to handle.
- `503` — Service Unavailable. The server is currently unable to handle the incoming requests.

---

[API](https://skmtc.net/hmrc/apis/uknw-auth-checker-api.md) · [All operations](https://skmtc.net/hmrc/apis/uknw-auth-checker-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/hmrc/uknw-auth-checker-api/revisions/73a6d650d2fd/schema)