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

The trust framework catalogue MUST support a POST call to a /brokers endpoint to retrieve broker evidence (in a brokerEvidence object).

Request

Authorization

An access token is used in POST calls to the /brokers endpoint. For more information, see Access Token.

The trust framework catalogue MUST validate that a POST call to a /brokers endpoint includes the Authorization header according to RFC 6750 and contains a valid access token

Parameters

For information about the parameters that are common to the trust framework’s API’s see Generic API Requirements.

The trust framework catalogue MUST validate that the HTTP body of a POST request to the /brokers endpoint contains the parameters as defined in the table below

Parameter				Type	Description

Parameter				Type	Description
`brokerRequest`			Required	Object	Object MUST contain `policyIssuer`, `target` and `policySets` objects, and may contain the `delegation_path` and `previous_steps` arrays as described below
	`policyIssuer`		Required	String in `delegationRequest`	MUST contain a valid Organisation ID (an EORI or KvK number) of the data service consumer making use of a data service broker.
	`target`		Required	Object in `delegationRequest`	Object MUST contain an `accessSubject`. No other elements are allowed. It makes the entire broker evidence applicable only to this `accessSubject`.
		`accessSubject`	Required	String in `target`	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).

Responses

200 OK

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 as defined here.

The trust framework catalogue MUST include a broker_token including of a brokerEvidence object in a response to a successful GET calls to the /brokers endpoint

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.