Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
Token | query | string | No | |
Action | query | string | No | |
MinScore | query | float | No | |
Score | query | float | No | |
ChallengedOn | query | DateTime | No | |
ErrorCodes | query | List<string> | No | |
Success | query | bool | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .soap12 suffix or ?format=soap12
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /soap12 HTTP/1.1
Host: www.bernhardt.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<RecaptchaFailed xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Emun.Auth">
<Action>String</Action>
<ChallengedOn>0001-01-01T00:00:00</ChallengedOn>
<ErrorCodes xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
<d2p1:string>String</d2p1:string>
</ErrorCodes>
<MinScore>0</MinScore>
<Score>0</Score>
<Success>false</Success>
<Token>String</Token>
</RecaptchaFailed>
</soap12:Body>
</soap12:Envelope>