Logistic integrations management
Webhooks
You can receive different types of requirements to use your logistics system. The types of requests you can receive are:
Type 1: Receive request to estimate the value of a route.
Type 2: Receive the request of your logistics service for the delivery of an order.
Manage Webhook
POST
https://integrations.mipos.shop/api/v1/logistic/system/webhook/manage
Create or update logistic system webhooks.
Headers
Authorization
string
Bearer {access_token}
Content-type
string
application/json
Request Body
type
string
Webhook type (1 or 2)
integration_id
string
Your Logistic System Id
url
string
Webhook URL
These webhook requests will send a header called X-Signature-Request, as a security measure to confirm that the request came from our system.
Webhook(Type 1 - Estimate Delivery Service)
Content Body
Key
Type
Value
origin
Object
Information where the order will be collected
destination
Object
Information where the order will be delivered
integration_id
Number
Id of your system
Key
Type
Value
address
String
Detailed address information
reference
String
Location help reference
lat
decimal number
Latitude
lng
decimal number
Longitude
contact_phone
String
-
contact_name
String
-
JSON received example
Expected response
Your service should POST a 200
response status code with the following json in the body. If the answer does not follow this format it will be ignored.
Webhook(Type 2 - Request Delivery Service)
Content Body
Key
Type
Value
origin
Object
Information where the order will be collected
destination
Object
Information where the order will be delivered
estimated_pickup
String
Estimated time the order would be ready to pick up
integration_id
String
Id of your system
webhook_url
String
Endpoint that will receive the status changes that occur during the delivery of the order
webhook_url
String
Endpoint that will receive the events of the new location where the order is located
order_id
String
Id of the order
store_id
String
Id of the store
third_party_id
String
Id of the third party service
Object (Origin/Destination)
Type
Value
address
String
Detailed address information
reference
String
Location help reference
lat
decimal number
Latitude
lng
decimal number
Longitude
contact_phone
String
-
contact_name
String
-
JSON received example
Expected response
Your service should POST a 200
response status code with the following json in the body. If the answer does not follow this format it will be ignored.
Send status change in delivery service
To inform the other system, of the state changes that the delivery of the package may have, you can use this endpoint.
Send status updates
POST
https://integrations.mipos.shop/api/v1/logistic/system/status/updates
Headers
Content-type
string
application/json
Request Body
service_identifier
string
Identifier of the service requested from your system
status
string
New delivery service status
location
object
Coordinates where the chage of state occurred
location(Object)
Type
Value
lat
decimal number
Latitude
lng
decimal number
Longitude
Send location of the person carrying the package
To inform the other system of the current location of the package, the frequency of sending this request will be your choice.
Send location updates
POST
https://integrations.mipos.shop/api/v1/logistic/system/status/updates
Headers
Content-type
string
application/json
Request Body
service_identifier
string
Identifier of the service requested from your system
location
object
Coordinates where the chage of state occurred
location(Object)
Type
Value
lat
decimal number
Latitude
lng
decimal number
Longitude
Last updated
Was this helpful?