POST
/
notes
Create a note
curl --request POST \
  --url https://api-sandbox.synctera.com/v0/notes \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "content": "Customer was frozen to investigate fraud.",
  "metadata": {},
  "related_resource_field": "/legal_address/city",
  "related_resource_id": "7d943c51-e4ff-4e57-9558-08cab6b963c7",
  "related_resource_type": "CUSTOMER",
  "status": "RESOLVED",
  "tenant": "abcdef_ghijkl",
  "type": "NOTE"
}'
{
  "author": "Jane Smith jane@example.com",
  "content": "Customer was frozen to investigate fraud.",
  "creation_time": "2010-05-06T12:23:34.321Z",
  "id": "7d943c51-e4ff-4e57-9558-08cab6b963c7",
  "last_updated_time": "2010-05-06T12:23:34.321Z",
  "metadata": {},
  "related_resource_field": "/legal_address/city",
  "related_resource_id": "7d943c51-e4ff-4e57-9558-08cab6b963c7",
  "related_resource_type": "CUSTOMER",
  "status": "RESOLVED",
  "tenant": "abcdef_ghijkl",
  "type": "NOTE"
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

note to create

​
content
string
required

The note's text content.

Example:

"Customer was frozen to investigate fraud."

​
related_resource_id
string
required

The id of the resource that is associated with the note. This is typically a UUID. For TENANT it is a string tenant ID.

Example:

"7d943c51-e4ff-4e57-9558-08cab6b963c7"

​
related_resource_type
enum<string>
required

Type of the resource associated with the note.

Available options:
ACCOUNT,
APPLICATION,
BUSINESS,
CUSTOMER,
FILE,
SHADOW_TRANSACTION,
SNAPSHOT,
TENANT,
TRANSACTION,
USER
Example:

"CUSTOMER"

​
metadata
object

Optional field to store additional information about the resource. Intended to be used by the integrator to store non-sensitive data.

​
related_resource_field
string

🚧 Beta This is a Beta property. Feedback from the community is welcome. We may make breaking changes to this property. Path to the field in the related resource that the note pertains to. This uses a dot notation like the following: Examples:

  • a field in the resource: first_name
  • a sub-field: legal_address.city
  • nested arrays: application_details.sections[1].pages[2].items[0].answer
Example:

"/legal_address/city"

​
status
enum<string>

The state of the FEEDBACK, use this field to mark fields as RESOLVED or UNRESOLVED. This is required when creating a note with type FEEDBACK. Providing a status with note type NOTE will result in a Bad Request error.

Available options:
RESOLVED,
UNRESOLVED
Example:

"RESOLVED"

​
tenant
string

The id of the tenant containing the resource. This is relevant for Fintechs that have multiple workspaces.

Example:

"abcdef_ghijkl"

​
type
enum<string>
default:NOTE

The type of note.

Available options:
FEEDBACK,
NOTE
Example:

"NOTE"

Response

Created note

​
author
string
required

The note's author.

Example:

"Jane Smith jane@example.com"

​
content
string
required

The note's text content.

Example:

"Customer was frozen to investigate fraud."

​
creation_time
string<date-time>
required

The date and time the note was created.

Example:

"2010-05-06T12:23:34.321Z"

​
id
string<uuid>
required

note ID

Example:

"7d943c51-e4ff-4e57-9558-08cab6b963c7"

​
last_updated_time
string<date-time>
required

The date and time the note was last updated.

Example:

"2010-05-06T12:23:34.321Z"

​
related_resource_id
string
required

The id of the resource that is associated with the note. This is typically a UUID. For TENANT it is a string tenant ID.

Example:

"7d943c51-e4ff-4e57-9558-08cab6b963c7"

​
related_resource_type
enum<string>
required

Type of the resource associated with the note.

Available options:
ACCOUNT,
APPLICATION,
BUSINESS,
CUSTOMER,
FILE,
SHADOW_TRANSACTION,
SNAPSHOT,
TENANT,
TRANSACTION,
USER
Example:

"CUSTOMER"

​
tenant
string
required

The id of the tenant containing the resource. This is relevant for Fintechs that have multiple workspaces.

Example:

"abcdef_ghijkl"

​
metadata
object

Optional field to store additional information about the resource. Intended to be used by the integrator to store non-sensitive data.

​
related_resource_field
string

🚧 Beta This is a Beta property. Feedback from the community is welcome. We may make breaking changes to this property. Path to the field in the related resource that the note pertains to. This uses a dot notation like the following: Examples:

  • a field in the resource: first_name
  • a sub-field: legal_address.city
  • nested arrays: application_details.sections[1].pages[2].items[0].answer
Example:

"/legal_address/city"

​
status
enum<string>

The state of the FEEDBACK, use this field to mark fields as RESOLVED or UNRESOLVED. This is required when creating a note with type FEEDBACK. Providing a status with note type NOTE will result in a Bad Request error.

Available options:
RESOLVED,
UNRESOLVED
Example:

"RESOLVED"

​
type
enum<string>
default:NOTE

The type of note.

Available options:
FEEDBACK,
NOTE
Example:

"NOTE"