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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Close

Close subpackage_schedulingLinks API

The subpackage_schedulingLinks API from Close — 8 operation(s) for subpackage_schedulinglinks.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 14 operations across 8 paths, and defines 11 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.

14 operations 8 paths 11 schemas 3 DELETE4 GET5 POST2 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_schedulingLinks 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 14

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

subpackage_schedulingLinks 14
GET
/scheduling_link/
List User Scheduling Links
list 1 param → 200400401404
POST
/scheduling_link/
Create a User Scheduling Link
create 1 param body → 201400401404
POST
/scheduling_link/integration/
Create or update a Scheduling Link via OAuth
create-integration 1 param body → 200400401404
DELETE
/scheduling_link/integration/{source_id}/
Delete a User Scheduling Link via OAuth integration
delete-integration 2 params → 204400401404
GET
/scheduling_link/{id}/
Fetch a User Scheduling Link
get 2 params → 200400401404
PUT
/scheduling_link/{id}/
Update a User Scheduling Link
update 2 params body → 200400401404
DELETE
/scheduling_link/{id}/
Delete a User Scheduling Link
delete 2 params → 204400401404
GET
/shared_scheduling_link/
List Shared Scheduling Links
list-shared 1 param → 200400401404
POST
/shared_scheduling_link/
Create a Shared Scheduling Link
create-shared 1 param body → 201400401404
GET
/shared_scheduling_link/{id}/
Fetch a Shared Scheduling Link
get-shared 2 params → 200400401404
PUT
/shared_scheduling_link/{id}/
Update a Shared Scheduling Link
update-shared 2 params body → 200400401404
DELETE
/shared_scheduling_link/{id}/
Delete a Shared Scheduling Link
delete-shared 2 params → 204400401404
POST
/shared_scheduling_link_association/
Map a Shared Scheduling Link
create-shared-association 1 param body → 201400401404
POST
/shared_scheduling_link_association/unmap/
Unmap a Shared Scheduling Link
delete-shared-association 1 param body → 200400401404

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

scheduling_links_deleteSharedAssociation_Response_200
object
Empty response body
scheduling_links_get_Response_200
object
Empty response body
scheduling_links_update_Response_200
object
Empty response body
scheduling_links_getShared_Response_200
object
Empty response body
scheduling_links_createSharedAssociation_Response_201
object
Empty response body
scheduling_links_createShared_Response_201
object
Empty response body
scheduling_links_create_Response_201
object
Empty response body
scheduling_links_listShared_Response_200
object
Empty response body
scheduling_links_list_Response_200
object
Empty response body
scheduling_links_updateShared_Response_200
object
Empty response body
scheduling_links_createIntegration_Response_200
object
Empty response body

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Close publishes across the network.

Close subpackage_activities API
AE Profile APIs.io
Close subpackage_activitiesCalls API
AE Profile APIs.io
Close subpackage_activitiesCreations API
AE Profile APIs.io
Close subpackage_activitiesCustomActivities API
AE Profile APIs.io
Close subpackage_activitiesEmails API
AE Profile APIs.io
Close subpackage_activitiesEmailThreads API
AE Profile APIs.io
Close subpackage_activitiesFormSubmissions API
AE Profile APIs.io
Close subpackage_activitiesLeadMerges API
AE Profile APIs.io
Close subpackage_activitiesLeadStatusChanges API
AE Profile APIs.io
Close subpackage_activitiesMeetings API
AE Profile APIs.io
Close subpackage_activitiesNotes API
AE Profile APIs.io
Close subpackage_activitiesOpportunityStatusChanges API
AE Profile APIs.io
#subpackage_schedulingLinks
← Back to C APIs
API Details
ID
close:close-subpackage-schedulinglinks-api
Base URL
https://api.close.com/api/v1
Docs
https://developer.close.com/api/resources/scheduling-links
Provider
Close
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=close-subpackage-schedulinglinks-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/close-subpackage-schedulinglinks-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Close subpackage_schedulingLinks 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.