Quick Start

The Orders API lets you place IT procurement orders directly from your own systems — no portal access required, only a single API key. This page explains the key concepts behind an API order so you know what to expect before you start integrating.

What is an API order?

An API order is a purchase order submitted programmatically to Danoffice IT via a single POST /orders/create call. It works the same as any other order placed through our webshop: lines are picked, packed, and shipped to your specified address. The difference is that we can help you taylor a setup where your system controls the entire flow — from triggering the order to receiving the confirmation and shipping updates.

The order request

A createOrderRequest consists of five main parts:

References

customerReference      Your internal reference (ticket ID, PO number, etc.)
externalDocumentNumber Your external document number (e.g. a purchase order)
type                   Order type — agreed with your account manager. Default is "New"

externalDocumentNumber and the generated correlationId are both returned on confirmations and invoices, making it straightforward to match orders back to records in your system.

Invoice details

The party to be invoiced. You can either pass a full address or an existing invoice record ID (id) if one is already registered with us. In most cases your account manager will provide you with one or more id's that you can include on the request. An id holds all the invoice details agreed with you and the account manager making it straight forward for the platform to handle your orders. At the same time it removes the option for errors.

Consignee

The company receiving the goods — if different from the invoice party. Like the invoice, this can be a full address or an existing consignee id. This is not necessary in most cases, but we will tell you to include it, when doing an integration workshop and analyzing your needs.

Sell-to

The party that is purchasing the goods, if different from the invoice party. This is typically required for marketplace or reseller scenarios.

Shipping details

Where and to whom the order should be shipped. Each order ship to a unique address, which means you can target any delivery location — a specific office, a remote user's home, or a warehouse — without batching.

The shipping part is special as it is the one with most requirements due to carrier limitations. We have configured the API reference with all the necessary details, so you can adopt it into your system and avoid validation errors.

Key shipping fields:

attention      Name of the person to address the delivery to
reference      Your internal shipping reference
deliveryAt     "Office" or "Home" — affects carrier handling
contact        Name, phone, and email of the delivery contact
address        Full address including city, zip, state (US/AU), and ISO3166 Alpha-2 country code.

Order lines

An array of items to include in the order:

itemNumber          Danoffice IT item number (agreed with your account manager)
quantity            Number of units
customerReference   Line-level internal reference (this is optional, but used in a lot of cases with SAP and ServiceNow)
comments            Optional instructions (e.g. "Add asset tag", "Insert SIM card")

The order response

A successful POST /orders/create returns a correlationId. This is your unique reference for the order within the Commerce Cloud platform — it is used to match incoming webhook events (shipping updates, status changes) back to the original order in your system.

Store it alongside your own references when you receive it.

What happens next

After the order is placed:

1. Danoffice IT receives and validates the order
2. The order enters the fulfilment workflow
3. As the order progresses, webhook events are pushed to your configured endpoint (if configured).

Ready to place an order?

Head to the API Reference for the full endpoint documentation, schema reference, and an interactive playground where you can test a live request with your API key.