If you are unsure whether your company already has a RIO account or which colleague has the necessary rights to invite you to the existing RIO account, please contact the RIO Customer Care Hotline via email at support@rio.cloud or by phone at 00800 / 22550746 (Monday to Friday from 8:00 AM to 4:30 PM).
Each company can register with RIO once and then invite any number of users to the RIO account.
Yes, you can have multiple DUNS numbers for your company.
The process follows these steps:
You can find example request in our documentation. To test the API with data from your client, please contact your client.
We recommend using the API as follows:
HTTP Status 200).aggregated_modified_after parameter set to the cut-off time of the previous day. aggregated_modified_after to 2025-01-14T11:30:00.000Z (12:30 CET the previous day).
There are several ways for receiving and forwarding time window IDs:
access_code)access_code)Customs information can be found on the article level (type of content is article) in the nested structure of goods. The article usually has a property country_of_origin containing both country_code and a dutiable_goods flag.
Dangerous goods information can be found on the article level (type of content is article) in the nested structure of goods. The article can have a property dangerous_goods_information containing the undg, a description and exception_regulation.
In most cases, goods are organized in a two-level structure of handling units, consisting of outer and inner packaging, with the articles contained inside. However, transport orders can also occur with a deeper structures of nested handling units. Therefore, the recommendation is to either implement the hierarchy handling in a fully recursive way that can support arbitrary depth, or to design the solution to handle at least 4–5 levels of nesting.
The transport status messages submitted via Order Exchange will be supplemented by RIO with the following data:
namesupplier_code (DE: Lieferantennummer)duns_numberaccess_code_at_unloading (if available based on the transport order lifecycle)transport_chain_reference (if available based on the transport order lifecycle)ship_from: The place of loadingship_to: The place of unloadingIn the unlikely event of a failure, we recommend designing your system to poll the data multiple times throughout the day, or at least during critical periods (e.g., between 12:00 am and 01:00 pm Europe/Berlin). This helps ensure timely data retrieval and reduces the impact of temporary disruptions.
Our API follows REST standards and returns 4xx status codes for client request errors and 5xx status codes for server errors.
You can manually copy and paste transport orders from webTMS into your system by following these steps:
To manually export transport orders from webTMS in CSV format, follow these steps:
If you continue to encounter problems, you can reach out to RIO support via email at support@rio.cloud or by using our contact form.