Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Retrieves a single claim of a party to the requesting party from the DSGO participant registry, based on an iSHARE did organisation identifier and a claim ID.
The central participant registry MUST support a GET call to a /parties/{partyId}/claims/{claimId} endpoint to retrieve a single party claim object. {partyId} must be a valid iSHARE did organisation identifier. {claimId} must be a valid claim id of a claim in that party_info object.
Request
Authorization
An access token is used in GET calls to the /parties/{partyId}/claims/{claimId} endpoint. For more information, see Access Token.
The central participant registry MUST validate that a GET call to a /parties/{partyId}/claims/{claimId} endpoint includes the “Authorization" header according to RFC 6750 and includes a valid access token
The central participant registry MUST validate that the HTTP body of a GET request to the /parties/{partyId}/claims/{claimId} endpoint contains the query parameters as defined in the table below
Query parameter
Type
Description
Query parameter
Type
Description
format
Optional
String
Used to specify if the response is in plain JSON or a signed JWT. Allowed values are json, jwt
> Authorization: Bearer IIeDIrdnYo2ngwDQYJKoZIhvcNAQELBQAwSDEZMBcGA1UEAwwQaVNIQ
GET /parties/did:ishare:EU.NL.NTRNL-98765432/claims/1624717e-414d-40ed-8c18-21f1528ff9ac
Responses
400 Bad Request
When Authorization header is provided, but the token format is invalid (for example, not Bearer). Additionally, a 400 should be returned when the provided access token is valid, but query parameters are either invalid or none of them were provided.
401 Unauthorized
When Authorization header is either missing, invalid or the access token has already expired.
404 Not Found
When a party or claim is not found
200 OK
If successful, the response contains data providing the requested parties information in a claimToken. The claimToken is a signed JWT, which contains the claim as defined in the iSHARE JWT, and additionally contains a claim object as defined here.
The response may also be the claim object in plain JSON.
The central participant registry MUST offer a claimToken including a claim object in a response to a successful GET calls to the /parties/{partyId}/claims/{claimId} endpoint
The central participant registry MAY offer a plain JSON claim object in a response to a successful GET calls to the /parties/{partyId}/claims/{claimId} endpoint