Skip to main content
Route4Green
Menu

How it works

Route4Green is an API service. Your system stays the source of data and the place decisions are issued. Route4Green does the route computation.

A depot yard in daylight, trucks parked waiting to load

Four steps

  1. 1. Get an API key

    Request a trial, we get in touch and issue a test key. Keys are delivered over a private channel, never on this site.

  2. 2. Push your data in

    Declare vehicles and vehicle plans, then push orders and drop points. If you already run a TMS, this is usually a background sync job.

  3. 3. Run an optimisation job

    Create a job with your constraints: delivery windows, payload, maximum stops per run. Jobs run asynchronously because the problem is large.

  4. 4. Read the result

    Poll the job, or register a webhook and get called back when it finishes. The result gives you stop order per vehicle plus the plan metrics.

How long integration really takes

It depends on how clean your order data already is. For a system that holds normalised drop points with coordinates, the API work is a few days. The longer part is usually address normalisation and reconciling the vehicle list. We say this up front because it is the step most often underestimated.

A dispatcher standing beside a truck, checking a list of drop points

What does not exist yet, stated plainly

  1. 01There is no self-service sandbox. Test keys are issued by hand after a conversation, not automatically on signup.
  2. 02There are no per-language SDKs yet. Today it is REST plus the public documentation on this site.
  3. 03No official price list has been published. We discuss volume and a fitting rate directly with you.

Read the docs first, decide after

Every partner-facing endpoint group is public. No signup needed to read them.

Open the API docsRequest a trial