Title: OpenApi Error E613200: Too many profile objects in fleet.profiles

Symptom 1

You get an OpenApi validation error with status 400 and code E613200 when trying to submit a routing problem.

### Symptom 2

The error message includes this detail:

<br />"[Path '/fleet/profiles'] Array is too long: must have at most 5 elements but instance has 260 elements"<br />

### Symptom 3

You cannot submit the request until the number of profile objects in fleet.profiles is reduced.

---

### Quick Answer

The error E613200 means your request includes more than 5 profile objects in the fleet.profiles array. The system allows a maximum of 5. To resolve, reduce the number of profiles to meet the API’s requirement and ensure no duplicates or unnecessary entries.

---

### How to Fix It

1. Review your fleet.profiles array

Open the JSON payload you are submitting and locate the fleet.profiles array.

1. Ensure the array has 5 or fewer entries

Remove or consolidate entries in the profiles array if the count is above 5.

1. Re-use consistent profile types

If different vehicle types have the same routing configuration, re-use the same profile name.

1. Move unique differences to the types array

Settings like capacity, amount, or shifts should be set under fleet.types, not profiles.

1. Resubmit the request

After modifying to meet the 5-profiles limit, send the request again.

1. Verify the API response

Ensure that the request now passes validation and the problem is submitted successfully.

---

### Applies To

HERE Tour Planning API
Submitting Vehicle Routing Problems
Synchronous or asynchronous problem submissions
JSON payloads with a large fleet.profiles array

---

### Tags

OpenApi error E613200
HERE Tour Planning
Too many profile entries
vehicle routing problems
API validation error
fleet configuration