Used to obtain broker evidence from the trust framework catalogue. Broker evidence can be used by a data service broker in future data service requests to data service providers
Excerpt | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
|
Request
Authorization
An access token must be used in POST calls to the /brokers
endpoint. For more information, see Access Token.
Excerpt | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
|
...
For information about the parameters that are common to the trust framework’s API’s see Generic API Requirements.
Excerpt | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
|
Parameter | Type | Description | |||
---|---|---|---|---|---|
| Required | Object | Object MUST contain | ||
| Required | String in | MUST contain a valid Organisation ID (an EORI or KvK number) of the data service consumer making use of a data service broker. | ||
| Required | Object in | Object MUST contain an | ||
| Required | String in | MUST contain a valid Organisation ID (an EORI or KvK number) of the data service broker which receives the rights to act for a data service consumer). |
...
Successful, the response contains data providing the requested parties information in a broker_token
. The broker_token
is a signed JWT, which contains the claims as defined in the Authentication JWT, and additionally contains a brokerEvidence
object.
...