In this JSON API you will find REST methods for creating, editing and sharing delivery note information. Roles and rights can be managed via the admin tool and can be assigned to users per company, location or function-related. In the area of contract logistics, rights can be temporarily passed on to partner companies. Delivery bill data can be linked to each other through assignments at process level or delimited from each other at company level.

Here are the available API documentation versions:

• API Documentation v2
  Stable version for existing integrations.

• API Documentation v3
  New version with pagination support and additional features.

• Combined API Documentation (v2 + v3)
  Useful if you need to work with both versions at the same time.

If you want to test the APIs through the Swagger-UI or Scalar-UI, you can authorize yourself in two ways:

1. Legacy API Key – Enter your API key directly.
2. Bearer Token (Keycloak Authentication) –
   • Obtain a token using the Keycloak login flow.
   • Remove the Bearer prefix before pasting it into the authorization field.
   • Keep in mind: Bearer tokens are valid for only 5 minutes.

Solution overview:

• Solution Overview Diagram
  High-level architecture diagram of the Cloud4Log system.

In the API, you can set up and use the following roles and functions:

1. consignor/ manufacturer
2. carrier / forwarder, contract logistics provider
3. consignee/ receiver, stationary trade

• Outgoing goods (consignor)
• Carrier / contract logistics
• Logistician / Driver
• Incoming goods (consignee)

• Admin Organizational Unit (OU)
• Admin Location
• User OU or location
• Driver / carrier