For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HomepageProduct HelpLog inTry for Free
Developers HomeAPI ReferenceMCP
Developers HomeAPI ReferenceMCP
  • Getting Started
    • Introduction
    • Authentication with API Keys
    • Authentication with OAuth
    • API Clients
    • Pagination
    • Specifying Fields
    • Filter Parameters
    • HTTP Response Codes
    • Rate Limits
    • Timezone Offsets
    • Rich Text Fields
    • Changelog
  • CRM Core
    • Leads
    • Contacts
    • Opportunities
    • Tasks
    • Files
    • Custom Objects
    • Comments
  • Activities
    • Activities
    • Notes
    • Calls
      • GETList or filter all Call activities
      • POSTLog an external Call activity
      • GETGet a single Call activity
      • PUTUpdate a Call activity
      • DELDelete a Call activity
    • Emails
    • Email Threads
    • WhatsApp Messages
    • Meetings
    • Custom Activities
    • Creations
    • Form Submissions
    • Lead Status Changes
    • Opportunity Status Changes
    • Lead Merges
    • Task Completions
  • Events & Webhooks
    • Webhooks
    • Events
  • Search & Reporting
    • Advanced Filtering
    • Smart Views
    • Reporting
  • Automation & Bulk Actions
    • Sequences (Workflows)
    • Bulk Actions
    • Exports
    • AI Field Enrichment
  • CRM Configuration
    • Custom Fields
    • Custom Activity Types
    • Custom Object Types
    • Pipelines
    • Opportunity Statuses
    • Lead Statuses
    • Integration Links
    • Forms
  • Communication Configuration
    • Email Templates
    • SMS Templates
    • Outcomes
    • Playbooks
    • Scheduling Links Guide
    • Scheduling Links
    • Connected Accounts
    • Send As
    • Unsubscribed Emails
    • Phone Numbers
    • Blocked Phone Numbers
    • Dialers
  • Users & Organizations
    • Users
    • Organizations
    • Memberships
    • Roles
    • Groups
Close

Product

OverviewCommunicationAutomationIntegrationsReportingSMSCallingSecurityForms

Pricing & Use Cases

PricingClose vs Other CRMsCustomer Stories

Resources

Sales BlogSales ResourcesSales GuidesWebinarsOn-Demand DemoSales Tools

Company

AboutCareersPartner with CloseBrand GuidelinesTermsPrivacyGDPRCCPA

Get Help

+1-833-GO-CLOSEHelp CenterDownload the Close AppProduct UpdatesSystem Status
LogoLogo
HomepageProduct HelpLog inTry for Free
On this page
  • Call transcripts
Activities

Calls

Call activities track inbound and outbound phone calls on a Lead.
|View as Markdown|Open in Claude|
Was this page helpful?
Edit this page
Previous

Delete a Note activity

Next

List or filter all Call activities

Built with

A Call is made:

  • via calling a lead directly or receiving an incoming call (regular call)
  • via the dialer using the power behavior (power dialer call)
  • via the dialer using the predictive behavior (predictive dialer call)

This is exposed in the call_method field with values regular, power, or predictive.

Every call also has a disposition. The values can be:

  • answered if the call was answered.
  • no-answer if the call was not answered.
  • vm-answer if a call was sent to voicemail, but the caller hung up without leaving a message (currently only applicable to incoming calls).
  • vm-left if a voicemail was left on an incoming call or dropped on an outgoing call.
  • busy if the call was not connected because the destination was busy.
  • blocked if Close did not allow the call to take place, e.g. due to the number being invalid.
  • error if an unexpected error occurred in Close or on our carrier’s side.
  • abandoned if the call was abandoned. This can only happen with the predictive dialer if no sales rep is available for a connected call.

Calls that connected may be assigned a custom user-defined outcome that will be present in the outcome_id field. See Outcomes to learn more.

The cost of the call is in US cents and is a decimal number.

About note_html and note parameters:

Call notes can be created/updated using either parameter, but setting one will overwrite the other. If both are in the same request, note_html takes precedence.

  • note_html is the preferred input. It supports rich-text content through a subset of HTML. Setting it will populate note with a plaintext representation, without guarantees about preserving formatting.
  • note is for plaintext only. Setting it will populate note_html by escaping HTML code and replacing newlines with <br /> tags.

Call transcripts

Call recording and voicemail transcripts can be accessed using this API but are not loaded by default. To load transcripts, use the _fields parameter. The available field names are recording_transcript and voicemail_transcript.

Example transcript in response:

1{
2 "recording_transcript": {
3 "utterances": [
4 {
5 "speaker_label": "John Lead",
6 "speaker_side": "contact",
7 "start": 0.1,
8 "end": 1.2,
9 "text": "Hey, what's up? How is it going?"
10 },
11 {
12 "speaker_label": "Jane User",
13 "speaker_side": "close-user",
14 "start": 1.3,
15 "end": 2.4,
16 "text": "Hey John, I'm doing great. How about you?"
17 }
18 ],
19 "summary_text": "Summary text",
20 "summary_html": "<p>Summary text</p>"
21 }
22}