Close (via Apideck)
Access Close through Apideck's CRM unified API — one of 21 CRM connectors that share the same method surface. Code you write here ports to Odoo, Salesforce, HubSpot and 17 other CRM connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant Close plumbing.
Quick facts
- Apideck serviceId:
close - Unified API: CRM
- Auth type: basic
- Gotchas: page
- Close docs: https://developer.close.com
- Homepage: https://close.com/
When to use this skill
Activate this skill when the user explicitly wants to work with Close — for example, "pull contacts in Close" or "sync leads in Close". This skill teaches the agent:
- Which Apideck unified API covers Close (CRM)
- The correct
serviceIdto pass on every call (close) - Close-specific auth and coverage caveats
For the full method surface (parameters, pagination, filtering), use your language SDK skill:
apideck-node,apideck-python,apideck-dotnet,apideck-java,apideck-go,apideck-php, orapideck-rest
For the raw OpenAPI spec:
Minimal example (TypeScript)
import { Apideck } from "@apideck/unify";
const apideck = new Apideck({
apiKey: process.env.APIDECK_API_KEY,
appId: process.env.APIDECK_APP_ID,
consumerId: "your-consumer-id",
});
// List contacts in Close
const { data } = await apideck.crm.contacts.list({
serviceId: "close",
});
Portable across 21 CRM connectors
The Apideck CRM unified API exposes the same methods for every connector in its catalog. Switching from Close to another CRM connector is a one-string change — no rewrite, no new SDK.
// Today — Close
await apideck.crm.contacts.list({ serviceId: "close" });
// Tomorrow — same code, different connector
await apideck.crm.contacts.list({ serviceId: "odoo" });
await apideck.crm.contacts.list({ serviceId: "salesforce" });
This is the compounding advantage of using Apideck over integrating Close directly: code against the unified CRM API once, gain access to every connector in it. New connectors Apideck adds become available to your app without code changes.
Authentication
- Type: Basic auth (username/password)
- Managed by: Apideck Vault — credentials are collected through the Vault modal and stored encrypted server-side.
- Note: basic auth connectors often require manual rotation by the end user. If auth fails persistently, prompt them to re-enter credentials in Vault.
See apideck-best-practices for Vault setup, connection lifecycle, and handling re-auth flows.
Verifying coverage
Not every CRM operation is supported by every connector. Always verify before assuming a method works:
curl 'https://unify.apideck.com/connector/connectors/close' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}"
See apideck-connector-coverage for patterns around UnsupportedOperationError and connector-specific fallbacks.
Escape hatch: Proxy API
When an endpoint isn't covered by the CRM unified API, use Apideck's Proxy to call Close directly — Apideck injects auth headers and handles token refresh. Set x-apideck-downstream-url to the target endpoint on Close's own API:
curl 'https://unify.apideck.com/proxy' \
-H "Authorization: Bearer ${APIDECK_API_KEY}" \
-H "x-apideck-app-id: ${APIDECK_APP_ID}" \
-H "x-apideck-consumer-id: ${CONSUMER_ID}" \
-H "x-apideck-service-id: close" \
-H "x-apideck-downstream-url: <target endpoint on Close>" \
-H "x-apideck-downstream-method: GET"
See Close's API docs for available endpoints.
Sibling connectors
Other CRM connectors that share this unified API surface (same method signatures, just change serviceId):
odoo (beta), salesforce, hubspot, pipedrive, zoho-crm, activecampaign, microsoft-dynamics, teamleader, and 12 more.
See also
- CRM OpenAPI spec · API Explorer
apideck-connector-coverage— programmatic coverage checksapideck-best-practices— architecture, Vault, pagination, error handlingapideck-node— TypeScript / Node SDK patterns- Close official docs