Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Parties [POST]

The POST request to the /parties endpoint can be used to create a new party in the Participant Registry.

The POST request to the /parties is an OPTIONAL endpoint. For more information on OPTIONAL specifications, see functional requirements per role.

Request model

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

  • id String. Contained in party_info. (Required) iSHARE Identifier of the party derived from original party identifiers.

  • name String. Contained in party_info. (Required) Name of the party.

  • alsoKnownAs Array of Strings. Contained in party_info 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).

  • claims Array of objects. (Required) Array of claims for the party. Refer to Claim models for an overview of available claims. In the POST request the id and registrarId fields may be omitted, as they will be provided by the Participant Registry. To create a party as part of the iSHARE Framework, at minimum the following claims MUST be provided:

  • x509Certificate or idpAssertion

  • frameworkCompliance

  • frameworkAgreement

  • frameworkRole

For all roles except for Service Consumer and Entitled Party an x509Certificate claim is required. Service Consumer and Entitled Party MUST either provide a x509Certificate claim or idpAssertion claim if authenticating via Identity Provider.

Example request

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.

Example response

Please also refer to the example response under the GET request definition.

PreviousParties [OPTIONS]NextParties (single party) [GET]

Last updated