Get the nominative onboarding file of a holder registry entry.

get

https://api.t-dx.com/api/rest/v1/holder-registries/{registryId}/entries/onboardings/{onboardingId}/attributes/{attributeId}/file/{fileName}

This endpoint retrieves nominative onboarding file.It is accessible to issuers exclusively when the client account is or has been associated with the registry ID specified in the query string.

Responses

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200A successful response.

400Bad Request: indicates that the server cannot or will not process the request due to something that is perceived to be a client error (for example, malformed request syntax, invalid request message framing, or deceptive request routing)

401Unauthenticated: indicates that the client request has not been completed because it lacks valid authentication credentials for the requested resource

403Forbidden: indicates that the server understands the request but refuses to authorize it

404Not Found: indicates that the server cannot find the requested resource

500Internal Server Error: indicates that the server encountered an unexpected condition that prevented it from fulfilling the request

503Service Unavailable: indicates that the server is not ready to handle the request.

defaultAn unexpected error response.