Parties
Last updated
Last updated
Even though all request parameters are optional, at least one parameter should be provided. E.x. if you would like to retrieve all parties, you could use name=*
or eori=*
.
Decoded parties_token parameters:
The model of the parties_token
JWT response is available on Swaggerhub. For convenience the model of the parties_info object, contained within the token, is described below:
parties_info
Object. Root level.
Contains results count and information about the parties.
count
Integer. Contained in parties_info
.
Total count of found parties. Since one request returns up to 10 parties, the value helps to understand if more than one page exists.
data
Array of Objects.
Contained in parties_info
.
Collection of parties.
party_id
String. Contained in party_info
.
iSHARE identifier of the party. Should be EORI number.
party_name
String. Contained in party_info
.
Name of the party.
registrar_id
String. Contained in party_info
.
Identifier of the party who registered the participant identified by the party_id attribute above.
adherence
Object. Contained in party_info
.
Object which contains status and validity timestamps of the party.
status
String. Contained in adherence
.
Status of the party. Available values are Active, Pending, NotActive and Revoked.
start_date
Timestamp (ISO 8601). Contained in adherence
.
UTC timestamp which states since when adherence status has established.
end_date
Timestamp (ISO 8601). Contained in adherence
.
UTC timestamp which states till when adherence status has established.
additional_info
Object. Contained in party_info
.
Object which contains additional general contact information of the party.
description
String. Contained in additional_info
.
A brief description of the party.
logo
String. Contained in additional_info
.
URL pointing to the endpoint where company logo can be found.
website
String. Contained in additional_info
.
URL pointing to the endpoint where company logo can be found.
company_phone
String. Contained in additional_info
.
General company phone number of the party.
company_email
String. Contained in additional_info
.
General company email id of the party.
publicly_publishable
Boolean. Contained in additional_info
.
Consent to publicly publish the information contained in this object.
countries_operation
Array of Objects. Contained in additional_info
.
An array of ISO names of the countries where the party operates.
sector_industry
Array of Objects. Contained in additional_info
.
An array of GICS based sectors/industry that party serves in.
tags
String. Contained in additional_info
.
An free text field containing keywords relevant for party.
agreements
Array of Objects. Contained in data
.Object which contains details about contracts including data space contracts that party has agreed and signed to.
type
String. Contained in the object of agreements
.
Type of agreement. Refers to the official type of agreement. For iSHARE following types are available Terms of Use, Accession Agreement, Certified Party Agreement, Satellite Agreement. Additionally, each data space can define their own type and it can be listed here when appropriate data space is chosen.
title
String. Contained in the object of agreements
.
The name of the agreement or agreement file.
status
String. Contained in the object of agreements
.
Status of the agreement. Available values are Draft, Signed, Accepted, Obsolete.
sign_date
Timestamp (ISO 8601). Contained in the object of agreements
.
Date of signature of the agreement.
expiry_date
Timestamp (ISO 8601). Contained in the object of agreements
.
Expiry date of the agreement. For non expiring agreements the end date is far in future.
hash_file
String. Contained in the object of agreements
.
The calculated hash of the agreement file that has been uploaded. Note agreements are not stored in ledger, but only their hash.
framework
String. Contained in the object of agreements
.
The trust framework to which this agreement complies to. Currently, only iSHARE is available.
dataspace_id
String. Contained in the object of agreements
.
The ID of the data space. If specified, party is onboarded in accordance to this data space’s terms and conditions.
dataspace_title
String. Contained in the object of agreements
.
The name of the selected dataspace.
complaiancy_verified
String. Contained in the object of agreements
.
Legal compliance to this agreement has been verified in accordance with the process set in trust framework as we as data space governance. Possible values are Yes, No, Not Applicable.
certificates
Array of Objects. Contained in data
.
Object which contains the details of the PKI/x509 certificates of the party. Either certificates or SPOR must be present.
subject_name
String. Contained in the object of certificates
.
subjectName as encoded in the X.509 certificate which corresponds with the party that is being requested from the iSHARE Satellite. Used by the iSHARE Satellite to match the certificate identifier.
certificate_type
String. Contained in the object of certificates
.
type of certificate.
enabled_from
Timestamp (ISO 8601). Contained in the object of certificates
.
UTC timestamp which states since when certificate is valid.
x5c
String. Contained in the object of certificates
.
The base64 encoded pem format value of the certificate identified by its subject name and fingerprint.
x5t#s256
String. Contained in the object of certificates
.
The SHA256 fingerprint of the certificate.
spor
Array of Objects. Contained in data
.
The signed proof received from recognised issuer (currently eID identity providers) of information about the organisation and the authorised representative of that organisation being authenticated with “High” level of assurance.
signed_request
String. Contained in the object of certifications
.
verifiable credentials of the participant signed by a trusted authority vouching for its authenticity.
roles
Array of Objects. Contained in data
.
Object which contains details about the iSHARE roles of the party. The details include the level of assurance as well as compliance status for each role.
role
String. Contained in the object of roles
.
Role name. Possible roles are ServiceConsumer, ServiceProvider, EntitledParty, AuthorisationRegistry, IdentityProvider, IdentityBroker and iShareSatellite.
start_date
Timestamp (ISO 8601). Contained in the object of roles
.
UTC timestamp which states since when certification is valid.
end_date
Timestamp (ISO 8601). Contained in the object of roles
.
UTC timestamp which states till when certification is valid.
loa
Integer. Contained in the object of roles
.
Certificate’s level of assurance. Available values are 1 (low), 2 (substantial) and 3 (high).
compliancy_verified
Boolean. Contained in the object of roles
.
Compliance requirements of this role has been met by party.
legal_adherence
Boolean. Contained in the object of roles
.
Legal requirements of this role has been met by party including signing of appropriate agreements.
auth_registries
Array of Objects. Contained in data
.
Object which contains details about the authorisation registers that the party uses.
name
String. Contained in the object of auth_registries
.
The name of the authorisation registry provider.
id
String. Contained in the object of auth_registries
.
The Id of the authorisation registry provider.
url
String. Contained in the object of auth_registries
.
The URL pointer specific to the party where authorisations can be queried/checked from.
dataspace_id
String. Contained in the object of auth_registries
.
The id of the data space where the party uses this authorisation registry provider.
dataspace_name
String. Contained in the object of auth_registries
.
The name of the data space corresponding to the data space id.
The response contains an encoded JWT, which looks like this:
After decoding, the example content of the JWT looks like this:
Note
This page must be considered part of the iSHARE Trust Framework
Search for participant information from your satellite. Various search parameters are supported as shown below. When results are more then 10 participants, pagination is used in response and each page contains up to 10 participants. Server response is an iSHARE signed JSON Web Token. Please refer to the models 'jwt_header' and 'jwt_payload_party_token' which indicate what the decoded response will look like.
/parties
Optional parameter used to search by party's "Active" status.
true
Optional parameter used to search by party's name. Can contain a single * as wildcard.
*Corporation
Optional parameter used to search by party's ID (EORI). Can contain a single * as wildcard.
EU.EORI.NL123456789
Search for parties that play one of the certified roles as defined in iSHARE role framework.
true
Search parties with specific adherence date
2023-01-31T00:00:00.000Z
Search for parties with adherence status like "Active", "Revoked","Not Active", "Pending"
Active
Search parties with specific adherence start date
2023-01-31T00:00:00.000Z
Search parties with specific adherence end date
2023-01-31T00:00:00.000Z
Search parties by their registrar satellite's ID (EORI) number
EU.EORI.NL012345678
Search a party by their website URL
https://www.example.com
Search a party by their email ID
John.doe@example.com
Search a party by their company phone number
Search parties whose general company contact information is allowed to be published
true
Search parties who match any of the keywords that they have added in their participant information under tags. It is a free text field and can contain any value
mobility
Search parties based on which framework they were onboarded with. Currently parties can only be registered with "iSHARE" framework
iSHARE
Search parties based on the subject name of their PKI (x509) certificates. Usually to find a party who is requesting tokens
SERIALNUMBER=EU.EORI.US000000005,CN=CFMInternational,O=CFMInternational,C=US
Search parties based on their roles as defined in iSHARE role framework. Possible roles are ServiceConsumer, ServiceProvider, EntitledParty, AuthorisationRegistry, IdentityProvider, IdentityBroker and iShareSatellite.
ServiceConsumer
Search parties based on their level of assurance which is registered in the participant list. Possible values are Low/Substantial/High
Substantial
Search parties that have their compliance to framework verified or not.
true
Search parties that have signed the appropriate legal agreements and that have been verified during or after onboarding. Parties adhering to legal agreements are legally obliged to adhere to terms of use of data.
true
Search parties based on their authorisation registry provider. The ID (EORI) of the authorisation registry must be provided in search parameter and this must be listed as authorisation registry in the participant record
EU.EORI.NL000000004
Search parties based on their authorisation registry provider. The name of the authorisation registry must be provided in search parameter and this must be listed as authorisation registry in the participant record
Askme anything
Search parties based on data-spaces they participate in. The ID of the data-space must be provided
EU.DSP.NLLOGISTICS_DLDS
Search parties based on data-spaces they participate in. The name of the data-space must be provided
Dutch Mobility Dataspace
Search parties by name of country they list as their country of operation
Belgium
Search parties by name of sector they list as their sector/industry
Energy
The parties API by default uses pagination. Each page size is fixed at 10 parties per page. When search results into more then 10 parties, the page parameter must be added for next pages
2
Search parties based on the subject name of their PKI (x509) certificates. Usually to find a party who is requesting tokens
SERIALNUMBER=EU.EORI.US000000005,CN=CFMInternational,O=CFMInternational,C=US