> For the complete documentation index, see [llms.txt](https://dev.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ishare.eu/participant-registry-role/parties-single-party-options.md).

# Parties (single party) \[OPTIONS]

The `OPTIONS` request to the `/parties/{id}` endpoint returns a list of supported HTTP methods that can be used with the `/parties/{id}` resource. This allows clients to determine which operations are permitted by the server for this endpoint.

### 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 whose claims 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.

### Example request

```
> Authorization: Bearer IIeDIrdnYo2ngwDQYJKoZIhvcNAQELBQAwSDEZMBcGA1UEAwwQaVNIQ

OPTIONS /parties/{id}
```

{% hint style="info" %}
***{id}** must be replaced by the actual party identifier for which HTTP OPTIONS are requested.*
{% endhint %}

### Example response

The server responds with status code 204.

The response contains the following HTTP header:

| Header | Example value       |
| ------ | ------------------- |
| Allow  | GET, PATCH, OPTIONS |