Turn the RTPD posting declaration portal into an API

What you can build on the RTPD portal

• Get posting declarations

  Build this

  Reads the Declarations list of one company account, filtered by status, country of posting or end date, with each declaration's driver, period and plates.

  Takes

  Company account, status (optional), country of posting (optional), end date before (optional)

  Returns

  Declaration number, driver, country of posting, start date, end date, type of operations, type of carriage, plate numbers, status, submission date, last update

• Check requests for documents

  Build this

  Reads the requests for documents that host Member State authorities sent to one company account, with the documents asked for and what has been sent.

  Takes

  Company account, received since (optional)

  Returns

  Requesting country, driver, period covered, date of request, documents requested, documents sent, new chat messages

• Get driver profiles

  Build this

  Reads the Drivers list of one company account, with each driver's licence, identification document and employment contract details.

  Takes

  Company account, driver name (optional)

  Returns

  Name, date of birth, driving licence number, document type, document number, issuing country, expiry date, contract start date, applicable law

• Extend a declaration's end date

  Build this

  Opens a submitted declaration that was made for less than 6 months, changes its end date and submits the update to the host authority.

  Takes

  Company account, declaration number, new end date

  Returns

  Declaration number, driver, country of posting, start date, end date, status, last update

Automate the RTPD portal 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.

• New requests for documents, with their 8-week deadline

  Build this

  Starts

  Every weekday at 8:00

  Step 1

  For each company account you name, check the requests for documents.

  Step 2

  Keep the requests that were not there on the last run.

  Step 3

  Email you each one with the requesting country, driver, documents requested and the date 8 weeks after the request.

• Submitted declarations ending in the next 7 days

  Build this

  Starts

  Every Monday at 7:00

  Step 1

  For each company account, get the declarations in Submitted status.

  Step 2

  Keep the ones whose end date falls in the next 7 days.

  Step 3

  Email you the list grouped by country of posting, so someone extends or copies each one in time.

• Driver identity documents close to expiry

  Build this

  Starts

  On the 1st of every month at 9:00

  Step 1

  For each company account, get the driver profiles.

  Step 2

  Keep the drivers whose identification document expires within 60 days.

  Step 3

  Post name, document type, document number and expiry date to your HR system's 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 “Get posting declarations” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "www.postingdeclaration.eu/get_posting_declarations",
    "input": {
      "company_account": "Acme Logistics",
      "status": "Submitted",
      "country_of_posting": "France"
    }
  }'

{
  "status": "completed",
  "data": {
    "company_account": "Acme Logistics",
    "declarations": [
      {
        "declaration_number": "48213",
        "driver": "Driver A. Example",
        "country_of_posting": "France",
        "start_date": "2026-09-01",
        "end_date": "2026-11-30",
        "type_of_operations": [
          "International carriage"
        ],
        "type_of_carriage": "Carriage of goods",
        "plate_numbers": [
          "AB-123-CD"
        ],
        "status": "Submitted",
        "submission_date": "2026-08-28T09:14:00Z",
        "last_update": "2026-10-02T15:40:00Z"
      }
    ],
    "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.

The RTPD portal’s own options

The RTPD portal has a REST API for economic operators that covers drivers, vehicle plate numbers and posting declarations, through a company API key valid for 1 year. Its documentation lists no endpoints for requests for documents, so those are read and answered in the portal itself. Drivers can also be uploaded from an Excel template.

Read on November 12, 2026: RTPD API for Economic Operators, RTPD portal help and FAQ.

Signing in to the RTPD portal

The RTPD portal signs people in with EU Login: each user needs a personal EU Login account, and the portal keeps no passwords of its own. One user can switch between up to 100 company accounts. With Fous you sign in once through the portal's own EU Login sign-in with your own account; the login is sealed with AES-256, and code and AI agents never see it.

Worth knowing

One declaration per driver and country

Each declaration covers one driver in one Member State, for 1 day to 6 months, and cannot be submitted more than 60 days before it starts. Only one made for less than 6 months can be extended; otherwise you copy it.

8 weeks to answer a request for documents

The 8 weeks run from the date of the request, and start again when the authority asks for more documents. Documents can be sent one by one, at most 4MB each; zip a file whose format is not accepted.

Profile changes reach live declarations

Changing a driver's profile updates all on-going declarations, except first name, last name and birth date. One edit to a licence or contract detail reaches every live declaration of that driver.

Local time on screen, UTC in the PDF

The portal shows dates in your local time zone, while the declaration PDF prints them in UTC. Use one time zone when you match a declaration's dates against your own records.

More in Government: Southern, Eastern and Nordic Europe, EU

• Telemaco
• EUDR Information System
• EU Funding & Tenders Portal
• Cégkapu
• UETS
• EPREL
• e-Zamówienia
• Mercell
• NEN
• Plataforma de Contratación del Sector Público
• Prozorro
• TRACES NT
• e-ΕΦΚΑ
• PUE ZUS
• Segurança Social Direta
• SGK İşveren Sistemi
• Sociálna poisťovňa e-Služby
• Dijital Vergi Dairesi
• myAADE
• Portal das Finanças
• e-Beyanname

Other industries: Planning Portal, USA North 811, Uniform Collateral Data Portal, PostalOne, BidNet Direct, CDTFA Online Services.