Log Incoming Call

Endpoint

POST {{url}}/api/resource/Emotive Call Log

Example Request

{
  "type": "Incoming",
  "start_time": "2026-09-23 05:02:50",
  "end_time": "2026-09-23 05:02:50",
  "activity_code": "BCELL",
  "result_code": "BIPM",
  "reference_document_type": "Contact",
  "reference_document_name": "Austin A Billins-2025-01143",
  "from": "5676754323",
  "call_receiver": "[email protected]",
  "call_made_from_doctype": "LMS Lending Accounts",
  "call_made_from_document": "LA-015793",
  "note": "Incoming call",
  "status": "Completed",
  "is_manual": 1
}

Request Body

Send the call details as a JSON object with the fields at the top level (do not wrap them in doc).

Do not send to or caller. They are used only for outgoing calls.

Date and time format

start_time and end_time use the format YYYY-MM-DD HH:mm:ss in 24-hour time, in the site's time zone.

• Example: 2026-09-23 16:05:00 for 4:05 PM on 23 September 2026.
• Do not send T, Z or a time zone offset.
• end_time must not be earlier than start_time.

Call Reason and Call Outcome

The Call Reason is an Activity Code record. For an incoming call, only Activity Codes with Activity Type Call and Direction Inbound or Both are valid.

Each Call Reason has its own list of allowed Call Outcomes. Send a result_code from the list for the selected activity_code.

Call Reason and Call Outcome mapping for incoming calls

Send the code exactly as shown, including spaces, for example "result_code": "PROMISE TO PAY".

Call Reasons and Call Outcomes are configured per site, so the list can differ between environments. To get the current values, use Supporting APIs 1 and 2.

Selecting the contact (reference_document_name)

reference_document_name is the Contact ID of the person who called on the Lending Account: the Buyer, a Co Buyer or the Co Signer. For example, when logging a call with the Co Buyer, send the Co Buyer's Contact ID.

To find the Contact ID, call Supporting APIs 3 and look in the signers list. Each entry in data.signers has a party_role and a contact. Use the contact of the entry whose party_role matches the person who called:

Example from Lending Account LA-015793:

"signers": [
  {
    "party_role": "Buyer",
    "customer": "2025-01143",
    "contact": "Austin A Billins-2025-01143",
    "full_name": "Austin A Billins1 Sr.",
    "primary_phone": "5676754323",
    "primary_mobile_no": "5676754323"
  }
]

To log a call with this Buyer, send "reference_document_name": "Austin A Billins-2025-01143".

from is the phone number of the same signer. Use their primary_mobile_no or primary_phone from Supporting APIs 3.

Response

The response returns the created Emotive Call Log record wrapped inside a data object.

• name – Unique ID of the call log record
• owner, creation, modified, modified_by, docstatus, idx – System metadata
• type, start_time, end_time, activity_code, result_code, call_receiver, from, note, status, is_manual – Call details as sent in the request
• reference_document_type, reference_document_name – Contact who called
• call_made_from_doctype, call_made_from_document – Lending Account the call was logged against
• additional_context – Snapshot of the Lending Account's amounts due, days past due, next due and last paid at the time the call was logged
• is_ai_generated_summary – Whether the call summary was generated by AI (0 for manually logged calls)
• doctype – Always Emotive Call Log

Example Response

{
  "data": {
    "name": "f15qlj6sg2",
    "owner": "[email protected]",
    "creation": "2026-09-23 05:15:59.381969",
    "modified": "2026-09-23 05:15:59.381969",
    "modified_by": "[email protected]",
    "docstatus": 0,
    "idx": 0,
    "from": "5676754323",
    "status": "Completed",
    "start_time": "2026-09-23 05:02:50",
    "reference_document_type": "Contact",
    "reference_document_name": "Austin A Billins-2025-01143",
    "activity_code": "BCELL",
    "result_code": "BIPM",
    "is_manual": 1,
    "note": "Note from UI",
    "call_made_from_doctype": "LMS Lending Accounts",
    "call_made_from_document": "LA-015793",
    "to": "",
    "type": "Incoming",
    "call_receiver": "[email protected]",
    "caller": "",
    "end_time": "2026-09-23 05:02:50",
    "is_ai_generated_summary": 0,
    "additional_context": "Due with Fees: $ 0.00 · Due without Fees: $ 0.00 (0 payments due) · Days Past Due: 0 · Next Due: $ 1,000.00 (10-22-2026)\nLast Paid: N/A",
    "doctype": "Emotive Call Log"
  }
}

Status Codes

After the call is logged

• The call appears in the Lending Account's activity timeline.
• A snapshot of the account's balances at the time of the call is saved on the call log in additional_context.
• Because is_manual is 1, the Lending Account is marked as worked in the collection queue.
• The contact's last contacted date is updated on the Lending Account.

Supporting APIs

📘

Get valid values before logging a call

Use these APIs to get valid values for activity_code, result_code, reference_document_name and from before logging the call.

1. Get Call Reasons

Returns the Call Reasons that can be used for incoming calls.

GET {{url}}/api/resource/Activity Code?filters=[["activity_type","=","Call"],["direction","in",["Inbound","Both"]]]&fields=["code","description"]&limit_page_length=0

Use data[].code as activity_code.

2. Get Call Outcomes for a Call Reason

Returns the Call Outcomes allowed for the selected Call Reason.

GET {{url}}/api/resource/Activity Code/{activity_code}

Use data.result_codes[].code as result_code.

3. Get the contact from the Lending Account

Returns the Buyer, Co Buyers and Co Signer on the Lending Account, with each person's Contact ID and primary phone numbers.

GET {{url}}/api/resource/LMS Lending Accounts/{lending_account_id}

Use data.signers[].contact of the person who called as reference_document_name. See Selecting the contact.

Use data.signers[].primary_mobile_no or data.signers[].primary_phone of the same person as from.