Attention: This site does not support the current version of your web browser. To get the best possible experience using our website we recommend that you upgrade to a newer version or install another browser

Person Notes


The Person Notes resource defines the interface for a list of notes attached to an entity (e.g., person, relationship). The Person Notes resource is to be considered an embedded resource, and any links to this resource are to be treated as embedded links.

Data Formats


If you make a GET request, specify the desired data format using the Accept header.


If you POST something, specify the data format using the Content-Type header.


Name Type Description
Authorization header The authorization carrying the OAuth 2.0 access token. See OAuth 2.0 Bearer Tokens.
X-Reason header Header giving the reason for creating a note.
pid path The id of the person.
access_token query The ID of the OAuth 2 access token used for identification and authorization of the user (and agent) making the request.


GET - Read the list of notes.

Status Codes
200 Upon a successful read.
204 Upon a successful query with no results.
301 If the person has been merged into another person.
404 The specified entity has been moved, deleted, or otherwise not found.
404 If the person is not found.
410 If the person has been deleted.
429 If the request was throttled.

POST - Create a note.

Status Codes
201 The creation of the note was successful. Expect a location header specifying the link to the note.
400 If the request was unable to be understood by the application.
404 If the request was throttled.
410 If the person has been merged or deleted.
429 If the request was throttled.

Example Requests

Create Note How to create a note on a person.
Read Notes How to read the list of notes on a person.
Update Note How to update a note.

Select a language