Welcome to the Urbano Express REST API documentation. This API will allow you to integrate your systems with our logistics services to manage shipments, check rates, track packages, and more.
Important: This documentation is based on our development environment. For production, replace the URLs as indicated in the Environments section.
Onboarding Process at Urbano:
This document details the steps required to integrate a new client into our logistics platform, using the available APIs for communication with Urbano Express Argentina.
1. Start of the Process and Email Chain:
To begin the integration process, credentials CAN ONLY BE REQUESTED BY YOUR ACCOUNT EXECUTIVE (from now on referred to as AE).
Your AE will be the point of contact to initiate this process and provide you with all the documentation needed for the commercial management.
Once your AE has started the process, an email chain will be set up where we will guide you through each step. The email chain must always include your AE and Integrations (integracionsistemas@urbano.com.ar) so the process flows smoothly without setbacks.
2. Testing Environment and Test Orders:
First, we will send you the credentials for our dedicated testing environment. This environment will allow you to configure and test the connection between your store and our platform before going to production. You will be able to generate test orders, print labels, and track your shipments with no real impact on our systems.
This step is key to avoiding inconsistencies and ensuring everything works correctly with the integration.
Key steps:
Initial configuration: You will need to configure your integration with our system in the testing environment.
Sending test orders: Once configured, it is essential that you send us a minimum of 5 orders generated in your store under our testing environment. These orders must be representative of the types of orders you will regularly manage (e.g. with different products, shipping addresses, etc.).
Review and validation: Our team will review these test orders to verify that the information is transmitted correctly and that there are no inconsistencies or errors in the received data.
This includes validation of:
- Recipient data (name, full address, phone, email).
- Product details (weight and dimensions are MANDATORY for each product).
3. Obtaining Production Credentials:
Once we have validated the 5 test orders sent from your testing environment and confirmed that the integration works correctly, we will proceed to send you the production credentials.
Process:
Validation confirmation: You will receive a confirmation from our team indicating that the testing orders have been successfully validated.
Credential delivery: Immediately after confirmation, we will provide you with the necessary credentials (Endpoint, Shipper Number and Password) to configure the integration in your production environment.
Production configuration: With these credentials, you will be able to replicate the successful testing environment setup in your production environment, enabling the real integration with Urbano Express Argentina.
Important considerations:
We recommend performing additional tests in production with a low volume of orders at the beginning to ensure optimal performance before operating at full volume.
For any questions or issues during the integration process, do not hesitate to contact us through the Email Chain mentioned above (always including your AE and the Integrations Team).
Important Things Before Integrating with Urbano:
Please note that once an order has been submitted it cannot be modified. The only option is to cancel it and reload it through the Customer Portal using an (.XLS) file manually.
General Description
Developed by Urbano Express, this API provides all the information needed to integrate your e-commerce with our logistics services.
Main benefits:
Logistics process automation
Real-time shipping rate quotes
Detailed shipment tracking
Pickup points and branch management
Label printing in multiple formats (A4, Z10X10, Z10X6, ZPL)
Address normalization for faster logistics
Package weight and dimensions lookup
Postal code routing
Support for multiple service types (delivery, pickup, cash on delivery, branch)
Flexible integration with multiple platforms
API Services
With our services you will have access to the following benefits:
It will return the corresponding rate according to your postal code, as well as return the "RealWeight". It will inform you if there is an error with your number and its description.
Destination postal code. Must be between 1000 and 9999
pesoEspecifico actual weight
decimal
4,2
Actual package weight in kg. Must be numeric
pesoVolumetrico volumetric weight
decimal
4,2
Volumetric weight in kg (optional). If alto, largo and ancho are provided, the system calculates the volumetric weight automatically using the shipper's aforo factor and takes the higher value between the calculated and the one sent. The final pesoReal returned is the higher value between pesoEspecifico and pesoVolumetrico
alto height
decimal
4,2
Package height in cm. Used to calculate volumetric weight
largo length
decimal
4,2
Package length in cm. Used to calculate volumetric weight
ancho width
decimal
4,2
Package width in cm. Used to calculate volumetric weight
Invalid credentials (shipper or password empty/incorrect)
ERROR
5
200
Invalid postal code (between 1000 and 9999), or pesoEspecifico missing or non-numeric
ERROR
-1
200
Internal error while processing the service
ERROR
Create Shipment Order
Creates a shipment order by specifying the recipient and their address (with an optional alternative address), a tracking code, delivery note, and observations. In Products, enter the description, dimensions, weight, value, SKU, and quantity.
Refers to the specific weight of the shipment (kg)
valor value
integer
8
Product value to insure the shipment. Optional; if omitted, assumed 0. This service must be managed with your Account Executive.
valorContrareembolso cash on delivery value
integer
8
Cash on delivery payment value. Required only for service type "B"; in that case it cannot be 0.
cantidad quantity
integer
4
Refers to the number of labels to be printed for the order
sku
string
30
SKU identifier of the product. Required only for WARE clients.
descripcionProducto product description
string
40
Refers to the product description
autentificacion
shipper
integer
-
Shipper number
password
string
-
Shipper password
destinatario
tipoDocumento document type
string
10
Refers to the type of identification of the person (DNI, LE or LC)
numeroDocumento document number
integer
10
Refers to the document number of the person
nombre name
string
40
Refers to the name of the person
email
array/string
45
Refers to the email address
telefono phone
string
40
Refers to the personal phone
celular mobile phone
string
15
Refers to the mobile phone
autorizado (array) - See recipient fields
domicilio
direccion street address
string
45
Recipient address
altura street number
string
6
Address number
piso floor
string
6
Floor of the address
departamento apartment
string
6
Apartment of the address
codigoPostal postal code
integer
4
Postal Code
localidad locality / city
string
-
Location of the address
provincia province
string
-
Province of the address
latitud latitude
string
10
Latitude location
longitud longitude
string
10
Longitude location
telefono phone
array
-
Address phone (array)
domicilioAlternativo - See address fields (all optional)
datoNumerico invoice / delivery note number
string
10
Additional numeric data
codigoSeguimiento
string
4-16
Unique identifier code of the shipment (minimum 4, maximum 16 characters)
codigoAlternativo alternative code
integer
15
Alternative code
servicio service type
string
1
Service type
observaciones observations
array
6
Additional observations (up to 6 elements, 95 characters each)
Important Notes
Service types:
E: Delivery
R: Pickup
B: Cash on delivery
F: Pick Up Point
G: Pick Up Point with cash on delivery
C: Exchange (Simultaneous Pickup and Delivery of products)
If the service is Cash on Delivery, the refund amount in the field "valorContrareembolso"cannot be 0
If the client has insurance, the "valor" field of the product cannot be 0. This service must be managed with your Account Executive.
Recipient fields are required except phone and email which can be null.
Authorized recipient fields can be null
Address fields: height, floor, apartment, longitude, latitude can be null. Address, location, province, and postal code are required.
Alternative address fields can be null.
The tracking code is required and has a maximum of 16 characters (minimum 4).
Alternative tracking code can be null.
Observations can be null. The character limit is 95 characters, maximum 2 observations.
If the order is for pick up point (service F or G), the localidad locality / city field must contain the branch code (e.g. G23), obtained from the prov_codigo field of the Branch Pick Up Points endpoint.
WAREHOUSING:
The SKU code cannot be null
The product weight can be 0
CROSS:
The product weight (package) cannot be 0
Using a Pick Up Point as destination
When the shipment must be delivered to an Urbano pick up point (service F — Pick Up Point, or G — Pick Up Point with cash on delivery), the destination address is the branch itself. Follow these steps:
Call the Branch Pick Up Points endpoint to retrieve the list of available branches and their codes.
From the response, take the prov_codigo value of the desired branch (e.g. "G23").
In the cargaCliente request:
Set servicioservice type to "F" or "G".
Set domicilio.localidadaddress · locality to the prov_codigo value obtained (e.g. "G23").
Set domicilio.provinciaaddress · province, domicilio.codigoPostaladdress · postal code and domicilio.direccionaddress · street with the branch address data from the same response.
Code examples:
cURL
curl -X POST "https://testing-apis.urbano.com.ar/cargaCliente/" \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"productos":[{"largo":10,"alto":5,"ancho":2,"peso":50,"valor":5200,"valorContrareembolso":0,"cantidad":5,"sku":"Test3","descripcionProducto":"1072-1"}],"autentificacion":{"shipper":671,"password":"MPzQG6%jfN%-#tsb=CUj"},"destinatario":{"tipoDocumento":"DNI","numeroDocumento":32222222,"nombre":"Urbano Dev Test","email":["dev-test@urbano.com.ar"],"telefono":"5492994230940","celular":"5492994230940"},"domicilio":{"direccion":"Santa Rita","altura":"9999","codigoPostal":"1657","localidad":"San Martin","provincia":"Buenos Aires"},"codigoSeguimiento":"TEST15004","servicio":"E"}'
Invalid credentials (shipper or password empty/incorrect)
ERROR
3
200
Missing tracking code or invalid quantity (must be greater than 0)
ERROR
5
200
Invalid postal code
ERROR
6
200
Invalid branch
ERROR
7
200
Special characters not allowed in tracking code (alphanumeric and "-" only)
ERROR
8
200
Tracking code already exists in the system
ERROR
9
200
Weight 0 is not allowed
ERROR
10
200
Incorrect service type or no products provided
ERROR
11
200
The value or cash-on-delivery amount cannot be negative
ERROR
400
200
Invalid SKU (does not exist in WMS), missing required document number, or empty request
ERROR
-1
200
Internal error while processing the service
ERROR
Tracking
Check the tracking according to the "codigoSeguimiento" parameter. It will return the tracking URL, as well as the movements with the check parameters, description, and date/time.
Invalid credentials (shipper or password empty/incorrect)
ERROR
4
200
Internal database error while processing the tracking query
ERROR
5
200
Postal piece not found for the provided tracking code
ERROR
-1
200
Internal error while processing the service
ERROR
Pick Up Points
Entering according to our address, it will return all available pick up points including according to your city and the corresponding parameters of "latitude", "longitude", "name", "address", "phone", "code", "cross streets", "postal code", "municipality", "location", "province", "elockers", "distance".
Invalid credentials (shipper or password empty/incorrect)
ERROR
-1
200
Internal error while processing the service
ERROR
Branch Pick Up Points
Returns the list of Urbano branches available as pickup destinations. Each branch includes its code (prov_codigo), address, coordinates, and locker availability. Use the prov_codigo value as the localidad field when creating a shipment order with service type F or G.
Fixed value: must always be sent as "%". Any other value will result in a 400 error
va_con_llc
integer
1
With locker (1) or without locker (0)
pieza
peso weight
decimal
4,2
Weight of the piece in kg
alto height
decimal
4,2
Height of the piece in cm
largo length
decimal
4,2
Length of the piece in cm
ancho width
decimal
4,2
Width of the piece in cm
Root
elockers
integer
1
Fixed value: always send as 1
Important Notes
The prov_codigo field returned by each branch in the response is the value that must be sent in the localidad field of the cargaCliente endpoint when the shipment is destined for a pick up point (branch).
Invalid credentials (shipper or password empty/incorrect)
ERROR
400
400
Cannot interpret the request (ubicacion.va_prov_codigo must be "%")
ERROR
-1
200
Internal error while processing the service
ERROR
Postal Code Router
Entering our postal code, it will return the logistics according to your code, it will inform if the query has been completed, as well as inform us about any error in the database with the error code.
This endpoint returns a PDF (not JSON). Errors are returned as plain text:
tipo missing → "Es necesario ingresar el formato de guia a imprimir (A4, Z10X10, Z10X6)."
| shipper or codSeguimiento missing → "Es necesario ingresar los datos generar la etiqueta."
Address Normalizer
Entering our address, it will return the correct address data according to our databases, this way we will get greater agility in the logistics of the shipments.
This endpoint uses status.success and status.message instead of codError.
HTTP
status.success
status.message
200
true
ok
200
false
No data found for the requested tracking code
400
false
Empty request or codigoSeguimiento required
401
false
Invalid credentials
Order Rescue
Allows requesting the rescue of pieces in transit through two modes:
Return — bulk rescue: the shipment is returned to the seller/sender. Multiple pieces can be sent in a single request.
Redirection — individual rescue: the piece is redirected to a new delivery address. Only one piece per request is allowed and the new recipient and address data are required.
La pieza ha sido rescatada correctamente The piece has been successfully rescued
OK
succeeded
Return
Solicitud de rescate de Devolucion generada correctamente Return rescue request generated successfully
OK
succeeded
Redirection
Solicitud de rescate de Redireccion generada correctamente Redirection rescue request generated successfully
OK
rejected
Both
La pieza ya tiene un Rescate existente The piece already has an existing rescue request
REJECTED
rejected
Both
La pieza no es apta para ser rescatada The piece is not eligible to be rescued
REJECTED
rejected
Redirection
La pieza no se pudo rescatar porque no tiene DESPACHO The piece could not be rescued because it has no dispatch
REJECTED
failed
Both
El proceso de rescate ha fallado, comuniquese con su Ejecutivo de Cuentas The rescue process has failed, please contact your Account Executive
ERROR
Order Cancellation
IMPORTANT: This End-Point will be deprecated by July 2026.
Allows requesting the cancellation of an order by its tracking code. The system checks whether Urbano holds the product and whether the piece is eligible for cancellation, automatically generating a rescue request in that case. Authentication is performed via HTTP headers instead of the JSON body.