---
title: "Unassign a user from a property claim"
method: DELETE
path: "/v1/property_claims/{property_claim_id}/assignments"
tags: ["Property Claim"]
---

# Unassign a user from a property claim

`DELETE /v1/property_claims/{property_claim_id}/assignments`

## Headers

- `X-Encircle-Attribution` string
- `X-Encircle-Request` string

## Request body

- PropertyClaimAssignmentRequest — A `PropertyClaimAssignment` represents an assignment of a `User` to a `PropertyClaim`. When the `User` is assigned to a `PropertyClaim`, access is granted to the `User`.
  - `id` string, required — This is the email address of the person accepting/receiving the claim assignment.

## Response `200`

The 'User' was unassigned to the property claim successfully.

- UserResponse — `User`s identify user accounts in the Encircle system including the ID of their organization. Any email address corresponds to at most one `User` object.
  - `id` string, required
  - `organization_id` string, uuid — A [RFC 4122](https://tools.ietf.org/html/rfc4122#section-3) compliant UUID in lowercase hexadecimal.

## Other responses

- `202` — The 'User' was not assigned to the property claim already.
- `400` — Error processing request.
- `401` — Authentication error.
- `404` — Requested resource does not exist.

---

[API](https://skmtc.net/encircleapp/apis/encircle-public-api.md) · [All operations](https://skmtc.net/encircleapp/apis/encircle-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/encircleapp/encircle-public-api/revisions/0e70222a2c6d/schema)