Availability

POST /availability answers whether Govza can take a delivery from a pickup right now. Call it at checkout to decide whether to offer Govza delivery. Nothing is created or reserved.

curl -X POST https://api.govza.app/v1/delivery/availability \
  -H "Authorization: Bearer $GOVZA_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "pickup":   { "latitude": 43.342439, "longitude": 45.693597 },
    "dropoffs": [{ "latitude": 43.320872, "longitude": 45.691756 }]
  }'

{
  "success": true,
  "data": {
    "available": true,
    "pickup": { "in_service_area": true },
    "dropoffs": [{ "in_service_area": true }],
    "couriers": { "status": "available", "pickup_eta": 6 },
    "reasons": [],
    "checked_at": "2026-10-05T12:00:00.000Z"
  }
}

Only coordinates are needed. dropoffs is optional.

Service area

in_service_area is reported for the pickup and for each dropoff, in request order. An order is accepted when at least one of its points is inside the service area, so a single dropoff outside it is not a refusal.

Couriers

couriers.status describes free couriers near the pickup:

Status	Meaning
`available`	Free couriers nearby outnumber the orders already waiting there.
`limited`	Someone is free, but waiting orders may take them first. Expect a longer wait.
`unavailable`	No courier is free near the pickup.

pickup_eta estimates how many minutes a courier would take to reach the pickup if the order were created now: the nearest free courier’s driving time plus the usual time to accept. It is null when the status is unavailable.

The overall answer

available is true when an order would be accepted and a courier is free — limited included. When it is false, reasons says why:

outside_service_area — no point is inside the service area; creating the order will be rejected;
no_couriers_nearby — nobody is free near the pickup right now.