check_xi _service_http_soap to check ContactLab Mail API ...

[xpertech]

there're a lot of "No data received from host" alert frequently when using check_xi _service_http_soap to check ContactLab Mail API, what could be the problem?

====================================================================================================================
check_xi_service_http_soap!/soap/services!application/soap+xml!<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ws="http://ws.api.contactlab.com/"><soap:He ... key><value xsi:type="xsd:string">[email protected]</value></attributes></userData></ws:sendImmediateMessageSdataCAl></soap:Body></soap:Envelope>!-S -e '200 OK' -s 'sendImmediateMessageSdataCAlResponse'!!!!

l /soap/services

l application/soap+xml

l <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ws="http://ws.api.contactlab.com/"><soap:He ... key><value xsi:type="xsd:string">[email protected]</value></attributes></userData></ws:sendImmediateMessageSdataCAl></soap:Body></soap:Envelope>

l -S -e '200 OK' -s 'sendImmediateMessageSdataCAlResponse'
====================================================================================================================

Support edit: Altered post to remove API and user keys.

[mbellerue]

I did a quick search of their developer site, but I couldn't find any information on limits of the usage of the ContactLab soap API. Usually there is some limit on the number of requests you can make in a certain time period, in order to prevent accidental or intentional DDOS attacks. I would think that you would be able to login more than a few times in a 15 minute period, but it might be worth posing the question to their support.

For now, however, it might be worth your while to try to execute the check command manually, and see if you can get it to fail at the command line. Then see if the output differs from what you have above. From what I can read of the output you posted, it looks like a successful connection.