# Parties (single party) \[PATCH]

The `PATCH` request to the `/parties/{partyId}` endpoint can be used to partially update information of an iSHARE participant in the Participant Registry (name and alsoKnownAs). Only the provided fields will be updated, other fields remain unchanged. The partyId cannot be changed through this operation. To update information stored in claims, use the PATCH method on claims instead.

{% hint style="info" %}
The `PATCH` request to the `/parties/{partyId}` is an **OPTIONAL** endpoint.
{% endhint %}

### Request model

The following URL parameter must be used.

* `partyId` {url}/parties/{**partyId**} <mark style="color:red;">(Required)</mark>\
  **String**. The id of the party who must be fetched. Can be anyone of the party id from id or alsoKnownAs attributes of that participant. Since all participants are automatically allocated the derived ishare did, that id is always an option to search for a participant.

The request must be passed as JWT. The JSON model in the JWT is as follows.

* `name`\
  **String**. Root level. <mark style="color:red;">(Required)</mark>\
  Name of the party.
* `alsoKnownAs`\
  **Array of strings**. Contained in `partyInfo`.\
  Array of registered party ids of the party with which the party is also identified. Optional, because a party could be identified with only its iSHARE-ID (in the 'id' property). When updating alsKnownAs all existing values must also be provided. Implementations should raise an error if any of the existing values are missing (meaning deletion) as Ids in this field cannot be deleted once registered.

### Example request

```json
PUT /parties/did%3Aishare%3AEU.NL.NTRLNL-10000001 HTTP/1.1
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json

{
  "name": "Example Corporation",
  "alsoKnownAs": [
    "did:ishare:EU.NL.NTRNL-12345678",
    "did:ebsi:LEIXG-724500AZSGBRY55MNS59",
    "did:web:example.com",
    "CoC:123456789"
  ]
}
```

### Response model

The response will be equal to the response of the GET request for retrieving a single party. Please refer to the [response model as defined here](/participant-registry-role/single-party.md#response-model).

### Example response

Please also refer to the [example response](/participant-registry-role/single-party.md#example-response) under the GET request definition.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dev.ishare.eu/participant-registry-role/parties-single-party-put.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.