Addresses
An address is sent structured into fields, and always includes coordinates. Govza does not geocode: there is no address lookup, spelling correction or fuzzy matching behind this API.
Address fields
Section titled “Address fields”| Field | Required | Notes |
|---|---|---|
latitude |
yes | −90 to 90. |
longitude |
yes | −180 to 180. |
area |
yes | City or locality. |
street |
yes | Street name, without the house number. |
building |
yes | House number, as text — "12к3" is valid. |
apartment |
no | Whole number. |
entrance |
no | Whole number. |
floor |
no | Whole number. |
intercom |
no | Door entry code. |
instructions |
no | Free text for the courier. |
{ "latitude": 43.3200, "longitude": 45.7000, "area": "Грозный", "street": "улица Мира", "building": "12", "apartment": 4, "entrance": 2, "floor": 3, "intercom": "12К4590", "instructions": "Entrance from the courtyard"}Coordinates and text
Section titled “Coordinates and text”Coordinates determine the route and the price. The text fields are what the courier reads on the way. The two are not reconciled against each other, so make sure they describe the same place.
If coordinates fall outside a served area, the order is rejected at creation.
Apartment, entrance and floor
Section titled “Apartment, entrance and floor”These fields accept whole numbers only. A value such as "12A" is rejected:
{ "field": "dropoffs.0.address.apartment", "message": "must be a whole number; put anything else in address.instructions"}Put anything that does not fit a number into instructions, which the courier
sees:
{ "apartment": 12, "instructions": "Block A, entrance from the courtyard"}Contacts
Section titled “Contacts”The pickup and every dropoff carry a contact with a phone number:
{ "value": "+79280003396", "name": "Musa" }Phone numbers are normalised on our side, so the formatting of the value does
not matter. name is optional but helps the courier.