Job creation docs incorrectly indicate company / firstname / lastname are required

Bug Reporting
1

The job payload field section of the job creation endpoint includes the following descriptions:

contact: Contact information at the origin. Either (firstname AND lastname) OR (company) are required.
firstname: Mandatory if company is empty.
lastname: Mandatory if company is empty.
company: Mandatory if firstname or lastname are empty.

Based on our testing none of the above fields are actually required (for both the pickups or dropoffs sections).

As a concrete example, the following job creation request results in successful job creation:

{
    "job": {
        "pickups": [
            {
                "address": "2 Tulse Hill, London SW2 2TP, UK",
                "contact": {
                    "phone": "+34666777555"
                }
            }
        ],
        "dropoffs": [
            {
                "package_type": "medium",
                "address": "1 Montego Close Railton Road, London SE24 0LH, UK",
                "contact": {
                    "phone": "+34666777555"
                }
            }
        ]
    }
}
2

Hello @mirek,

Indeed, this request does not currently return an error when these fields are missing.

When designing the API, we decided not to block all requests where none of these fields were included, because in some very specific use cases, some customers could not provide any of these information.

However, we encourage you to fill out these fields, as those are very valuable information for our couriers and in many cases they will not be able to complete the delivery without them.

3

Sure thing, and makes sense. My only suggestion would be to update the API docs accordingly, as currently they’re inaccurate :slight_smile:

4

Hi @mirek,

Thank you for your message.

However, we wrote it this way in our documentation because we want these fields to be filled out whenever it is possible for the client (most of the time).