---
title: "Add a call log"
method: POST
path: "/callLogs"
tags: ["CallLogs"]
---

# Add a call log

`POST /callLogs`

Adds a new call log.

## Request body

- object
  - `user_id` integer — The ID of the owner of the call log. Please note that a user without account settings access cannot create call logs for other users.
  - `activity_id` integer — If specified, this activity will be converted into a call log, with the information provided. When this field is used, you don't need to specify `deal_id`, `person_id` or `org_id`, as they will be ignored in favor of the values already available in the activity. The `activity_id` must refer to a `call` type activity.
  - `subject` string — The name of the activity this call is attached to
  - `duration` string — The duration of the call in seconds
  - `outcome` 'connected' | 'no_answer' | 'left_message' | 'left_voicemail' | 'wrong_number' | 'busy', required — Describes the outcome of the call
  - `from_phone_number` string — The number that made the call
  - `to_phone_number` string, required — The number called
  - `start_time` string, date-time, required — The date and time of the start of the call in UTC. Format: YYYY-MM-DD HH:MM:SS.
  - `end_time` string, date-time, required — The date and time of the end of the call in UTC. Format: YYYY-MM-DD HH:MM:SS.
  - `person_id` integer — The ID of the person this call is associated with
  - `org_id` integer — The ID of the organization this call is associated with
  - `deal_id` integer — The ID of the deal this call is associated with. A call log can be associated with either a deal or a lead, but not both at once.
  - `lead_id` string, uuid — The ID of the lead in the UUID format this call is associated with. A call log can be associated with either a deal or a lead, but not both at once.
  - `note` string — The note for the call log in HTML format

## Response `200`

The call log was successfully created.

- object
  - `success` boolean — If the response is successful or not
  - `data` object
    - `user_id` integer — The ID of the owner of the call log. Please note that a user without account settings access cannot create call logs for other users.
    - `activity_id` integer — If specified, this activity will be converted into a call log, with the information provided. When this field is used, you don't need to specify `deal_id`, `person_id` or `org_id`, as they will be ignored in favor of the values already available in the activity. The `activity_id` must refer to a `call` type activity.
    - `subject` string — The name of the activity this call is attached to
    - `duration` string — The duration of the call in seconds
    - `outcome` 'connected' | 'no_answer' | 'left_message' | 'left_voicemail' | 'wrong_number' | 'busy', required — Describes the outcome of the call
    - `from_phone_number` string — The number that made the call
    - `to_phone_number` string, required — The number called
    - `start_time` string, date-time, required — The date and time of the start of the call in UTC. Format: YYYY-MM-DD HH:MM:SS.
    - `end_time` string, date-time, required — The date and time of the end of the call in UTC. Format: YYYY-MM-DD HH:MM:SS.
    - `person_id` integer — The ID of the person this call is associated with
    - `org_id` integer — The ID of the organization this call is associated with
    - `deal_id` integer — The ID of the deal this call is associated with. A call log can be associated with either a deal or a lead, but not both at once.
    - `lead_id` string, uuid — The ID of the lead in the UUID format this call is associated with. A call log can be associated with either a deal or a lead, but not both at once.
    - `note` string — The note for the call log in HTML format
    - `id` string — The call log ID, generated when the call log was created
    - `has_recording` boolean — If the call log has an audio recording attached, the value should be true
    - `company_id` integer — The company ID of the owner of the call log

## Other responses

- `400` — The request contains wrong or incorrectly formatted arguments.
- `403` — You don't have permission to access the resource.
- `404` — A resource required to process the request was not found.
- `500` — There was an error processing the request.

---

[API](https://skmtc.net/pipedrive/apis/pipedrive-api-v1.md) · [All operations](https://skmtc.net/pipedrive/apis/pipedrive-api-v1/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pipedrive/pipedrive-api-v1/revisions/bf863a979545/schema)