Get your DAKOSY EMP port order status through an API

What you can build on EMP

• Check port order status

  Build this

  Reads EMP's status information for the container numbers or Port Order references you give, with the current status and customs references.

  Takes

  Container numbers or Port Order references

  Returns

  Reference, container number, status, status code, terminal, MRN, status time

• List port orders that are not released

  Build this

  Reads the port order status module in the EMP web application, filtered to Port Orders whose customs status is Not released, Loading stopped or Rejected.

  Takes

  Terminal (optional), vessel name (optional)

  Returns

  Port Order reference, container number, status, status code, terminal, vessel name, status time

• Get the customs status of an export MRN

  Build this

  Reads the status of an export MRN in EMP, from Goods presentation expected through Exit ongoing to Export completed, Rejected or Inspection.

  Takes

  MRN

  Returns

  MRN, status, status code, related Port Order references, status time

Automate EMP with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

• Containers still Not released before the vessel closes

  Build this

  Starts

  When your system calls the workflow's webhook with the containers booked on a vessel

  Step 1

  Check the port order status of each container number your system sends.

  Step 2

  Keep the containers whose status is not Released.

  Step 3

  Email you the list with reference, status, terminal and MRN.

• Port Orders newly Not released, Loading stopped or Rejected

  Build this

  Starts

  Every hour

  Step 1

  List the Port Orders whose status is Not released, Loading stopped or Rejected.

  Step 2

  Keep the ones that were not on the last run, or whose status changed since then.

  Step 3

  Post each one with reference, container number, status and terminal to your webhook.

• Completed exports handed to your ERP

  Build this

  Starts

  Every weekday at 18:00

  Step 1

  For each export MRN your team lists, get its customs status in EMP.

  Step 2

  Keep the MRNs that changed to Export completed since the last run.

  Step 3

  Post MRN, status, Port Order references and status time to your ERP webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Check port order status” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "emp.dakosy.de/check_port_order_status",
    "input": {
      "references": [
        "ACMU4821937",
        "NWDU1650284"
      ]
    }
  }'

{
  "status": "completed",
  "data": {
    "results": [
      {
        "reference": "S26K048213",
        "container_number": "ACMU4821937",
        "status": "Released",
        "status_code": "0002",
        "terminal": "CTB",
        "mrn": "26DE485100004821A7",
        "status_time": "2026-11-12T06:42:00+01:00"
      }
    ],
    "count": 1
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

EMP’s own options

EMP takes Port Orders through DAKOSY's Port Order XML interface, with published XSD schemas, which replaces the older HDS, GM01 and GPO formats. DAKOSY says status information can be received by email, EDI, web or API, and EMP is fully covered in its forwarding software DAKOSY GE. Without those, authorised users work in the EMP web application.

Read on November 12, 2026: Interfaces for the seaport (developer documentation), EMP / ZAPP, Port of Hamburg export.

Signing in to EMP

EMP opens on its own Login page, with a link to a public Status Request for container and Port Order references that needs no sign-in. DAKOSY describes EMP as one log-in for all former ZAPP functions, for authorised users. With Fous you sign in once through EMP's own sign-in with your own account: the login is sealed with AES-256, never returned by the API or written to logs, and code and AI agents never see it.

Worth knowing

Released can turn back to Not released

At HHLA terminals and Eurogate, a released consolidation container is validated again when it arrives. Its status can then return to Not released, and S-numbers that do not match are cancelled and declared again.

MIT ended on 1 July 2026

Since 1 July 2026 the declaration type MIT is not allowed and DUX in GM01 format can no longer be used. CTA, CTB, CTT and Eurogate do not accept DUX with MRN.

DUX without MRN needs more data

Since 5 May 2026 a Port Order of type DUX without MRN also needs the carrier's EORI, the transport document, the UN number for dangerous goods and the Verfahrensübergang (procedure transfer).

Why an S-number gets no release

Customs may have ordered a measure, ATLAS may have rejected the data, the goods may not be in the terminal's custody, or the terminal may have no loading permission. A rejected declaration is sent again with corrected data.

More in Logistics: ocean carriers, terminals and ports

• myDCLI
• PayCargo
• APM Terminals TERMPoint
• Georgia Ports WebAccess
• 易港通
• INTTRA
• CMA CGM eBusiness
• COSCO SHIPPING Lines eBusiness
• Maersk.com
• myMSC
• ONE eCommerce
• ShipmentLink
• eModal
• PortTruckPass
• Destin8
• Portbase
• PierPASS
• Forecast by Tideworks
• 1-Stop Vehicle Booking System

Other industries: CassPort, TWX-21, ABS MyFreedom, PropertyMe, myCHEP, Syndigo CXH.