Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Headers
An idempotency key is an arbitrary unique value generated by client to detect subsequent retries of the same request. It is recommended that a UUID or a similar random identifier be used as an idempotency key. A different key must be used for each request, unless it is a retry.
"7d943c51-e4ff-4e57-9558-08cab6b963c7"
Path Parameters
The unique identifier of a note
"64438afd-fa20-4010-a573-2bbdca77cdb6"
Query Parameters
Only return notes that have a related resource with the specified type.
ACCOUNT
, APPLICATION
, BUSINESS
, CUSTOMER
, FILE
, SHADOW_TRANSACTION
, SNAPSHOT
, TENANT
, TRANSACTION
, USER
"CUSTOMER"
Body
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.
RESOLVED
, UNRESOLVED
"RESOLVED"
Response
Updated Note representation.
The note's author.
"Jane Smith jane@example.com"
The note's text content.
"Customer was frozen to investigate fraud."
The date and time the note was created.
"2010-05-06T12:23:34.321Z"
note ID
"7d943c51-e4ff-4e57-9558-08cab6b963c7"
The date and time the note was last updated.
"2010-05-06T12:23:34.321Z"
The id of the resource that is associated with the note. This is typically a UUID. For TENANT it is a string tenant ID.
"7d943c51-e4ff-4e57-9558-08cab6b963c7"
Type of the resource associated with the note.
ACCOUNT
, APPLICATION
, BUSINESS
, CUSTOMER
, FILE
, SHADOW_TRANSACTION
, SNAPSHOT
, TENANT
, TRANSACTION
, USER
"CUSTOMER"
The id of the tenant containing the resource. This is relevant for Fintechs that have multiple workspaces.
"abcdef_ghijkl"
Optional field to store additional information about the resource. Intended to be used by the integrator to store non-sensitive data.
🚧 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
"/legal_address/city"
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.
RESOLVED
, UNRESOLVED
"RESOLVED"
The type of note.
FEEDBACK
, NOTE
"NOTE"