Skip to main content
API docs by Redocly

Enviame API (3.0.0)

Download OpenAPI specification:Download

License: Apache 2.0

Intro

Hello world, this is the new Enviame API v3 definition.

Authentication

Before using this API version, you have to request an initial setup of your company's account to our support team. You'll be provided with a cURL example to an Auth0 application that we will have created for you (we're sorry for this unsophisticated way, we are working on a better setup). The Auth0 app provides valid access tokens to call our API methods.

Pickups

Get Pickups as a Company/Seller

Lista todos los retiros creados por una Empresa/Seller.

path Parameters
shipper_id
required
integer <int64>

ID of the Company/Seller, generated by Enviame

header Parameters
Accept
required
string
Default: application/json

Not modified

Responses

Response samples

Content type
application/json
{
  • "code": 201,
  • "data": [
    ]
}

Create Pickup as a Company/Seller

Endpoint to create pickup as a Company/Seller. The response depends on the schedule of each carrier.

path Parameters
shipper_id
required
integer <int64>

ID of the Company/Seller, generated by Enviame

header Parameters
Accept
required
string
Default: application/json

Not modified

Request Body schema: multipart/form-data
carrier_code
required
string

Carrier code to which the pickup will be requested.

warehouse_code
required
string

Warehouse code from which the pickup will be requested.

qty
required
number <int64>

Quantity of packages

contact_name
required
string

Name of the contact responsible for the pickup.

contact_phone
required
string

Number phone of the contact responsible for the pickup.

warehouse_contact_email
string <email>

Email of the contact responsible for the pickup at the warehouse.

range_time
required
string

Range time for the pickup (Ej: 13:00 - 14:00)

pick_up_date
required
string <date>

Date of pickup in format AAAA-MM-DD.

information
string <= 250 characters

Aditional information to add to the pickup.

weight
required
integer

Weight (Kg) of the packages.

size
required
string

Size of the packages (xs, s, m, l, c)

width
integer

Width of the packages. Required when the size is "c"

length
integer

Length of the packages. Required when the size is "c"

height
integer

Height of the packages. Required when the size is "c"

description
string <= 250 characters

Description of the packages. Required when the size is "c"

Responses

Request samples

Content type
multipart/form-data
{
  "carrier_code": "BLX",
  "warehouse_code": "bod_ruka1",
  "weight": 5,
  "qty": 4,
  "contact_name": "Usuario Bodega",
  "contact_phone": 987654321,
  "warehouse_contact_email": "contacto@bodega.com",
  "range_time": "13:00 - 14:00",
  "pick_up_date": "2026-03-01",
  "size": "c",
  "width": 80,
  "length": 80,
  "height": 80,
  "information": "Este es un retiro",
  "description": "Requerido porque es tipo c"
}

Response samples

Content type
application/json
{
  • "code": 201,
  • "data": {
    }
}

Create Return Pickup as a Company/Seller

Endpoint to create return pickup as a Company/Seller. The response depends on the schedule of each carrier.

path Parameters
shipper_id
required
integer <int64>

ID of the Company/Seller, generated by Enviame

header Parameters
Accept
required
string
Default: application/json

Not modified

Request Body schema: application/json
carrier_code
required
string

Carrier code to which the pickup will be requested.

return_deliveries
required
Array of strings

OTs of the return deliveries.

qty
required
integer

Quantity of packages

weight
required
integer

Weight (Kg) of the packages.

required
object
pick_up_date
required
string <date>

Pickup date in format AAAA-MM-DD.

contact_name
required
string

Name of the contact responsible for the pickup.

contact_phone
required
string

Number phone of the contact responsible for the pickup.

range_time
required
string

Range time of the pickup (Ej: 13:00 - 14:00)

information
required
string <= 250 characters

Aditional information to add to the return pickup.

size
required
string

Size of the packages (xs, s, m, l, c)

width
integer

Width of the packages. Required when the size is "c"

length
integer

Length of the packages. Required when the size is "c"

height
integer

Height of the packages. Required when the size is "c"

description
string <= 250 characters

Description of the packages. Required when the size is "c"

Responses

Request samples

Content type
application/json
{
  • "carrier_code": "CHX",
  • "qty": 1,
  • "weight": 1,
  • "address": {
    },
  • "pick_up_date": "2026-01-02",
  • "contact_name": "Nombre del contacto",
  • "contact_phone": "999999999",
  • "range_time": "15:00 - 16:00",
  • "size": "c",
  • "length": 80,
  • "width": 80,
  • "height": 80,
  • "information": "Caja grande",
  • "description": "Paquete de prueba",
  • "return_deliveries": [
    ]
}

Response samples

Content type
application/json
{
  • "code": 201,
  • "data": {
    }
}

Export pickups

Export pickups to a excel file

Request Body schema: application/json
pickup_date_from
string <date>

Date From

pickup_date_to
string <date>

Date To

pickup_date
string <date>

If this parameter is set, the pickup_date_from and pickup_date_to parameters will be ignored.

updated_at_from
string <date>

Date of last update from

updated_at_to
string <date>

Date of last update to

shipper_id
integer <int64>

Shipper ID

organization_id
integer <int64>

Organization ID

carrier_code
string

Carrier code

carrier_pickup_number
string

Carrier pickup number

status_code
Array of strings
Items Enum: "scheduled" "done" "failed" "canceled"

Statuses of the pickups to export

type
string
Value: "return"

Types of pickups

Responses

Request samples

Content type
application/json
{
  • "pickup_date_from": "2019-08-24",
  • "pickup_date_to": "2019-08-24",
  • "pickup_date": "2019-08-24",
  • "updated_at_from": "2019-08-24",
  • "updated_at_to": "2019-08-24",
  • "shipper_id": 0,
  • "organization_id": 0,
  • "carrier_code": "string",
  • "carrier_pickup_number": "string",
  • "status_code": [
    ],
  • "type": "return"
}

Response samples

Content type
application/json
{}

PUDOs

List PUDOs by place

Retrieves a list of PUDOs, based on the provided place.

query Parameters
type
required
string
Enum: "store" "courier"
Example: type=store

The type of PUDOs that you want to retrieve.

place_name
required
string

Specifies the name of the smallest geographic administrative unit for the specified country. For Chile, this refers to the name of the commune; for Colombia, it corresponds to the municipality; for Peru, it refers to the name of the district. In the case of Mexico, this parameter accepts the name of any administrative division such as neighborhood, city, municipality, or state.

parent_place_name
string

required: only for Colombia and Peru.

Specifies the name of the parent administrative division of the given place for the specified country. For Chile and Peru, this refers to the name of the province; for Colombia, it corresponds to the department. In the case of Mexico, this parameter is ignored and is not necessary.

place_level_name
string
Enum: "state" "municipality" "city" "neighborhood"
Example: place_level_name=city

required: for Mexico only.

Name of the geographical subdivision corresponding to the sent place.

zip_code
string

applies: for Mexico only.

The zip code of the neighborhood. If this field is provided, it is assumed that the place corresponds to a neighborhood.

page
integer

The page number from which you want your page search results to be displayed.

limit
integer

Default 20 per page.

Number of results per page.

Responses

Response samples

Content type
application/json
Example
{
  • "status": "success",
  • "message": "PUDOs obtained successfully",
  • "paging": {
    },
  • "data": [
    ]
}

Tickets

Get all tickets

Retrieve a list of tickets.

query Parameters
delivery_id
integer <int64>

ID of the delivery

current_type
string

current type of the ticket

current_status
string

current status of the ticket

page
integer <int64>

page number to retrieve

limit
integer <int64>

number of tickets per page to retrieve

delivery_status
string

filter ticket by current delivery status

ticket_mode
string
Enum: "delivery" "return"

filter by tickets mode (delivery or return)

order_by
string
Enum: "CREATED_AT_ASC" "CREATED_AT_DESC" "LAST_MESSAGE_ASC" "LAST_MESSAGE_DESC" "WAITING_DAYS_ASC" "WAITING_DAYS_DESC"

order by a specific field. The available fields are: CREATED_AT_ASC, CREATED_AT_DESC, LAST_MESSAGE_ASC, LAST_MESSAGE_DESC, WAITING_DAYS_ASC, WAITING_DAYS_DESC

created_at_from
string

filter tickets created from a date in UTC timezone

created_at_to
string

filter tickets created to a date in UTC timezone

country
string
Enum: "CL" "PE" "CO" "MX"

filter tickets where the carrier is from the specified country

carrier
string

filter tickets by carrier code

shipper
string

filter tickets by shipper code

shipper_id
string

filter tickets by shipper id

current_status_date_from
string

filter tickets where the date of their current status is equal to or greater than a specified date in utc

current_status_date_to
string

filter tickets where the date of their current status is equal to or less than a specified date in utc

current_type_date_from
string

filter tickets where the date of their current subject is equal to or less than a specified date in utc

current_type_date_to
string

filter tickets where the date of their current subject is equal to or less than a specified date in utc

current_stage_date_from
string

filter tickets where the date of their current stage is equal to or less than a specified date in utc

current_stage_date_to
string

filter tickets where the date of their current stage is equal to or less than a specified date in utc

last_message_from
string

filter tickets where the date of their last message is equal to or less than a specified date in utc

last_message_to
string

filter tickets where the date of their last message is equal to or less than a specified date in utc

current_stage
string
Enum: "ISSUE" "COMPLAINT" "COMPENSATION" "CLOSED" "DISAGREEMENT"

filter tickets by current stage

fulfillment
boolean

filter tickets by fulfillment type

organization
string

filter tickets by organization code

organization_id
integer <int64>

filter tickets by organization id

read_client
boolean

filter tickets where the last message has been read or not by the client

read_agent
boolean

filter tickets where the last message has been read or not by the agent

Responses

Response samples

Content type
application/json
{
  • "status": "fail",
  • "message": "string",
  • "errors": [
    ]
}

Get ticket details by delivery id

Retrieve a ticket by delivery id.

path Parameters
delivery_id
required
integer <int64>

ID of the delivery

Responses

Response samples

Content type
application/json
{
  • "status": "fail",
  • "message": "string",
  • "errors": [
    ]
}

Create a message for a ticket

Create a message for a ticket.

path Parameters
delivery_id
required
integer <int64>

ID of the delivery

Request Body schema: application/json
message
string

The message to be sent.

timezone
string

The timezone of the message.

object
object

Responses

Request samples

Content type
application/json
{
  • "message": "string",
  • "timezone": "string",
  • "type": {
    },
  • "extra_fields": {
    }
}

Response samples

Content type
application/json
{
  • "status": "fail",
  • "message": "string",
  • "errors": [
    ]
}

Deliveries

Manual Status Update

Allows manual updating of a shipment's status (delivery or return). By default, this is only allowed for internal transport (INT), unless the company or organization has the external carrier configuration enabled.

path Parameters
delivery_id
required
integer

Internal shipment ID.

Request Body schema: application/json
required
object
status
required
integer

ID of the new status.

info
string

Additional information about the change.

user
string

Email of the user performing the change (optional, defaults to the token user).

date
string

Change date (YYYY-MM-DD HH:MM:SS).

object

Supporting data (optional).

Responses

Request samples

Content type
application/json
{
  • "status_change": {
    }
}

Response samples

Content type
application/json
{
  • "status": "success",
  • "message": "Status updated successfully"
}

Get delivery and return tracking

Gets the tracking of a delivery using its identifier (delivery_id, imported_id, or tracking_number).

path Parameters
identifier
required
string

delivery_id, imported_id, or tracking_number.

Responses

Response samples

Content type
application/json
{
  • "data": {
    }
}

Create delivery

Endpoint to create deliveries for a Company.

path Parameters
company_id
required
integer <int64>

Company ID, generated by Enviame

header Parameters
Accept
required
string
Default: application/json

Do not modify

Content-Type
required
string
Default: application/json

Do not modify

Request Body schema:

Create a new delivery

object
object
object
object
object
Array of objects


Allow Empty Array

Request samples

Content type
{
  • "shipping_order": {
    },
  • "shipping_origin": {
    },
  • "shipping_destination": {
    },
  • "dimensions": {
    },
  • "carrier": {
    },
  • "extra_fields": [
    ]
}

Returns

Create return

path Parameters
id_seller
required
integer

Seller ID

Request Body schema: application/json
required
object or object

Return origin (address or PUDO/agency)

required
object or object

Return destination (address or warehouse)

required
object
required
object

Responses

Request samples

Content type
application/json
Example
{
  • "origin": {
    },
  • "destination": {
    },
  • "order": {
    },
  • "carrier": {
    }
}

Response samples

Content type
application/json
{
  • "code": "success",
  • "message": "OK",
  • "data": {
    },
  • "errors": [ ]
}

Create return from an existing delivery

path Parameters
id_seller
required
integer

Seller ID

delivery_id
required
integer

Original delivery ID

Request Body schema: application/json
object
object

Responses

Request samples

Content type
application/json
{
  • "order": {
    },
  • "carrier": {
    }
}

Response samples

Content type
application/json
{
  • "code": "success",
  • "message": "OK",
  • "data": {
    },
  • "errors": [ ]
}