# 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 |


---

# 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-options.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.