Close API Documentation

This is the complete API documentation for connecting to the Close API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet Close: Manage leads, communicate across channels, automate follow-ups, and close deals. Keep reading to get started.

Quickstart

Before you run your first Close request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one Close connection — create or choose one in Connections. Note its connectionId.

Every Close action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/close/latest/actions/{actionSlug}

You need a MindCloud API Key and a Close connection. Then call an action such as Get Contact:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/close/latest/actions/get-contact" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Close account that should run the action. MindCloud stores and refreshes the Close credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

Close actions

All 41 published actions for this Close version. Each page documents the endpoint, arguments, and response controls.

• POSTCreate Contact
• POSTCreate Lead
• POSTCreate Opportunity
• POSTCreate Smart View
• POSTCreate Task
• DELETEDelete Contact
• DELETEDelete Lead
• DELETEDelete Opportunity
• DELETEDelete Smart View
• DELETEDelete Task
• GETGet Contact
• GETGet Current User
• GETGet Email Template
• GETGet Lead
• GETGet Opportunity
• GETGet Smart View
• GETGet SMS Template
• GETGet Task
• GETGet User
• GETGet Webhook
• GETList Activities
• GETList Contacts
• GETList Email Templates
• GETList Lead Statuses
• GETList Leads
• GETList Opportunities
• GETList Opportunity Statuses
• GETList Pipelines
• GETList Sequences
• GETList Smart Views
• GETList SMS Templates
• GETList Tasks
• GETList User Availabilities
• GETList Users
• GETList Webhooks
• POSTMerge Leads
• PUTUpdate Contact
• PUTUpdate Lead
• PUTUpdate Opportunity
• PUTUpdate Smart View
• PUTUpdate Task

Related apps

More Sales & CRM apps on the Universal API, behind the same REST shape. Or browse all apps.

HubSpotPipedriveGoogle TasksGoogle ContactsTodoistZoho CRMFollow Up BossDubsado