Update Job Territory Conflicts
Changed onRecomputes territory matching for the job's current address/assignment and PERSISTS the result onto the job's service_territory field. Unlike the GET on this same path (read-only), this is a real write. No request body is read beyond the job_uid path parameter — it recomputes from the job's existing data, it does not accept new address/assignment values directly.
put/jobs/{job_uid}/territory/conflicts
Request
- Base URLhttps://dc-region.zuperpro.com/api
- URLhttps://dc-region.zuperpro.com/api/jobs/{job_uid}/territory/conflicts
- AuthAPI key in header x-api-key
Path parameters
job_uidstring required
Response
200
Example response
{
"type": "success"
}Changes
- info
endpoint added
- info