Movilitas.Cloud Support

You can use the Manufacturer V2 API to integrate the shopfloor and the enterprise resource planning (ERP) systems with the Serialized Manufacturing application.

The Manufacturer V2 API uses the Representational State Transfer (REST) standard to interact with other systems.

The Manufacturer V2 API is an extension of the Serialized Manufacturing application of Movilitas.Cloud that enables you to send requests from external systems to the application.

The following figure provides an overview of all the requests that you can send by using the Manufacturer V2 API:

This article describes how to create and execute a label (printing) order in the Serialized Manufacturing application using the Manufacturer V2 API.

API Tool to Use

In this document, we provide examples by using the cURL command-line tool. To send the API request, you can find a lot of user-friendly REST API tools on the Internet, for example, Postman.

Before You Begin

1. You must enable the Serialized Manufacturing application.

2. You must create an API key and secret.

3. You must create a shopfloor channel with the Manufacturer V2 API source. You will need the channel key for your requests.

4. You must configure the Serialized Manufacturing application and the channels required to connect to external systems.

5. You must have the authentication token to send requests over API. Select one of the following ways:

• Apply a dynamic token. Send an authentication request over the Authentication API. For more information about the Authentication API, open the Tenant Dashboard in Movilitas.Cloud, select API keys, and choose Authentication API Documentation. Also, see Authentication Request.
• Apply a static token. Generate a static token for your previously created API key.

For more information, see Configuring the Movilitas.Cloud APIs.

Procedure

1. Use the POST method and the following URL:

https://api-acc.movilitas.cloud/v1/manufacturer/v2/api/label_orders/

2. For the header, define the content type (JSON), the authentication token, and the channel key.

The token can be given in one of the following ways:

• As x-access-token header.
• As Authorization header by using the Bearer schema.

Header Option 1

Header Option 2

3. In the body of the request, define the parameters and their values based on the table below.

*If the extra_label_amount field is provided in the request, the extra_label_type field is required.

**If any of the origin fields is provided in the request, all origin fields are required (origin_product_code, origin_product_code_schema, and origin_batch).

***If the destination_tag field points to a Zebra Cloud Connect destination, the template_tag field is required.

4. Send the request. The label order is created and, depending on the execute flag status in the request, released, that you can check under the Serialized Manufacturing application --> Labels --> Orders tab.

Sample cURL Request

curl -X POST \
  https://api-acc.movilitas.cloud/v1/manufacturer/v2/api/label_orders/ \
  -H 'Content-Type: application/json' \
  -H 'x-access-token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJrZXkiOiKzX2FqazQyS3RLQWhHdiE4TUZtY1Q2Uzh' \
  -H 'x-channel-key: Ky1SpfEXmjj05fW3USBFD3pgoEi9AQ29Atsnj4Zy' \
  -d '{
    "order_id": "MCS365906",
    "product_code": "02026072111121",
    "product_code_schema":"GTIN",
    "batch": "BAT26072101",
    "quantity": 10,
    "extra_label_amount": 20,
    "extra_label_type": "percentage",
    "origin_product_code": "R8543592",
    "origin_product_code_schema": "CUSTOM",
    "origin_batch": "HERP0721",
    "destination_tag": "sftp-test",        
    "execute": true
}'

Sample Response (Success 200) 

{
    "success": true,
    "message": "Label order created successfully"
}

Error Types and Resolution

This section lists some of the most general error types when sending the request.