The API documentation on providing coordinates during job creation reads “The coordinates object contains latitude and longitude coordinates which are integer values” (emphasis mine). This should read floating point values.
Additionally, the job creation example in the above section does not include coordinates, so it’s not clear what the “coordinates” object should look like (the only way to find out is to review the announcement Job Creation with Lat/Long coordinates). Presumably the API docs should be self contained.
It’s especially important include this info in the docs themselves since the way coordinates are represented during job creation is different than how coordinates are represented elsewhere in the API:
- during job creation coordinates are represented as an object with field names
- when fetching a created job, a coordinate object is not used, and the underlying terms are referred to as
longitude(similarly with webhook updates).
- for the
areasroute coordinate points are encoded as floating point tuple.
- still elsewhere