# Cloud4Log carrier pilot

> Prepare a fleet workspace to retrieve Cloud4Log delivery notes and let assigned drivers open archived originals.

The Cloud4Log carrier integration is a prepared pilot. It needs provisioned API access and live validation before use with a real fleet. It is not a certification claim.

Fleet dispatch can find a delivery note using the sender's GLN and delivery note number, optionally narrowed by the Cloud4Log order number. Dispatch explicitly selects a result and the order's pickup and delivery stops. Maxmove imports the original PDF into its document archive. Assigned drivers can open the archived PDF in the driver app.

## Provisioning

Ask Maxmove support to provision a Cloud4Log machine-to-machine API client for your workspace, environment and carrier site. Credentials remain on the server. The fleet's Cloud4Log administrator must grant the relevant site roles and permissions.

The pilot uses the official OAuth client-credentials flow and these read operations:

| Operation | Cloud4Log API v2 path |
| --- | --- |
| Check accessible carrier sites | `GET /me/organization-sites` |
| Find delivery notes | `POST /organization-sites/{site}/carrier/delivery-notes/lookup` |
| Retrieve the complete original PDF | `GET /organization-sites/{site}/carrier/delivery-notes/{note}/complete-pdf` |

The required permissions are `user_me_read`, `carrier_delivery_note_keys_lookup` and `carrier_delivery_notes_complete_pdf_read`. A successful site check does not prove that a particular note can be found or downloaded. Verify those permissions with an authorized test document.

See the [official OAuth documentation](https://github.com/JR-2022/C4L/blob/main/OAuth2-Authentication.md) and [combined API reference](https://api.cloud4log.com/api-docs-combined/). Confirm onboarding, certification and commercial terms directly with Cloud4Log.

## Document behavior

An import preserves the provider's original bytes. **Import current PDF** retrieves the provider's current version; changed bytes create another archived revision. **Refresh list** only updates Maxmove's archive status. Neither action checks goods in or out, records acceptance or creates a Maxmove signature.

References are private to their workspace. Every read checks current order participation and assignment. Removing a reference retains the archived original. Switching the configured provider environment or site does not retarget an existing reference.

Cloud4Log originals use the dashboard and driver document flow. They are not exposed through the public delivery REST API or its consignment-note endpoints. The [consignment notes guide](https://maxmove.com/en/developers/docs/guides/consignment-notes) covers Maxmove CMR and German freight notes separately.

Cloud4Log wallet invitations, QR handover, check-in, checkout and automatic receipt notifications are not part of this pilot. Continue those steps in the established Cloud4Log process. Opening a PDF in Maxmove requires an internet connection.

For the fleet setup and document controls, see [Cloud4Log delivery notes](https://maxmove.com/en/help/delivery-fleet/cloud4log-delivery-notes).

---

Source: https://maxmove.com/en/developers/docs/guides/cloud4log