MCT.IT.MonitorAPI

AwsCheckRequest

The following routes are available for this service:
POST	/sns/awscheck

**AwsCheckRequest** Parameters:
Name	Parameter	Data Type	Required
types	body	AWSCheckReturnType	No
Type	body	string	No
MessageId	body	string	No
Token	body	string	No
TopicArn	body	string	No
Message	body	string	No
SubscribeURL	body	string	No
Timestamp	body	string	No
SignatureVersion	body	string	No
Signature	body	string	No
SigningCertURL	body	string	No

**AWSCheckReturnType** Parameters:
Name	Parameter	Data Type	Required
Type	form	string	No
MessageId	form	string	No
Token	form	string	No
TopicArn	form	string	No
Message	form	string	No
SubscribeURL	form	string	No
Timestamp	form	string	No
SignatureVersion	form	string	No
Signature	form	string	No
SigningCertURL	form	string	No

**BaseResponse** Parameters:
Name	Parameter	Data Type	Required	Description
IsSuccess	form	bool	No
ErrorMessage	form	string	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

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"}