Headers
-
x-fapi-auth-date
string The time when the PSU last logged in with the TPP. All dates in the HTTP headers are represented as RFC 7231 Full Dates. An example is below: Sun, 10 Sep 2017 19:43:31 UTC
Format should match the following pattern:
^(Mon|Tue|Wed|Thu|Fri|Sat|Sun), \d{2} (Jan|Feb|Mar|Apr|May|Jun|Jul|Aug|Sep|Oct|Nov|Dec) \d{4} \d{2}:\d{2}:\d{2} (GMT|UTC)$
. -
x-fapi-customer-ip-address
string The PSU's IP address if the PSU is currently logged in with the TPP.
-
x-fapi-interaction-id
string An RFC4122 UID used as a correlation id.
-
x-customer-user-agent
string Indicates the user-agent that the PSU is using.
Query parameters
-
page
integer The page number to return of the result set
-
size
integer The size of the pages to return
-
startDate
string(date-time) Optional start of date range to constrain the set of results returned. This will restrict the clients returned to those whose metadata was most recently modified after the specified startDate. The date must be supplied in RFC3339 format. If not supplied, the startDate used will be the epoch.
-
endDate
string(date-time) Optional end of date range to constrain the set of results returned. This will restrict the clients returned to those whose metadata was most recently modified before the specified sendDate. The date must be supplied in RFC3339 format. If not supplied, the endDate used will be the current date and time.
-
role
string A role name, clients that have this role (whether active or inactive) will be returned. Clients with this role in an Inactive state will be returned but will not show the role in their roles array
-
status
string Return clients with a matching status. Available values are Active, Inactive and Suspended
-
name
string Search the available clients based on a name match. Match is partial so a search for 'abc' will return clients 'abc','abc1', '1abc' and '1abc2'
Responses
-
200 application/json
All clients
-
400 application/json
Bad Request
-
Unauthorized
-
Forbidden
-
404 application/json
Not found
-
Not Acceptable
-
Too many requests, maximum capacity reached. Requests are now throttled.
-
Internal Server Error
-
Bad Gateway
-
Upstream timeout, insufficient capacity to serve request. More capacity being brought online. Please try again.
curl \
--request GET 'https://matls-api.sandbox.raidiam.io/clients' \
--header "Authorization: Bearer $ACCESS_TOKEN" \
--header "x-fapi-auth-date: string" \
--header "x-fapi-customer-ip-address: string" \
--header "x-fapi-interaction-id: string" \
--header "x-customer-user-agent: string"
# Headers
x-fapi-interaction-id: 73cac523-d3ae-2289-b106-330a6218710d
# Payload
{
"empty": true,
"numberOfElements": 42,
"offset": 42,
"pageNumber": 42,
"pageable": {
"number": 42,
"offset": 42,
"size": 42,
"sort": {
"orderBy": [
{
"ascending": true,
"direction": "ASC",
"ignoreCase": true,
"property": "createdAt"
}
],
"sorted": true
},
"sorted": true,
"unpaged": true
},
"size": 42,
"totalPages": 42,
"totalSize": 42
}
# Headers
x-fapi-interaction-id: 73cac523-d3ae-2289-b106-330a6218710d
# Payload
{
"errors": [
"string"
]
}
# Headers
x-fapi-interaction-id: 73cac523-d3ae-2289-b106-330a6218710d
# Payload
{
"errors": [
"string"
]
}