OK - Feature status

Our platform's extensive feature system allow for easy customization to meet your needs. Checking on the the current state of features through REST or GraphQL endpoints enables quick reactions in your clients. This level of configurability ensures a personalized experience for optimal efficiency.

Get features status

More Features-API information can be found here: REST API documentation - Features

REST API

GET https://{YOUR-TENANT-NAME}.api.fulfillmenttools.com/api/features

This will respond with a HTTP 200 OK containing all features for that facility:

[
    {
        "name": "routing",
        "status": "enabled",
        "version": 42
    }
]

GraphQL API

feature(featureName: "{featureName}") {
  name
  status
  version
}

Enter the feature name you want to query in the query parameter in {featureName}. You will receive a response similar to the following:

{
    "data": {
        "feature": {
            "name": "routing",
            "status": "enabled",
            "version": 42
        }
    }
}

The name field denotes the feature name, while the status field indicates whether the corresponding feature is currently enabled, disabled or inactive. If a feature is inactive it cannot be enabled or disabled. The version field indicates the current version of the corresponding feature document.

Get specific feature

GET https://{YOUR-TENANT-NAME}.api.fulfillmenttools.com/api/features/{featureName}

Enter the feature name you want to query in the URL in {featureName}. You will receive a response similar to the following:

{
    "name": "routing",
    "status": "enabled",
    "version": 42
}

Feature status

Enabled

All functions and endpoints related to this feature will be available.

Disabled

All functions and endpoints related to this feature will not be available.

Inactive

This is a transitional state recommended for disabling a feature. Entities that are already in the processing pipeline of the targeted feature can still be processed, but new entities won't trigger the feature. For example, if an order has been created but a pick job has not been generated yet, setting the picking feature to inactive would allow a pick job to be created for that order. However, any new orders created after setting the feature to inactive would not trigger the creation of pick jobs.