# Check NoteData by Source Check the NoteData by Source without pulling the full list. This reutrns a true/false on whether there are notes for the identified source. Endpoint: GET /note-data-check Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Query parameters: - `noteCategory` (string, required) Note_Category - `columnName1` (string, required) Column_Name1 - `keyValue1` (string, required) Key_Value1 - `columnName2` (string) Column_Name2 - `keyValue2` (string) Key_Value2 - `columnName3` (string) Column_Name3 - `keyValue3` (string) Key_Value3 - `columnName4` (string) Column_Name4 - `keyValue4` (string) Key_Value4 - `columnName5` (string) Column_Name5 - `keyValue5` (string) Key_Value5 ## Response 200 fields (text/plain): - `data` (boolean) - `error` (object) - `error.detail` (string,null) A human-readable explanation specific to this occurrence of the problem. - `error.instance` (string,null) A URI reference that identifies the specific occurrence of the problem.It may or may not yield further information if dereferenced. - `error.status` (integer) The HTTP status code([RFC7231], Section 6) generated by the origin server for this occurrence of the problem. - `error.title` (string,null) A short, human-readable summary of the problem type.It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization(e.g., using proactive content negotiation; see[RFC7231], Section 3.4). - `error.type` (string,null) A URI reference [RFC3986] that identifies the problem type. This specification encourages that, when dereferenced, it provide human-readable documentation for the problem type (e.g., using HTML [W3C.REC-html5-20141028]). When this member is not present, its value is assumed to be "about:blank". - `debug` (object) - `debug.activityID` (string, required) ## Response 401 fields