Status Changes Report
POST {{target-endpoint}}
Request
This endpoint is used to send a POST request to the target endpoint of your service. The request payload is in raw (JSON) format and includes a tracking number along with a list of events, each of which contains the event date, time zone, status code, and status description.
The following list shows the catalog of possible statuses to report. Please select the ones that best suit your requirements and communicate them with the Moovin Technology team for proper integration:
Status Code | Status Description |
---|---|
INSERT | Package inserted into an order |
PICKUP | Pick up the package from the client |
INMOOVIN | Entering Moovin headquarters |
EXITMOOVIN | Leaving Moovin headquarters |
ASSINGROUTE | Assigned to a route |
ASSINGMOOVER | Assigned to a Moover |
DELIVERED | The package was delivered |
FAILED | Delivery failed |
GIVEBACK | In transit to the client's headquarters |
INROUTE | In possession of a Moover |
COLLECTMOOVER | When the Moover collected the package |
RELEASE | When a package is to be released |
INSERVICE | When in service |
RETURN | Request for package return |
SCHEDULE | Scheduled |
CANCEL | Cancel |
CANCELREQUEST | Request for package cancellation |
PREPARE | Package that needs to be prepared |
SENDSERVICE | Sent to on-demand contest |
INROUTEPICKUP | Coordinated for delivery |
COORDINATE | Package in route to be picked up |
DELIVEREDCOMPLETE | Complete delivery |
DELIVEREDINCOMPLETE | Incomplete delivery |
REVIEWDOCS | Document review |
COLLECTPICKUP | Moover collects a package |
DELETEPACKAGE | When a package is to be deleted to avoid actions on it |
CHANGEPARAMETERS | Parameter changes |
ASSIGNDRAWER | Assigned to a drawer |
REVIEW | Package review for anomalies |
CHANGECONTACTPOINT | Change in contact information of a package point |
CUSTOMSENTRY | Packages entered customs |
CUSTOMINSPECTION | Inspected by customs |
DELAYCUSTOM | Customs delay |
CUSTOMSCLEARED | Customs duties declared |
CUSTOMSREALEASE | Released by customs |
OUTCOUNTRY | International shipment |
PRECOORDINATIONSEND | Pre-coordination email sent |
CONFIRMEDPRECOODINATION | Client confirms delivery location |
Response
The response to this request can be documented as a JSON schema.
Column | Data type | Description |
---|---|---|
code | int | Response Code |
message | string(255) | Response message |
Response Codes
code | message | HTTP Status Code |
---|---|---|
201 | SUCCESS | 201 |
400 | INCORRECT_REQUEST | 400 |
401 | UNAUTHORIZED | 401 |
404 | ORDERDOESNOT_EXISTS | 404 |
500 | SERVER_ERROR | 500 |
Example:
{
"code": 201,
"message": "SUCCESS"
}
Request Body
{"tracking_number"=>"EX000000001", "events"=>[{"event_date"=>"2020-12-12 15:59:59", "time_zone"=>"+00:00", "status_code"=>"INMOOVIN", "status_description"=>"Entrar en la sede de moovin"}, {"event_date"=>"2020-12-12 18:26:59", "time_zone"=>"+00:00", "status_code"=>"ASSINGROUTE", "status_description"=>"Asignado a una ruta"}]}
HEADERS
Key | Datatype | Required | Description |
---|---|---|---|
Content-Type | string |