Close is a sales CRM built for high-velocity teams, combining pipeline management, built-in calling, email automation, SMS, and real-time reporting in a single platform. Designed for startups and small to mid-sized businesses, Close centralizes all sales communications and activity data so teams can manage leads, track opportunities, log calls and emails, and measure performance without switching between tools. Its REST API exposes the full breadth of Close data—leads, contacts, opportunities, activities, custom fields, and more—enabling seamless integration with data pipelines, BI tools, and external systems.
Power end-to-end data operations for your Close API with Nexla. Our bi-directional Close connector is purpose-built for Close, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Close or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Close workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Close supports two authentication methods for its API: API Key (HTTP Basic Auth) and OAuth 2.0. API keys are best suited for server-side integrations, internal tools, and scripts. OAuth 2.0 is recommended for user-facing integrations where individual users authorize access on behalf of their own Close accounts.
Enter a descriptive name for the key (for example, "Nexla Integration") and click Generate.
Copy the API key immediately after it is generated. For security reasons, the full key value will not be displayed again after you navigate away from this page.
Important
Store your API key securely. Anyone with access to this key can make API requests on behalf of your organization. If a key is compromised, delete it immediately from Settings > Developer > API Keys and generate a new one.
Set Up an OAuth 2.0 Application (OAuth 2.0 Method Only)
If you plan to authenticate using OAuth 2.0, you must first create an OAuth app in Close. OAuth 2.0 is recommended when your integration requires access on behalf of individual Close users.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Close credentials in Nexla support two authentication methods: API Key and OAuth 2.0 (3-Legged). Select the method that matches your integration requirements, and complete the corresponding fields.
Close Authentication Methods
API Key
OAuth 2.0 (3-Legged)
Authenticate using an API key generated from your Close organization settings. This method uses HTTP Basic Auth with the API key as the username and an empty password. API keys are per-organization and are best suited for server-side integrations, internal tools, and automated scripts.
Enter your Close API key in the **API Key** field. This key authenticates Nexla with the Close API on behalf of your organization and should be kept secure. API keys can be generated in **Settings > Developer > API Keys** within your Close account.
Authenticate using the OAuth 2.0 three-legged authorization flow, where a user grants Nexla permission to access their Close account. This method is recommended for user-facing integrations. You must first create an OAuth app in Close (Settings > Developer > OAuth Apps) to obtain a Client ID and Client Secret.
Enter the **Client ID** for your Close OAuth application in the **Client ID** field. This is the unique public identifier assigned to your OAuth app when it was created in **Settings > Developer > OAuth Apps**.
Enter the **Client Secret** for your Close OAuth application in the **Client Secret** field. This private key authenticates your application when requesting tokens and should be kept secure.
If your integration requires specific OAuth permission scopes, enter them as a space-separated list in the **Access Scope** field. Leave blank to request the default set of permissions for your application. For details about available scopes, refer to the [Close OAuth documentation](https://developer.close.com/topics/authentication-oauth2/).
Click the **Authorize** button to begin the OAuth authorization flow. You will be redirected to Close's authorization page, where you can grant Nexla access to your Close account. After authorization, you will be returned to Nexla and the credential will be configured with the resulting access token.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Close connector tile, then select the credential that will be used to connect to the Close instance, and click Next; or, create a new Close credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Close.com endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below; click on an endpoint to see more information about it and how to configure your data source for this endpoint.
Get Current User
This endpoint returns profile and permission information for the currently authenticated user. Use it to verify credential configuration or retrieve the user's organization membership details.
Response data is extracted from $ (root object) — the entire response is treated as a single record containing the authenticated user's details.
This endpoint is useful for confirming that your Close credential is correctly configured before building larger data flows.
List Leads
This endpoint returns a paginated list of all leads in the Close.com account. Leads represent companies or organizations and serve as the primary CRM object in Close. Use this endpoint to export lead records for analysis, syncing to a data warehouse, or downstream reporting.
Response data is extracted from $.data[*]. Each record is a lead object including associated contacts, custom fields, and status. Results are paginated; use _skip and _limit query parameters to page through results.
Use the date_updated__gte query parameter with a date/time macro to perform incremental loads — fetching only leads updated since the last ingestion run.
List Contacts
This endpoint returns a list of all contacts in the Close.com account. Contacts are individual people associated with leads. Use this endpoint to export contact records for CRM analysis, deduplication, or enrichment workflows.
Response data is extracted from $.data[*]. Each record contains contact name, email addresses, phone numbers, and the associated lead ID.
List Opportunities
This endpoint returns a list of all sales opportunities in the Close.com account. Use it to export pipeline data, track deal progression, or analyze win/loss rates.
Response data is extracted from $.data[*]. Each record includes opportunity value, status, close date, pipeline, and the associated lead ID.
Use date_updated__gte with a date/time macro for incremental opportunity ingestion.
List Events
This endpoint returns a chronological list of events in the Close.com account, representing all changes and interactions logged in the system. Use it for audit trails, activity feeds, or change-data-capture workflows.
Response data is extracted from $.data[*]. Each record contains event type, timestamp, object type, object ID, and the changed data.
List Email Activities
This endpoint returns a list of email activities recorded in Close.com, including both inbound and outbound emails associated with leads. Use it to analyze communication patterns, email volume, or response rates.
Response data is extracted from $.data[*]. Each record contains email subject, body, direction, timestamps, and the associated lead ID.
List Call Activities
This endpoint returns a list of call activities recorded in Close.com, including inbound and outbound calls with their duration, disposition, and recording details. Use it to track sales call volume, agent performance, or call outcomes.
Response data is extracted from $.data[*]. Each record includes call duration, direction, disposition, voicemail flag, recording URL, and the associated lead ID.
Call recordings are not included in the response body; the record contains a URL to retrieve the recording separately if needed.
List Note Activities
This endpoint returns a list of note activities in Close.com — free-text notes logged against leads by sales reps. Use it to extract CRM notes for NLP analysis, activity auditing, or data migration.
Response data is extracted from $.data[*]. Each record contains the note text, the user who created it, timestamps, and the associated lead ID.
List SMS Activities
This endpoint returns a list of SMS activities in Close.com, capturing text messages sent and received through the Close platform. Use it to analyze SMS engagement or log communication history.
Response data is extracted from $.data[*]. Each record contains the SMS text, direction, phone numbers, and the associated lead ID.
List Meeting Activities
This endpoint returns a list of meeting activities recorded in Close.com. Use it to track meeting cadence, follow up on scheduled interactions, or analyze engagement patterns across your sales team.
Response data is extracted from $.data[*]. Each record contains meeting title, date, attendees, and the associated lead ID.
List Email Thread Activities
This endpoint returns a list of email thread activities in Close.com, grouping related email messages into conversation threads. Use it to analyze email conversations at the thread level rather than individual message level.
Response data is extracted from $.data[*]. Each record represents an email thread and includes participant information and thread metadata.
List Created Activities
This endpoint returns a list of "created" activity records in Close.com, capturing the creation events for leads and other CRM objects. Use it to track when new leads were created and by whom.
Response data is extracted from $.data[*]. Each record includes the object type, creation timestamp, and the user responsible for creation.
List Lead Status Change Activities
This endpoint returns a list of activities recording status changes for leads in Close.com. Use it to track lead funnel progression, measure time in stage, or analyze conversion rates between lead statuses.
Response data is extracted from $.data[*]. Each record contains the old and new status, timestamp, and the user who made the change.
List Opportunity Status Change Activities
This endpoint returns a list of activities recording status changes for opportunities in Close.com. Use it to track deal progression through the pipeline and analyze stage-to-stage conversion rates.
Response data is extracted from $.data[*]. Each record contains the old and new opportunity status, timestamp, and the user who made the change.
List Task Completed Activities
This endpoint returns a list of activities recording completed tasks in Close.com. Use it to measure task completion rates, track follow-up discipline, or analyze rep productivity.
Response data is extracted from $.data[*]. Each record contains the task type, completion timestamp, and associated lead ID.
List Lead Tasks
This endpoint returns a list of tasks assigned to leads in Close.com. Use it to export open or completed tasks for follow-up tracking, rep workload analysis, or reporting dashboards.
Response data is extracted from $.data[*]. Each record includes task type, due date, assigned user, completion status, and associated lead ID.
List Incoming Email Tasks
This endpoint returns tasks created from incoming emails in Close.com — emails that require a follow-up action. Use it to track inbound email response queues or measure response time SLAs.
Response data is extracted from $.data[*]. Each record includes the triggering email reference, due date, and assigned user.
List Email Followup Tasks
This endpoint returns a list of email follow-up tasks in Close.com. Use it to identify pending outreach tasks or analyze follow-up cadence across your sales team.
This endpoint returns tasks created from missed calls in Close.com, representing callback reminders for unanswered inbound calls. Use it to track callback queues or measure missed-call follow-up rates.
Response data is extracted from $.data[*]. Each record includes the missed call timestamp, associated lead, and assigned user.
List Answered Detached Call Tasks
This endpoint returns tasks created from answered detached calls — calls that were answered but not yet associated with a lead. Use it to identify calls requiring lead assignment or follow-up.
This endpoint returns tasks created from voicemails in Close.com, representing callback reminders for inbound voicemails. Use it to track voicemail response queues.
This endpoint returns tasks associated with opportunities that are due in Close.com. Use it to surface time-sensitive deal tasks for prioritization or reporting.
Response data is extracted from $.data[*]. Each record includes the opportunity ID, due date, and assigned user.
List Incoming SMS Tasks
This endpoint returns tasks related to incoming SMS messages in Close.com, representing inbound text messages that require a reply or follow-up. Use it to track SMS response queues.
This endpoint returns the list of available statuses configured for leads in Close.com. Use it to retrieve status definitions for mapping or validation in downstream workflows.
Response data is extracted from $.data[*]. Each record contains the status ID, label, and type.
List Opportunity Statuses
This endpoint returns the list of available opportunity statuses configured in Close.com. Use it to retrieve status definitions for pipeline mapping or validation.
Response data is extracted from $.data[*]. Each record contains the status ID, label, and whether it represents a won/lost state.
List Pipelines
This endpoint returns a list of sales pipelines configured in the Close.com organization. Use it to retrieve pipeline definitions for reporting or to map opportunity statuses to their parent pipelines.
Response data is extracted from $.data[*]. Each record contains the pipeline ID, name, and associated opportunity statuses.
List Roles
This endpoint returns a list of user roles available in the Close.com organization. Use it to retrieve role definitions for access control mapping or user management workflows.
Response data is extracted from $.data[*]. Each record contains the role ID, name, and associated permissions.
List Smart Views
This endpoint returns a list of saved searches (Smart Views) in the Close.com account. Smart Views are pre-configured filter sets used to segment leads and contacts. Use this endpoint to inventory available views or integrate view-based segmentation into data pipelines.
Response data is extracted from $.data[*]. Each record contains the view name, query parameters, and creation metadata.
List Email Templates
This endpoint returns a list of email templates available in the Close.com account. Use it to export template definitions for documentation, replication, or content auditing.
Response data is extracted from $.data[*]. Each record contains the template name, subject, body, and sharing settings.
List Email Sequences
This endpoint returns a list of email sequences configured in the Close.com account. Use it to inventory automation sequences, audit step configurations, or track which sequences are active.
Response data is extracted from $.data[*]. Each record contains the sequence name, steps, sender settings, and active status.
List Custom Activities
This endpoint returns a list of custom activity types defined in the Close.com organization. Custom activities extend the built-in activity types with user-defined structures. Use it to retrieve custom activity type definitions for schema mapping or validation.
Response data is extracted from $.data[*]. Each record contains the custom activity type ID, name, and field schema.
List Lead Custom Fields
This endpoint returns a list of custom fields configured for leads in Close.com. Use it to retrieve field definitions for schema documentation, data mapping, or validation in downstream workflows.
Response data is extracted from $.data[*]. Each record contains the field name, type, and possible values.
List Contact Custom Fields
This endpoint returns a list of custom fields configured for contacts in Close.com. Use it to understand the contact data model or map custom fields to target schema in downstream systems.
This endpoint returns a list of custom fields configured for opportunities in Close.com. Use it to map opportunity data models to target schemas or validate field coverage in pipeline reporting.
This endpoint returns a list of custom fields configured for activities in Close.com. Use it to understand extended activity data structures when building activity-based reporting flows.
This endpoint returns a list of integration links configured for the Close.com organization — deep links that connect Close records to external systems. Use it to audit third-party integrations or export integration configuration.
This endpoint returns a list of email addresses and identities available for sending emails from Close.com. Use it to inventory sender identities for auditing or configuration management.
Response data is extracted from $.data[*]. Each record contains the sender email, name, and associated user.
Get Dialer
This endpoint returns the dialer configuration and settings for the Close.com organization, including power dialer status and settings. Use it to retrieve dialer configuration for auditing or change tracking.
Response data is extracted from $ (root object). The entire response is treated as a single dialer configuration record.
List Email Bulk Actions
This endpoint returns a list of email bulk actions that have been created or executed in Close.com. Use it to audit mass email campaigns or track the status of bulk email operations.
Response data is extracted from $.data[*]. Each record includes the action type, status, affected record count, and creation timestamp.
List Sequence Subscription Bulk Actions
This endpoint returns a list of bulk actions for sequence subscriptions in Close.com. Use it to audit bulk enrollment or unenrollment operations from email sequences.
This endpoint returns a list of bulk delete actions that have been executed in Close.com. Use it to audit mass deletion operations for compliance or change-management tracking.
This endpoint returns a list of bulk edit actions that have been executed in Close.com. Use it to track mass field update operations across leads or contacts for auditing or change-data-capture workflows.
This endpoint returns a list of Google accounts connected to Close.com for email and calendar integration. Use it to audit connected account configurations or verify integration status.
Response data is extracted from $.data[*]. Each record contains the Google email address and connection status.
List Custom Email Connected Accounts
This endpoint returns a list of custom (non-Google, non-Microsoft) email accounts connected to Close.com via IMAP/SMTP. Use it to audit custom email integration configurations.
This endpoint returns a list of Zoom accounts connected to Close.com for video meeting integration. Use it to audit Zoom integration configurations or verify connection status.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Close.com sources can also be manually configured to ingest data from any valid Close API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
The Close REST API base URL is https://api.close.com/api/v1. All endpoint URLs entered in Nexla should include this base URL followed by the specific resource path — common endpoints include leads (https://api.close.com/api/v1/lead/), contacts (https://api.close.com/api/v1/contact/), opportunities (https://api.close.com/api/v1/opportunity/), activities (https://api.close.com/api/v1/activity/), users (https://api.close.com/api/v1/user/), and pipelines (https://api.close.com/api/v1/pipeline/). The Close API enforces a default rate limit of 60 requests per minute per organization.
Most Close API list endpoints wrap records in a top-level data array alongside pagination metadata such as has_more and total_results. Enter $.data[*] in the Set Path to Data in Response field to extract individual records from this array. Combine date-filter query parameters such as date_updated__gte with Nexla date/time macros (for example, {now-1}) to perform incremental loads. The Close API's Authorization header is handled automatically by Nexla based on your credential configuration and does not need to be added as a request header. For a complete list of available endpoints, refer to the Close API Reference.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Close data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Close destination, and select the Send to Destination option from the menu. Select the Close connector from the list of available destination connectors, then select the credential that will be used to connect to the Close organization, and click Next; or, create a new Close credential for use in this flow.
Close destinations are manually configured to send data to any valid Close API endpoint. Select the API method — POST to create new records, PUT or PATCH to update existing records, or DELETE to remove them — and follow the instructions in Connect to Any API to configure the data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
The Close API accepts JSON for all write operations. The Close REST API base URL is https://api.close.com/api/v1 — for example, create leads with a POST to https://api.close.com/api/v1/lead/, or update or delete an existing record by appending its ID to the resource URL (for example, https://api.close.com/api/v1/lead/{'{lead_id}'}/). When sending contacts, opportunities, or activities, include the lead_id field in your Nexset data so that each record is linked to the correct lead. The Close API's Authorization and Content-Type headers are handled automatically by Nexla based on your credential and content format configuration. The Close API does not have a native bulk import endpoint for most resource types, so verify that the target endpoint supports batch payloads before enabling record batching; for high-volume sends, use Nexla's rate-limiting settings to stay within Close's default limit of 60 requests per minute per organization. For a complete list of required and optional fields for each resource type, refer to the Close API Reference.
Sending test data to write endpoints will create or modify actual records in your Close CRM account. Use a test lead or sandbox environment when possible to avoid unintended changes to production data.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to the configured Close endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Close until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
