# SOR43 - Create a thread on a service order

Call FrequencyRecommended usage: At each new message posted on a service orderMaximum usage: At each new message posted on a service order

Endpoint: POST /api/mms/orders/{order_id}/threads

## Path parameters:

  - `order_id` (string, required)
    The identifier of the order on which the thread is created.

## Query parameters:

  - `shop_id` (integer)
    Use this parameter when your user has access to several shops. If not specified, the shop_id from your default shop will be used.

## Request fields (multipart/form-data):

  - `files` (array)
    List of attachments for the first message of the thread

  - `thread_input` (object, required)
    The content of the thread: body, topic, participants...

  - `thread_input.body` (string, required)
    The message body

  - `thread_input.to` (array, required)
    The message recipients
    Enum: "OPERATOR", "SHOP", "CUSTOMER"

  - `thread_input.topic` (object, required)
    Thread topicThe topic can either have a free or a fixed value depending on the topic type

  - `thread_input.topic.type` (string, required)
    Topic type
    Enum: "FREE_TEXT", "REASON_CODE"

  - `thread_input.topic.value` (string, required)
    Topic value, which depends on the type:When type equals FREE_TEXT: the topic value is freeWhen type equals REASON_CODE: the topic value must be a reason code (example: MPS_ORDER_MESSAGING_ISSUE)

## Response 201 fields (application/json):

  - `message_id` (string, required)
    Id of the first message created on the thread

  - `thread_id` (string, required)
    Id of the created thread