Close.com
SaaS API (REST)
Managed auth, retries, and throttling
Export coverage
Know exactly what Vern pulls before you migrate.
Objects Vern extracts
Vern extracts the full set of queryable Close.com objects (45 total), including: Activity Custom Fields, Answered Detached Call Tasks, Call Activities, Contact Custom Fields, Contacts, Created Activities, Custom Activities, Custom Email Connected Accounts, Delete Bulk Actions, Dialer, Edit Bulk Actions, Email Activities, Email Bulk Actions, Email Followup Tasks, Email Sequences, Email Templates, Email Thread Activities, Events, Google Connected Accounts, Incoming Email Tasks, Incoming Sms Tasks, Integration Links, Lead Custom Fields, Lead Status Change Activities, Lead Statuses, Lead Tasks, Leads, Meeting Activities, Missed Call Tasks, Note Activities, Opportunities, Opportunity Custom Fields, Opportunity Due Tasks, Opportunity Status Change Activities, Opportunity Statuses, Pipelines, Roles, Send As, Sequence Subscription Bulk Actions, Smart Views, Sms Activities, Task Completed Activities, Users, Voicemail Tasks, and Zoom Connected Accounts. 21 of these support incremental change tracking, so syncs pull only what changed.
Output schema
Normalized JSON per object with referential keys preserved, so the relationships between your user's records survive the import. Timestamps are returned in ISO 8601. Delivered as JSON or CSV, or loaded straight into your own application database or pushed to your API — whatever your product expects.
Where it can land
Your own application database (Postgres, MySQL), a direct push to your API or webhook, or JSON/CSV files, plus another crm system (AgileCRM, Apptivo, Capsule CRM) when a user is switching tools.
Source details
Built for the source type shown above, with extractor content refreshed from the collection record.
Managed by Vern
The details you normally have to build yourself.
Authentication
API key / access token. Your user pastes their Close.com API key once when they sign up; Vern stores it encrypted and attaches it to every request, handling header signing and retries so you never touch the raw credential. See Close.com's authentication guide.
Pagination
Vern detects and handles Close.com's paging model (cursor, page-number, or offset) internally and returns one consistent, de-duplicated result set — so you import a user's complete data without ever managing page tokens.
Rate limits and gotchas
Close.com enforces its own API rate limits (see Close.com's rate-limit docs). Vern queues and throttles requests internally so importing a new user's data never trips a 429 — even on a large account.
API-key sources rarely surface their true rate ceilings until you hit a 429 mid-import, and many silently cap page size. Vern throttles to stay under the limit and normalizes paging so a partial pull never lands a user in your product with missing data.
API quickstart
A cleaner way to extract without rebuilding source-specific plumbing.
View docs
Common questions
Can I keep a user's Close.com data in sync after the first import? Yes — 21 Close.com objects support incremental change tracking, so after the first full import Vern pulls only what changed on re-run.
Can I move a user from Close.com to AgileCRM? Yes — Vern normalizes the Close.com data model into typed tables that map cleanly onto AgileCRM and into your own product.
What does it cost to read the Close.com API? Close.com's own API access follows Close.com's pricing/plan; Vern is billed separately per import. Check Close.com's developer docs for their current limits.
