PUT | /api/services/{ServiceGuid}/registrationfilters/{RegistrationFilterGuid} |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Value | body | String | No | |
Type | body | String | No | Allowable Values
|
AccessGranted | body | Boolean | No | Allowable Values
|
CraExempt | body | Boolean | No | Allowable Values
|
ServiceGuid | path | Guid | No | |
RegistrationFilterGuid | body | Guid | No | |
DefaultGroupGuid | body | Guid | No | |
AllowSsoSelfRegister | body | Boolean | No | Allowable Values
|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ResponseStatus | form | ResponseStatus | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
PUT /api/services/{ServiceGuid}/registrationfilters/{RegistrationFilterGuid} HTTP/1.1
Host: api.secure-messaging.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{
"value": "String",
"type": "String",
"accessGranted": false,
"craExempt": false,
"serviceGuid": "00000000000000000000000000000000",
"registrationFilterGuid": "00000000000000000000000000000000",
"defaultGroupGuid": "00000000000000000000000000000000",
"allowSsoSelfRegister": false
}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length { "responseStatus": { "errorCode": "String", "message": "String", "stackTrace": "String", "errors": [ { "errorCode": "String", "fieldName": "String", "message": "String", "meta": { "String": "String" } } ], "meta": { "String": "String" } } }