---
title: "Bulk append fee status rows for multiple Application List Entries."
method: PUT
path: "/application-lists/{listId}/entries/fees"
tags: ["application-list-entries"]
---

# Bulk append fee status rows for multiple Application List Entries.

`PUT /application-lists/{listId}/entries/fees`

Atomically appends the supplied fee status rows to each specified entry in the source list (path `listId`). Existing fee status rows are preserved to retain fee-status history. If any supplied fee detail has `hasOffsiteFee=true`, the selected entries will be ensured to have an off-site fee mapping. `hasOffsiteFee=false` does not remove an existing off-site fee mapping. If any entry cannot be updated, no fee status rows are changed.

## Path parameters

- `listId` string, uuid, required

## Response `200`

Fee status rows appended for all entries.

## Other responses

- `400` — Invalid request parameters.
- `401` — Authentication required or token invalid.
- `403` — Authenticated but not permitted to perform this action.
- `404` — The requested resource was not found.
- `409` — Conflict with the current state of the resource.
- `500` — Unexpected server error.

---

[API](https://skmtc.net/hm-courts-and-tribunals-service/apis/applications-register-api.md) · [All operations](https://skmtc.net/hm-courts-and-tribunals-service/apis/applications-register-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/hm-courts-and-tribunals-service/applications-register-api/revisions/ea2dadd4450b/schema)