Activate an authority authorisation domain by Id
PUThttps://matls-api.sandbox.raidiam.io/references/authorities/:AuthorityId/authorisationdomains/:AuthorityAuthorisationDomainId
activate a mapping between an authority and authorisation domain
Request
Path Parameters
Possible values: non-empty
and <= 40 characters
, Value must match regular expression ^[^<>]*$
The reference authority Id
Possible values: <= 50 characters
, Value must match regular expression ^[^<>]*$
ID of the Authority mapped with Authorisation Domain
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.
- application/json
Body
required
Authority Authorisation Domain mapping request
Possible values: non-empty
, Value must match regular expression ^[^<>]*$
The authorisation domain name
Possible values: [Active
, Inactive
]
Default value: Active
Current status of this resource
Responses
- 200
- 400
- 401
- 403
- 404
- 406
- 429
- 500
- 502
- 504
Authority to domain mapping data
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
Possible values: Value must match regular expression ^[^<>]*$
The authorisation domain name
Possible values: Value must match regular expression ^[^<>]*$
The GUID of the Authority
Possible values: Value must match regular expression ^[^<>]*$
The GUID of the Authority-Domain mapping
Possible values: [Active
, Inactive
]
Default value: Active
Current status of this resource
{
"AuthorisationDomainName": "string",
"AuthorityId": "string",
"AuthorityAuthorisationDomainId": "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
curl -L -X PUT 'https://matls-api.sandbox.raidiam.io/references/authorities/:AuthorityId/authorisationdomains/:AuthorityAuthorisationDomainId' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-H 'Authorization: <API_KEY_VALUE>' \
-d '{
"AuthorisationDomainName": "string",
"Status": "Active"
}'