MCT.IT.MonitorAPI

<back to all web services

AwsCheckRequest

The following routes are available for this service:
POST/sns/awscheck
AwsCheckRequest Parameters:
NameParameterData TypeRequiredDescription
typesbodyAWSCheckReturnTypeNo
TypebodystringNo
MessageIdbodystringNo
TokenbodystringNo
TopicArnbodystringNo
MessagebodystringNo
SubscribeURLbodystringNo
TimestampbodystringNo
SignatureVersionbodystringNo
SignaturebodystringNo
SigningCertURLbodystringNo
AWSCheckReturnType Parameters:
NameParameterData TypeRequiredDescription
TypeformstringNo
MessageIdformstringNo
TokenformstringNo
TopicArnformstringNo
MessageformstringNo
SubscribeURLformstringNo
TimestampformstringNo
SignatureVersionformstringNo
SignatureformstringNo
SigningCertURLformstringNo
BaseResponse Parameters:
NameParameterData TypeRequiredDescription
IsSuccessformboolNo
ErrorMessageformstringNo

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

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /sns/awscheck HTTP/1.1 
Host: monitorapi.mcttechnology.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"types":{"Type":"String","MessageId":"String","Token":"String","TopicArn":"String","Message":"String","SubscribeURL":"String","Timestamp":"String","SignatureVersion":"String","Signature":"String","SigningCertURL":"String"},"Type":"String","MessageId":"String","Token":"String","TopicArn":"String","Message":"String","SubscribeURL":"String","Timestamp":"String","SignatureVersion":"String","Signature":"String","SigningCertURL":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"IsSuccess":false,"ErrorMessage":"String"}