Returns the notes associated with a lead. To use this API –
- Pass the “RelatedId” (Mandatory) in the JSON body. This is the “LeadId” or the “ProspectId” of the lead whose notes you wish to retrieve.
- Pass the “Id” (Optional) of a particular note you wish to retrieve in the JSON body. If you don’t pass this Id, all the lead’s notes will be retrieved.
Pass the “LeadId” or “ProspectId” of the lead here.
Pass the Id of a particular note here.
The results matching your criteria may be large. You can fetch the result in blocks of “PageSize” and make multiple calls to the API with increasing values of “PageIndex”. For example, you can specify “PageIndex”: 1, “PageSize”: 100 for the first call and specify “PageIndex”: 2, “PageSize”: 100 for the second call.
The column on which results will be sorted. For example, if you want results to be shown in descending order of lead creation date then use “CreatedOn” in “ColumnName” and choose “Direction” as “1”. Direction “1” implies descending order and “0” means ascending order.
The column on which results will be sorted. For example, if you want results to be shown based on creation date, pass “CreatedOn”.
Direction “1” means descending order and “0” means ascending order.
HTTP Response Codes
This is the status code for successful API call.
The API call was made with invalid access credentials. Check your AccessKey and SecretKey.
|400 Bad Request||
The message body on the request is not as per API specification. Make sure that content type is set to “application/json” and the JSON body has correct attribute names and structure.
|404 Not Found||
The API could not be found. Please check the API signature.
|429 Too Many Requests||
API calls exceeded the limit of 25 in 5 second(s)
|500 Internal Server Error||
The API called failed. There could be many reasons for it. Check the exception message to get more details.