For the complete documentation index, see llms.txt. This page is also available as Markdown.

Fulfillment | Orders

List fulfillment orders of your customers

get

A fulfillment order represents a single order of a service or cancellation or change of an existing service instance (subscription).

These orders need to be fulfilled to process the lifecycle of the service instances.

For example, use the status filter to get open fulfillment orders that you then can process through the transition route.

You can only access orders of customers of your provider entity.

Authorizations
X-API-KEYstringRequired

Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.

Query parameters
customersinteger · int32[]Optional

Filter the orders by one or more customer ids or names.

servicesinteger · int32[]Optional

Filter the orders by one or more ordered service ids.

orderstringOptional

Filter by the order number of the sales order.

externalIdsstring[]Optional

Filter by one or more external ids.

serviceCategoriesinteger · int32[]Optional

Filter by one or more service categories based on their id.

afterstring · date-timeOptional

Filter the orders created after the specified date.

beforestring · date-timeOptional

Filter the orders created before the specified date.

sortBystringOptional

Sort the results by a given criterion (customer|date).

Default: date
sortOrderstringOptional

Sort the results in a given order (asc|desc).

Default: desc
offsetinteger · int32Optional

Specifies the index of the first result to return

Default: 0
limitinteger · int32Optional

Specifies the maximum number of results to return (min: 1; max: 1000)

Default: 100
Responses
200

OK: List of fulfillment orders.

application/json
totalinteger · int32Required
get/v1/fulfillment/orders

Retrieve a single fulfillment order by its id.

get
Authorizations
X-API-KEYstringRequired

Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.

Path parameters
orderIdinteger · int64Required

The identifier of the fulfillment order.

Responses
200

OK: The requested fulfillment order.

application/json
transactionTypestring · enumRequired

The action triggered by a fulfillment order.

Possible values:
statusstring · enumRequired

Status of the fulfillment process.

Possible values:
fulfillmentTypestring · enumOptional

Types of fulfillment to complete a customer order.

Possible values:
isPreorderbooleanOptional

Indicates whether this order is a preorder. Preorders should only be prepared until ready for delivery and then wait to be requested by the customer before shipment.

partnerNotestring · nullableOptional

A note shared with the intermediary partner. (Only for orders placed by partner customers)

Example: Contract number: 154587858
preferredProvisionDatestring · date-time · nullableOptional

The preferred provision date.

totalRecurringPricenumber · doubleOptional

Sum of the recurring prices of the service offer and the ordered options in this item.

totalPurchasePricenumber · doubleOptional

Sum of the purchase prices of the service offer and the ordered options in this item.

idinteger · int64Required

The identifier of the order.

Example: 13
externalIdstring · nullableOptional

The identifier of the order in an external app.

Example: 5214e3bed1454eaf
get/v1/fulfillment/orders/{orderId}
Deprecated

Update a fulfillment order regarding context information like the external id. To update the status see transition endpoint. (deprecated - please use the PATCH route instead)

put
Authorizations
X-API-KEYstringRequired

Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.

Path parameters
orderIdinteger · int64Required

The identifier of the order.

Body
externalIdstring · max: 100 · nullableOptional

The identifier of the order in an external app. Note: null value will be ignored on update. Set to empty string to clear a current value.

Example: 5214e3bed1454eaf
Responses
204

NoContent: Update successful.

No content

put/v1/fulfillment/orders/{orderId}

No content

Patch a fulfillment order regarding context information like the external id. To update the status see transition endpoint.

patch
Authorizations
X-API-KEYstringRequired

Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.

Path parameters
orderIdinteger · int64Required

The identifier of the order.

Bodyobject · Operation[]
valueany · nullableOptional
pathstring · nullableOptional
opstring · nullableOptional
fromstring · nullableOptional
Responses
204

NoContent: Patch successful.

No content

patch/v1/fulfillment/orders/{orderId}

No content

Update the fulfillment status of an order

post

To process the status of an order, cancellation or change, post a transition. This will process the lifecycle status of the related service instance (subscription).

See the schema of the request body below for allowed actions in the transition.

You can only access orders of customers of your provider entity.

Authorizations
X-API-KEYstringRequired

Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.

Path parameters
orderIdinteger · int64Required

The identifier of the order.

Body
actionstring · enumRequired

The action to take on the fulfillment order.

Possible values:
activationDatestring · date-time · nullableOptional

The (UTC) date on which the service should be activated (time component is ignored). Only applicable for the complete action. If not provided, the service is activated immediately upon completion.

Responses
204

NoContent: Update successful.

No content

post/v1/fulfillment/orders/{orderId}/transitions

No content

Last updated

Was this helpful?