---
title: "Update Job Territory Conflicts"
method: PUT
path: "/jobs/{job_uid}/territory/conflicts"
---

# Update Job Territory Conflicts

`PUT /jobs/{job_uid}/territory/conflicts`

## Request

- Base URL: `https://dc-region.zuperpro.com/api`
- URL: `https://dc-region.zuperpro.com/api/jobs/{job_uid}/territory/conflicts`
- Auth: API key in header `x-api-key`

Recomputes 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.

## Path parameters

- `job_uid` string, required

## Response `200`

200

- object
  - `type` string
  - `data` object
    - `territory` object: The newly-persisted territory, expanded to its full object only if one was assigned.
    - `is_conflict` boolean
    - `conflicts` string[]

## Other responses

- `400`: 400
- `404`: 404

## Changes

- **2026-11-03** `3c21bc232e16`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/zuper/apis/zuper-pro-api/changes/jobs/:job_uid/territory/conflicts/put.md)

---

[API](https://skmtc.dev/zuper/apis/zuper-pro-api.md) - [All operations](https://skmtc.dev/zuper/apis/zuper-pro-api/llms.txt) - [OpenAPI document](https://skmtc.dev/zuper/apis/zuper-pro-api/revisions/3c21bc232e16?raw)