> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dekhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PromoStandards API overview

> Which PromoStandards services DEKHQ provides, the versions and endpoints, and how to make your first request.

[PromoStandards](https://promostandards.org) is a nonprofit that publishes open web service standards for the promotional products industry. Trading partners use the same standard services with every company that supports them, so you don't need a custom integration for each one.

DEKHQ provides PromoStandards services so that trading partners of a decorator can look up the status of their orders and get shipment details, such as carriers and tracking numbers, from their own systems.

<Note>
  You need an id and password to use the API. Ask the decorator you work with whether they offer PromoStandards access and how to request credentials.
</Note>

## Services DEKHQ provides

DEKHQ provides two PromoStandards services, both at version 1.0.0.

| Service | Version | Operations | SOAP endpoint |
| - | - | - | - |
| [Order Status](/api/services/order-status) | 1.0.0 | `getOrderStatusDetails`, `getOrderStatusTypes` | `https://partners.dekhq.com/api/promostandards/order-status` |
| [Order Shipment Notification](/api/services/order-shipment-notification) | 1.0.0 | `getOrderShipmentNotification` | `https://partners.dekhq.com/api/promostandards/order-shipment-notification` |

DEKHQ doesn't provide the Product Data, Inventory, Pricing and Configuration, or Invoice services.

### SOAP and JSON

The services follow the PromoStandards SOAP standard: you send a SOAP 1.1 request envelope with `POST` to the service's endpoint.

The same data is also available as JSON over plain HTTPS, if that's easier for your system:

| Service | JSON endpoint (`GET`) |
| - | - |
| Order Status | `https://partners.dekhq.com/api/partners/v1/orders/status` |
| Order Shipment Notification | `https://partners.dekhq.com/api/partners/v1/orders/shipments` |

Both use the same id and password. See [Authentication](/api/authentication).

### WSDL files

Each service serves its official PromoStandards 1.0.0 WSDL when you add `?wsdl` to its endpoint. Point your SOAP tooling at these URLs to generate a client:

* Order Status: [`https://partners.dekhq.com/api/promostandards/order-status?wsdl`](https://partners.dekhq.com/api/promostandards/order-status?wsdl)
* Order Shipment Notification: [`https://partners.dekhq.com/api/promostandards/order-shipment-notification?wsdl`](https://partners.dekhq.com/api/promostandards/order-shipment-notification?wsdl)

The XSD schemas each WSDL imports are served beside its endpoint, for example `https://partners.dekhq.com/api/promostandards/order-status/GetOrderStatusDetailsRequest.xsd`, and the WSDL references them by full URL, so your tooling can fetch them directly.

## Make your first request

<Steps>
  <Step title="Get your credentials">
    Ask the decorator you work with for an id and a password. You send them with every request. See [Authentication](/api/authentication).
  </Step>

  <Step title="Check that the service is up">
    Send a `GET` request to the health check. It needs no credentials.

    ```bash theme={null}
    curl https://partners.dekhq.com/api/promostandards/health
    ```

    A working service answers with the services and protocols it provides:

    ```json theme={null}
    {
      "status": "ok",
      "surface": "promostandards-partner-api",
      "services": ["order-status-1.0.0", "order-shipment-notification-1.0.0"],
      "protocols": ["soap", "rest"]
    }
    ```
  </Step>

  <Step title="Send a request">
    Send a SOAP request to a service endpoint, with your id and password in the request. [Authentication](/api/authentication) has a complete example. If something goes wrong, the response explains why. See [Errors](/api/errors).
  </Step>
</Steps>

<Info>
  The `partners.dekhq.com` host serves only the PromoStandards API. Any other path on it returns `404 Not found`.
</Info>

***

<sub>Verified against DEKHQ f1677c6 on 2026-10-09</sub>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.