This environment is your pre-production or sandbox to try out the capabilities of our API and to test the integration with your pre-production environment(s):

❗️

Do not use real data

We highly recommend not using real data in the sandbox environment.

🚧

Different environments, different data

The production and testing environments are independent environments where each one manages its own data. Accounts, credentials, parcels and webhook subscriptions exist in one or the other, never both. Sandbox credentials will not authenticate against production, and a parcel id from one environment is not found in the other.

Getting access

Sandbox accounts are created by us, not self-service. If you cannot generate
test keys from the panel, or the sandbox login does not accept your production
password, that is expected — ask us and we will set the account up. It is the
single most common reason an integration stalls before it starts.

What you can test end to end

Authentication, shipping type discovery, estimates, parcel creation, shipment
requests, cancellation, webhook subscriptions and tracking all behave as they do
in production.

Simulate express deliveries

To make the testing environment as similar to production as possible, we have developed a service to simulate drivers' behavior, moving around the city and picking up the parcels near them.

Once a simulated driver is assigned, it takes some time to reach the pick-up
location, and from there the parcel advances through the states of a normal
express delivery, including a fake proof of delivery.

🚧

The simulator is a test fixture, not the real fleet

It is best effort. A parcel can stall part way through — waiting for a driver
that never arrives, or sitting in delivering — without that meaning anything
is wrong with your integration. If a test parcel has not moved for a while,
it is the simulator, not your code.

Do not build your acceptance tests around the assumption that every sandbox
parcel reaches delivered on its own, and do not read a stalled sandbox
parcel as a production behaviour you need to handle. When you need a parcel
driven to a particular state, ask us rather than waiting.

Simulate same-day or next-day deliveries, and failure states

The simulator covers the happy path of express deliveries. The exception flows —
incident, undelivered, returning, returned, a failed pickup — and the
same-day and next-day modalities are not reproducible on your own.

We can drive a parcel to the state you need so you can verify your handling of
it. Ask us with your client id, the parcel id, and the state you want to reach.
It is worth doing before you go live: the exception flows are exactly the ones
your integration will handle worst if it has never seen them.

Where are these drivers located?

We have several drivers in different cities. You can't create deliveries outside.

Lima

Santiago de Chile

Buenos aires

Bogotá