Skip to main content

🧪 UAT / test environment

Early‑Access API

🚧 Heads‑up! This is our next‑generation API and it’s still under active development.

How you can help

  1. Try it out in non‑production environments first.
  2. Report issues or request features by mailing [email protected]

Thank you for partnering with us to shape the future of our platform!

Base URL


https://uat.dockflow.com/v3

UAT mirrors the production API surface.
The only difference is authentication and the optional mock‑tracking features described below.

EnvironmentHostRequired token prefix
Productionapi.dockflow.comprod_…
UAT (sandbox)uat.dockflow.comuat_…

Production keys are rejected on UAT, and vice versa.


Mock tracking

When posting a tradeflow to /downstream/tradeflows in UAT, include the field mock_tracking.
Dockflow will automatically generate events that simulate real‑world progress.

Basic format

{
"tradeflow_reference": "PO4564268",
"port_of_loading": "BEANR",
"port_of_discharge": "USLAX",

"mock_tracking": {
"scenario": "ocean_basic"
}
}
PropertyTypeDefaultDescription
scenariostringSelects the event template (table below).

Required fields

When using mock_tracking, you must also provide:

  • port_of_loading — 5-character UN/LOCODE (e.g., BEANR)
  • port_of_discharge — 5-character UN/LOCODE (e.g., USLAX)

If no container_reference is provided, the system will use a random existing container from the database.

Predefined scenarios

CodeEvents that will be generated
ocean_basicVessel departure (actual) → Estimated arrival (predicted)

Additional scenarios may be added in future versions.

Custom events

For full control, send your own events array (see Tradeflows API). If both events and mock_tracking.scenario are present, the custom events are appended after the mock sequence.


Usage example

curl -X POST https://uat.dockflow.com/v3/downstream/tradeflows \
-H "Authorization: uat_e7d51f4d5719462d958e4b31" \
-H "Content-Type: application/json" \
-d '{
"tradeflow_reference": "PO4564268",
"port_of_loading": "BEANR",
"port_of_discharge": "USLAX",
"mock_tracking": { "scenario": "ocean_basic" }
}'

Response:

{
"status": "queued",
"tradeflows": [{ "tradeflow_reference": "PO4564268", "created": true }]
}

Data retention & limits

  • Retention: data is wiped every Monday 00:00 UTC.
  • Rate limits: identical to production (bursts of 120 req/min, 5 MB payload).
  • E‑mails & webhooks: disabled; mock events are visible via the API only.

Use UAT to validate integrations safely before switching to production. For questions about tokens or mock scenarios, contact Dockflow support.