Errors

When a request fails, the response tells you why. SOAP endpoints return a SOAP fault. JSON endpoints return an HTTP error status with a JSON body.

SOAP faults

DEKHQ follows SOAP 1.1: a fault comes back with HTTP status 500 and a text/xml body like this one.

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <soap:Fault>
      <faultcode>soap:Client</faultcode>
      <faultstring>Invalid id or password</faultstring>
    </soap:Fault>
  </soap:Body>
</soap:Envelope>

A faultcode of soap:Client means something in your request needs to change. Read the faultstring to find out what.

`faultstring`	What it means	What to do
`Malformed SOAP request`	DEKHQ couldn’t read the request as a SOAP envelope with a body and an operation element.	Check that you’re sending a complete SOAP envelope as the request body, with the operation element (for example `GetOrderStatusDetailsRequest`) inside `Body`.
`Invalid id or password`	The id or password is wrong, or missing.	Check the `id` and `password` elements. See Authentication.

JSON errors

JSON endpoints return an HTTP error status and a body with an error message, for example:

{"error":"Invalid id or password"}

Status	`error`	What to do
`401`	`Missing credentials — use HTTP Basic auth (id:password)`	Send your id and password with HTTP Basic authentication.
`401`	`Invalid id or password`	Check your id and password.

Not found

The partners.dekhq.com host serves only the PromoStandards API. A request to any other path returns HTTP 404 with the text Not found. Check the endpoint URL against the list of services.

_{Verified against DEKHQ 41cdde7 on 2026-10-09}

Get started

Services

API reference

Reference

SOAP faults

JSON errors

Not found

​SOAP faults

​JSON errors

​Not found

SOAP faults

JSON errors

Not found