API Changelog

Opportunities now support a note_html field for rich text notes, alongside the existing plaintext note field.

When you create or update an opportunity:

• Providing note_html makes it the source of truth. The plaintext note is automatically derived from it, overriding any note sent in the same request.
• On update, sending note_html: null clears both note_html and note.
• When you send only note and the opportunity already has a note_html, the rich text version is re-derived from the new note.

We have added the Forms API.

You can now list the forms your team has built in Close and inspect their field definitions, including field types and select-field choices.

We have added a new Playbooks API for managing playbooks — reusable templates that standardize how your team conducts calls and meetings.

We have added a new Blocked Phone Numbers API, which lets you manage a list of phone numbers that should be blocked from calling or messaging within your organization.

We now publish an OpenAPI spec for the Close API at: https://api.close.com/api/openapi.json

This spec is currently considered experimental and does not yet contain 100% coverage of request/response schemas. If you have any feedback or use cases you’d like to share, please let us know by emailing support@close.com.

The applies_to field on the Outcome API is now deprecated on write operations (create and update). In a future update, the field will be ignored on create and update requests and will instead be derived from the type field:

• When type is custom, applies_to will always be ["calls", "meetings"].
• When type is vm-dropped, applies_to will be ["calls"].

We have added support for Form Submissions as a new activity type. Form Submissions are created by the system whenever someone fills out a Close Form.

We also introduced new events activity.form_submission.created, activity.form_submission.updated, and activity.form_submission.deleted, which you can subscribe to using webhooks.

We fixed a bug in the Email API that previously allowed creating emails without a sender in cases where a sender is required.

The sender field is required for emails with status inbox, scheduled, outbox, or error. It may be omitted in the following cases:

• For draft, since the sender can be specified later before sending.
• For sent, where it defaults to the email address of the user associated with the email or the owner of the API key.

You can now set a Note’s title field when creating or updating a Note via the Note API.

We have also added the title and pinned_at fields to responses in the Note API.

We have added the transcripts field to responses in the Meeting API.

We have introduced the Outcome API which allows you to organize & manage outcomes, i.e. standardized results that can be applied to activities such as calls and meetings.

Outcomes can help sales teams track and categorize the results of their interactions with prospects and customers.

We have introduced the Field Enrichment API that uses AI to intelligently populate fields on leads and contacts.

We have added support for WhatsApp Messages as a new activity type. This allows integration partners to sync WhatsApp messages into Close, enabling viewing of ongoing WhatsApp conversations within the CRM.

Important: WhatsApp messages can only be synced into Close for viewing and tracking purposes. Close does not send WhatsApp messages directly - actual sending must be done through WhatsApp apps or other third-party WhatsApp platforms.

We have added the ability to create a contact without specifying an existing lead_id. Doing so will create a new lead, named after the contact, and associate the new contact with this new lead.

We have also added the ability to create an opportunity without specifying an existing lead_id. Doing so will create a new lead with no name (it will appear in the Close UI as “Untitled”), and associate the new opportunity with this new lead.

We have updated the Webhook Subscription PUT endpoint to accept additional parameters. You can now update existing subscriptions with a new url, a new list of events to subscribe to, and a verify_ssl parameter to control if SSL is verified at the destination URL.

The boolean record_calls field on the Membership API has been deprecated in favor of auto_record_calls, an enum field with the initial value of 'unset' for a new membership, and which can be updated to 'enabled' or 'disabled' to control whether calls are automatically recorded or not.

We have updated the Export API with a new date_format parameter to control the format of date objects in CSV exports.

Custom Object Types can now be archived, by providing is_archived: true flag during an update operation.

Custom Objects are no longer in beta, meaning they are available to everyone on the corresponding billing plan.

We have added the ability to delete Lead and Opportunity Status Change activities.

Deleting a status change does not change the status of the Lead or Opportunity. It only removes the status change event from the Lead’s activity feed. It should only be used if the status change is irrelevant (such as records for a change that has been reverted), and having it in the activity feed is causing integration problems with another system.