• You need to provide a callback URL registered with Orion to receive timely notifications of changes in the execution status of your robot tasks when the task status changes.
• Robot task execution status callbacks depend on the robot's task execution status reporting. If the Orion server cannot receive reports from the robot side (such as due to poor network connectivity), callbacks cannot be completed.
• Due to the asynchronous and parallel nature of callbacks, and factors such as the response time of your callback URL, Orion cannot guarantee the timing of callbacks.

• The callback URL can be an HTTP or HTTPS address, but HTTPS is recommended.
• The callback URL must support POST requests, as we will use the POST method for requests.
• The callback URL can carry parameters, but the concatenated parameters must not exceed 1KB in length.

• The callback will occur immediately when an event (i.e., event_type) is triggered for a task.
• Different tasks have different event callbacks, please refer to the Task and Event List.

curl --location 'https://your_domain.com/your_callback_url' \
     --form 'open_appid=test_appid' \
     --form 'open_code=b317979b11292276e0a1b49a08953dec' \
     --form 'robot_sn=test_sn' \
     --form 'ov_corpid=test_ov_corpid' \
     --form 'task_id=85b35e3b5fc452a0f7a6d2a60d9edb9b' \
     --form 'task_type=meals_deliver_task-deliver' \
     --form 'event_type=te_arrived' \
     --form 'task_data={"pos_name":"Table A01"}' \
     --form 'event_data={"pos_name":"Table A01"}'

Additional data (task_data) for different task event types (event_type) under each task type (task_type)

{
    "pos_name" : "Table A01" // Destination point name
}

{
    "pos_name" : "Table A01" // Destination point name
}

Additional data (event_data) for different task event types (event_type) under each task type (task_type)

{
    "pos_name" : "Table A01" // Destination point name
}