Get a reference authority by Id
GEThttps://matls-api.sandbox.raidiam.io/references/authorities/:AuthorityId
get details of a specific authority
Request
Path Parameters
Possible values: non-empty and <= 40 characters, Value must match regular expression ^[^<>]*$
The reference authority Id
Header Parameters
Possible values: Value must match regular expression ^(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)$
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
The PSU's IP address if the PSU is currently logged in with the TPP.
An RFC4122 UID used as a correlation id.
Indicates the user-agent that the PSU is using.
Responses
- 200
- 400
- 401
- 403
- 404
- 406
- 429
- 500
- 502
- 504
Get a reference authority by Id
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
Possible values: non-empty and <= 40 characters, Value must match regular expression ^[^<>]*$
Unique ID associated with the Authorisation reference schema
Possible values: <= 255 characters
Name of the Authority i.e. FCA, etc
Possible values: <= 40 characters
Code of the Authority i.e. FCA, etc
Possible values: Value must match regular expression ^[^<>]*$
URI of the authority
Possible values: <= 255 characters, Value must match regular expression ^[^<>]*$
country of the Authority
Possible values: [Active, Inactive]
Default value: Active
Current status of this resource
{
"AuthorityId": "string",
"AuthorityName": "string",
"AuthorityCode": "string",
"AuthorityUri": "string",
"AuthorityCountry": "string",
"Status": "Active"
}
Bad Request
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
Validation Error messages
{
"errors": [
"string"
]
}
Unauthorized
Response Headers
Forbidden
Response Headers
Not found
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
Validation Error messages
{
"errors": [
"string"
]
}
Not Acceptable
Response Headers
Too many requests, maximum capacity reached. Requests are now throttled.
Response Headers
Internal Server Error
Response Headers
Bad Gateway
Response Headers
Upstream timeout, insufficient capacity to serve request. More capacity being brought online. Please try again.
Response Headers
- curl
- python
- go
- nodejs
- ruby
- csharp
- php
- java
- powershell
- CURL