How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Close subpackage_leads API

The subpackage_leads API from Close — 3 operation(s) for subpackage_leads.

Close subpackage_leads API is one of 126 APIs that Close publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 3 paths, and defines 33 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.close.com/api/v1.

6 operations 3 paths 33 schemas 1 DELETE2 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.close.com/api/v1
Authentication
HTTP Basic, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Close subpackage_leads API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (ApiKeyAuth). It accepts HTTP bearer tokens (OAuth2).

  • ApiKeyAuth — Use your API key as the username and leave the password empty.

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

subpackage_leads 6
GET
/lead/
List Leads
list 4 params → 200400401404
POST
/lead/
Create a new lead
create 1 param body → 200400401404
POST
/lead/merge/
Merge two leads
merge 1 param body → 200400401404
GET
/lead/{id}/
Get a single Lead
get 3 params → 200400401404
PUT
/lead/{id}/
Update an existing lead
update 2 params body → 200400401404
DELETE
/lead/{id}/
Delete a lead
delete 2 params → 200400401404

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are Opportunity (39 properties), Lead (29 properties), Contact (19 properties), BasicSubscriptionInfoForContact (10 properties). Each schema is shown below with its type and property counts.

leads_list_Response_200
object
2 properties 2 required
StalledOpportunityActionTypeV1
string
BasicSubscriptionInfoForContact
object
10 properties 10 required
Opportunity
object
39 properties 19 required
OpportunityStatusType
string
Lead
object
29 properties 12 required
OpportunityFollowUpCallActionDetails
object
2 properties 2 required
CallStatus
string
Current status of the call.
CommentSummary
object
2 properties 2 required
StatusReason
string
Reason for each higher level status on a Workflow run.
WorkflowStatus
string
StalledOpportunityActionItems
object
2 properties 2 required
LeadAddress
object
8 properties 7 required
ContactRecentCall
object
5 properties 5 required
OpportunitySuggestedActionDetails
ActionItem
object
2 properties 2 required
StalledOpportunityActionTypeV2
string
ContactEmail
object
3 properties 3 required
OpportunityAdjustCloseDateActionDetails
object
1 property 1 required
OpportunityFollowUpEmailActionDetails
object
3 properties 3 required
RenderedIntegrationLink
object
2 properties 2 required
leads_delete_Response_200
object
Empty response body
ContactUrl
object
2 properties 2 required
ContactPhone
object
6 properties 2 required
WorkflowRunStatus
string
leads_merge_Response_200
object
Empty response body
Contact
object
19 properties 9 required
OpportunityValuePeriod
string
StalledOpportunityCommunicationIssue
string
OpportunityChangeStatusActionDetails
object
1 property 1 required
OpportunitySuggestedAction
object
3 properties 3 required
OpportunityFollowUpSMSActionDetails
object
2 properties 2 required
Attachment
object
5 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

close-subpackage-leads-api-openapi.yml Raw ↑

Other APIs Close publishes across the network.

Close subpackage_activities API
Close subpackage_activitiesCalls API
Close subpackage_activitiesCreations API
Close subpackage_activitiesCustomActivities API
Close subpackage_activitiesEmails API
Close subpackage_activitiesEmailThreads API
Close subpackage_activitiesFormSubmissions API
Close subpackage_activitiesLeadMerges API
Close subpackage_activitiesLeadStatusChanges API
Close subpackage_activitiesMeetings API
Close subpackage_activitiesNotes API
Close subpackage_activitiesOpportunityStatusChanges API
Where this information came from

This is an independent, third-party profile of Close subpackage_leads API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.