---
title: "Create a note"
method: POST
path: "/v2/property_claims/{property_claim_id}/notes"
tags: ["Property Claim"]
---

# Create a note

`POST /v2/property_claims/{property_claim_id}/notes`

## Headers

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

## Request body

- union — A `Note` must have at least a `title` or `text` that is not null. `text` is expected to be in [Markdown](https://www.markdownguide.org/basic-syntax/) format. Some common pitfalls: - Paragraphs are expected to be separated by two newlines, or \\n\\n. - Some features, such as \`code blocks\`, are not fully supported by our system at this time. - For security, we do not allow HTML in the text. Please refer to [GFM](https://github.github.com/gfm/) for the precise Markdown specification we use, or contact our support team if you have questions.
  - object
    - `title` string, required — The title of the `Note`.
    - `text` string, nullable — The contents of the `Note`. (a valid Markdown string)
  - object
    - `title` string, nullable — The title of the `Note`.
    - `text` string, required — The contents of the `Note`. (a valid Markdown string)

## Response `200`

The `Note` that was created successfully.

- NoteResponse
  - `id` integer, required
  - `client_created` string, date-time, nullable, required — `client_created` is the timestamp at which a user's client created the model. It is typically earlier than the `server_created` timestamp, but since this timestamp is provided by the client and not verified, it could have been altered to any time in the past or future. The Encircle mobile app allows users to work offline. This timestamp captures the time that the model was created locally, regardless of when the client goes back online. Encircle web and mobile applications typically display the earlier of the `client_created` and `server_created` timestamps. Refer to `server_created` for the timestamp recorded by Encircle servers. A [RFC 3339](https://tools.ietf.org/html/rfc3339#section-5.6) compliant `date-time` string.
  - `server_created` string, date-time, required — `server_created` is the timestamp at which Encircle servers created the model. It is typically later than the `client_created` timestamp (unless the client had provided an inaccurate timestamp). This unbounded delay depends on how long the client took to sync with the server. The Encircle mobile app allows users to work offline, which means that a client can create a model, wait a day, then go online and sync with Encircle servers. The server's timestamp would be delayed by about a day after the model's creation on the client. Refer to `client_created` for the client provided timestamp. A [RFC 3339](https://tools.ietf.org/html/rfc3339#section-5.6) compliant `date-time` string.
  - `creator` ActorResponse, required
    - `actor_type` 'User', required
    - `actor_identifier` string, required — A string that identifies the actor. The identifier is an email address when the `actor_type` is `User`.
  - `title` string, nullable, required — The title of the `Note`.
  - `text` string, nullable, required — The contents of the `Note`.

## Other responses

- `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)