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 list of all data services to the requesting party
A data service provider MUST support a GET call to a /dataServices endpoint to retrieve a list of their DSGO data services.
Request
Authorization
An access token is used in GET calls to the /dataServices endpoint. For more information, see Access Token.
Parties MUST validate that a GET call to a /dataServices endpoint includes the “Authorization" header according to RFC 6750 and includes a valid access token
Parties MUST validate that the HTTP body of a GET request to the /dataServices endpoint contains the query parameters as defined in the table below
Query parameter
Type
Description
Query parameter
Type
Description
page
Optional
integer
Requests to return a specific page
size
Optional
integer
Sets the page size (number of items per page)
format
Optional
string
Used to specify if the response is in plain JSON or a signed JWT. Enum with values json, jwt
> Authorization: Bearer IIeDIrdnYo2ngwDQYJKoZIhvcNAQELBQAwSDEZMBcGA1UEAwwQaVNIQ
GET /dataServices?format=jwt
Responses
200 OK
If successful, the response contains data providing the requested information in a dataServicesToken. This is a signed JWT, which contains the claims as defined in the iSHARE JWT, and additionally contains a dataServicesInfo object asdefined here. The response may also be the dataServicesInfo object in plain JSON.
Parties MUST offer a dataServicesToken including a dataServicesInfo object in a response to a successful GET call to the /dataServices endpoint
Parties MAY also offer a plain JSON dataServicesInfo object in a response to a successful GET call to the /dataServices endpoint
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.