Routing Strategy (DOMS)

Endpoints to configure the routing strategy of the DOMS.

Get routing decision logs

get

This part of the API is in Alpha status. For details please check the api-release-life-cycle documentationarrow-up-right.

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Query parameters
sourcingOptionRefstringOptional

All decision logs for given sourcingOptionRef

processRefstringOptional

All decision logs for given processRef

orderRefstringOptional

All decision logs for given orderRef

routingPlanRefstringOptional

All decision logs for given routingPlanRef

sourcingOptionsRefstringOptional

All decision logs for given sourcingOptionsRef

tenantOrderIdstringOptional

All decision logs for given tenantOrderId

startAfterIdstringOptional

All decision logs after given Id

sizeinteger · min: 1 · max: 500Optional

Number of decision logs to show

Default: 25
Responses
chevron-right
200

Decision logs were found & you were allowed to access them. The result is in the body.

application/json

RoutingDecisionLogs

totalintegerRequired

Total number of found decision logs for this query

Example: 42
get
/api/routing/decisionlogs

List category node configuration

get
Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Query parameters
startAfterIdstringOptional

all entities

sizeintegerOptional

number of entities to show

Default: 25
Responses
chevron-right
200

The current list of available categories

application/json

RoutingStrategyNodeConfigCategoryTransporter

totalintegerRequired

Total number of entities found for this query

Example: 42
get
/api/routing/nodeconfigcategories

Create category node configuration

post

Creates a new category for a routing strategies node config.

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Body

RoutingStrategyNodeConfigCategoryForCreation

colorstringRequired
Responses
post
/api/routing/nodeconfigcategories

Returns category node configuration

get

returns the category

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
categoryIdstringRequired

Id of the category you wish to retrieve

Responses
chevron-right
200

The returned category.

application/json

RoutingStrategyNodeConfigCategoryForResponse

get
/api/routing/nodeconfigcategories/{categoryId}

Updates category node configuration

put

Updates a category

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
categoryIdstringRequired

Id of the category you wish to update

Body

RoutingStrategyNodeConfigCategoryForModification

colorstringRequired
versionnumberRequired
Responses
chevron-right
200

The updated category.

application/json

RoutingStrategyNodeConfigCategoryForResponse

put
/api/routing/nodeconfigcategories/{categoryId}

Delete category node configuration

delete

deletes the category

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
categoryIdstringRequired

Id of the category you want to delete

Responses
chevron-right
200

The category has been deleted.

No content

delete
/api/routing/nodeconfigcategories/{categoryId}

No content

List routing strategies

get
Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Query parameters
startAfterIdstringOptional

all entities

sizeintegerOptional

number of entities to show

Default: 25
Responses
chevron-right
200

The current list of available routing strategies

application/json

RoutingStrategyTransporter

totalintegerRequired

Total number of entities found for this query

Example: 42
get
/api/routing/strategies

Create routing strategy

post

Creates a new revision of the routing strategy.

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Body

RoutingStrategyForCreation

Responses
post
/api/routing/strategies

Get routing strategy

get

Returns the routing strategy.

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
strategyIdstringRequired

Id of the routing strategy you wish to retrieve

Responses
chevron-right
200

The returned routing strategy.

application/json

RoutingStrategy

and
get
/api/routing/strategies/{strategyId}

Update routing strategy

put

Updates a routing strategy

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
strategyIdstringRequired

Id of the routing strategy you wish to update

Body

RoutingStrategyForModification

versionintegerRequired
Responses
chevron-right
200

The updated routing strategy.

application/json

RoutingStrategy

and
put
/api/routing/strategies/{strategyId}

Call routing strategy action

post

Performs an action on a routing strategy.

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
strategyIdstringRequired

Id of the routing strategy

Body

RoutingStrategyActionsParameter

or
Responses
chevron-right
200

The updated routing strategy.

application/json

RoutingStrategy

and
post
/api/routing/strategies/{strategyId}/actions

Evaluate routing strategy

post

Evaluates a routing strategy against a given order

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
strategyIdstringRequired

Id of the routing strategy

Body

OrderForCreation

customAttributesobjectOptional

Attributes that can be added to the order. These attributes cannot be used within fulfillment processes, but it could be useful to have the informations carried here.

orderDatestring · date-timeRequired

The date this order was created at the supplying system.

Example: 2020-02-03T08:45:50.525Z
sourceone ofOptional
or
statusstring · enumOptional

The state of the order. Initially it is OPEN.

Possible values:
tenantOrderIdstringOptional

Field can be used as a reference number in foreign systems, for example as a reference to the source system's identifier for this order.

Example: R456728546
Responses
chevron-right
200

The result of the evaluation of the routing strategy.

application/json

RoutingStrategyEvaluationResult

post
/api/routing/strategies/{strategyId}/evaluation

Evaluate routing strategy node

post

Evaluates a routing strategy node and return the path.

Authorizations
AuthorizationstringRequired
Bearer authentication header of the form Bearer <token>.
Path parameters
strategyIdstringRequired

Id of the routing strategy

nodeIdstringRequired

Id of the node

Responses
chevron-right
200

The result of the evaluation of this routing strategy node.

application/json

RoutingStrategyEvaluationResult

post
/api/routing/strategies/{strategyId}/nodes/{nodeId}/evaluation

Last updated