---
title: "Update the status list registry entry manually."
method: POST
path: "/management/api/status-list/{statusListId}"
tags: ["Status List API"]
---

# Update the status list registry entry manually.

`POST /management/api/status-list/{statusListId}`

## Request

- Base URL: `http://localhost:8080`
- URL: `http://localhost:8080/management/api/status-list/{statusListId}`
- Auth: none declared

Update the status list registry entry manually. Optionally accepts configuration overrides to control key material selection for this update. If provided, the override will be persisted on the status list and used for subsequent publications. This endpoint can also be used in automatic synchronization mode to update the configuration override.

## Path parameters

- `statusListId` string, uuid, required

## Request body

- StatusListUpdate: Optional overrides for status list updates.
  - `configuration_override` ConfigurationOverride: Override for configuration to be use for the created entity
    - `issuer_did` string, nullable: Override to be used in place of the ISSUER_ID
    - `verification_method` string, nullable: Override for the verification method that is looked up in the did document during verification of the entity. Most often the full did and a unique id after #
    - `key_id` string, nullable: ID of the key in the HSM
    - `key_pin` string, nullable: The pin which protects the key in the hsm, if any. Note that this only the key pin, not hsm password or partition pin.

## Response `200`

OK

- StatusList
  - `id` string, uuid: Id of the status list used by the business issuer.
  - `statusRegistryUrl` string: URI of the status list used by registry.
  - `maxListEntries` integer: How many status entries can be part of the status list. The memory size of the status list is depending on the type and the config of the status list.
  - `remainingListEntries` integer: How many status entries are not used in the status list.
  - `config` object: Additional config parameters, depending on the status list type. For Example {"bits": 2} for token status list with revocation & suspension {"purpose": "suspension"} for a bit string status list for suspension

## Changes

- **2026-10-06** `d24758bc44e0`: 4 info
  - the request property `configuration_override/issuer_did` became nullable
  - the request property `configuration_override/key_id` became nullable
  - the request property `configuration_override/key_pin` became nullable
  - the request property `configuration_override/verification_method` became nullable
- **2026-05-26** `beb3cc8fa8bf`: 1 info
  - removed the non-success response with the status `404`
- **2026-03-11** `dcffaea18715`: 2 warning, 1 info
  - removed the optional property `type` from the response with the `200` status
  - removed the optional property `version` from the response with the `200` status
  - added optional request body
- **2025-11-13** `8f416cf29705`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/swiyu/apis/issuer-service-api/changes/management/api/status-list/:statusListId/post.md)

---

[API](https://skmtc.dev/swiyu/apis/issuer-service-api.md) - [All operations](https://skmtc.dev/swiyu/apis/issuer-service-api/llms.txt) - [OpenAPI document](https://skmtc.dev/swiyu/apis/issuer-service-api/revisions/f2f3fbbaf461?raw)