/api/v3/orders

post https://delivery.99minutos.com/api/v3/orders

Create orders.

Responses

Response body

object

string

required

shipments

array of objects

required

shipments*

object

sender

object

required

Person who will receive the shipment.

recipient

object

required

Person who will receive the shipment.

origin

object

required

Location where the package is picked up.
Depending on the flow you choose,
you must send different parameters.

A location is a geographical point that can be taken as the origin and/or destination of a shipment.

There are 3 ways in which you can define a location, feel free to choose the one that best suits your business rules.
Each one is described below.

Coords-based
It is the option with the best precision to define an origin or destination.
Latitude and longitude are taken to define the location
LocationId-based
A LocationId is a uuid that identifies a single geographic point.
The locationId is generated by this API (check out the Get Location id request in Locations folder).
By using locationId, no further data needs to be passed.
It is useful when you have the same point in several shipments since you can reuse the locationId.
Address string-based
In this option the client sends only the address. We will process the address to obtain the other data.

However, if the address does not contain information necessary to locate it,
the system will return a 400 error and the order will not be created, so you must handle the error.

It is important to emphasize that in the two previous flows there is no possibility to reject an order for the location

destination

object

required

Location where the package is picked up.
Depending on the flow you choose,
you must send different parameters.

A location is a geographical point that can be taken as the origin and/or destination of a shipment.

There are 3 ways in which you can define a location, feel free to choose the one that best suits your business rules.
Each one is described below.

Coords-based
It is the option with the best precision to define an origin or destination.
Latitude and longitude are taken to define the location
LocationId-based
A LocationId is a uuid that identifies a single geographic point.
The locationId is generated by this API (check out the Get Location id request in Locations folder).
By using locationId, no further data needs to be passed.
It is useful when you have the same point in several shipments since you can reuse the locationId.
Address string-based
In this option the client sends only the address. We will process the address to obtain the other data.

However, if the address does not contain information necessary to locate it,
the system will return a 400 error and the order will not be created, so you must handle the error.

It is important to emphasize that in the two previous flows there is no possibility to reject an order for the location

payments

object

Payment options are included in this section

options

object

required

Options to customize the shipment.

items

array of objects

required

items*

object

uuid | null

required

size

string

required

xs s m l xl xxl unknown -

description

string

weight

integer

required

≥ 1

Measurement in grams of weight

length

integer

≥ 1

Horizontal measurement in centimeters take from one end to the other of the longer or longest side of an object

width

integer

≥ 1

Horizontal measurement in centimeters taken from one end to the other of theshorter or shortest side of an object

height

integer

≥ 1

Vertical measure in centimeters of distance from base to top

string

required

internalKey

string | null

Unique shipment identifier. You can use this field to store your unique identifier of the shipment. All of our tracking systems support searching by internalKey. We strongly suggest you always use this field and make sure it is unique.If its not given we will assign an uuid for this field.

deliveryType

string

required

Indicate the Delivery Type which can be SameDay(SMD), Sprint (SPT), 99minutos(99M), Co2Free (CO2F), Reverse(RET) Tailor made (TLM), PuntoaPunto (P2P). Be careful submitting accepted abbreviations.

SMD SPT 99M CO2F RET NAL TLM P2P

trackingId

integer

required

account

object

required

Has additional fields

billId

integer

required

transactionId

integer

required

channelId

integer

required

draft

boolean

Indicates if an order is not yet finalized. The order is only processed when is confirmed. By default it's false.

deactivated

boolean

required

createdAt

date-time

required

expiresAt

date-time

required

migratedBy

string

required

stream batch

Language

Credentials

Bearer

JWT

URL


xxxxxxxxxx
1
curl --request POST \
2
     --url https://delivery.99minutos.com/api/v3/orders \
3
     --header 'accept: application/json' \
4
     --header 'content-type: application/json'

Click Try It! to start a request and see the response here! Or choose an example:

application/json

201

202

400

401

412