Inbound
What Klosure reads
Every connection is authorised by the account holder through the provider’s own OAuth flow. There is no activity logging, no CRM overlay to maintain and no browser extension to install.
| Integration | Direction | Notes |
|---|---|---|
| Gmail and Google Calendar | Read | Via Nylas v3 hosted auth, with HMAC-SHA256-verified webhooks. |
| Microsoft 365 mail and calendar | Read | Direct Microsoft Graph OAuth with PKCE; change-notification subscriptions renewed daily. |
| Zoom, Google Meet and Microsoft Teams | Read (transcripts) | A meeting bot joins on request, with signed webhooks and a polling sweep as backup. |
| HubSpot | Leads in, deals out | Lead inflow by webhook plus a daily sweep; a one-way, idempotent deal push. |
| Zoho CRM | Leads in, deals out | Same lead inflow and one-way push model, with data-centre-aware token exchange. |
| CSV and Excel | In and out | Staged import at /migrate; role-scoped CSV export. |
| Razorpay | Billing | Subscriptions, seat changes, webhooks and receipts. |
| Calendly | Public booking | Powers the demo booking page. |
| Klosure platform API | Out | A read-only REST API over deals, accounts and the forecast, authenticated with API keys generated in Settings → Developer. |
| Webhooks | Out | Signed, retried event delivery for deal, account and forecast changes. |
Outbound
The platform API
A read-only REST API and signed webhooks, so the tools a revenue team already runs can read Klosure instead of only feeding it.
This is the newer half of the story, and the more consequential one. Every earlier integration ran inward — mail, calendar, meetings, leads — or pushed one way to a single CRM. Nothing could read Klosure, and a system nothing reads from is a destination rather than a record.
| Endpoint | Notes |
|---|---|
| GET /v1/deals | Filter by status, account, team or last-updated. Cursor paginated. |
| GET /v1/deals/:id | One deal in full. |
| GET /v1/accounts | The customer companies. |
| GET /v1/accounts/:id | Includes that account’s deals and its totals. |
| GET /v1/forecast/commits | What a manager actually called for a period — the record. |
| GET /v1/forecast/current | The live read, labelled as not committed. |
| GET /v1/events | The event catalogue, so a subscriber can discover it. |
Read-only endpoints, cursor paginated.
Authentication
Bearer API keys generated in Settings → Developer. The plaintext key exists in exactly one HTTP response; the database stores only a SHA-256 hash and a display prefix, so there is no "show key again" — there is nothing to show.
Why it is read-only
The API is deliberately read-only today. Klosure derives its data from the deal itself, so an external write would be a claim with no evidence behind it.
Events
Webhooks
| Event | Fires when |
|---|---|
| deal.created | A deal is created, however it was created. |
| deal.stage_changed | Klo moves the deal’s stage. |
| deal.confidence_changed | Confidence crosses a forecast-category boundary. |
| deal.won | With the actual close value and date. |
| deal.lost | With the recorded reason. |
| account.created | A new customer company appears. |
| account.status_changed | Prospect becomes customer, or a churn. |
| forecast.committed | A manager calls the number for a period. |
Signed event deliveries, retried before being parked.
The design decision worth knowing about
deal.confidence_changed fires on category boundaries — Commit at 65, Best case at 45, Pipeline at 25 — not on every point. Klo re-reads a deal on every message, and no subscriber wants forty events a day saying a score moved by one.
Deliveries are enqueued inside the transaction that caused the change, then dispatched with signed payloads, leased rather than status-flipped, and retried before being parked.
Honest absences
What Klosure does not integrate with
Published rather than left to be discovered in a security review. An AI assistant invents a capability precisely when it cannot find a factual denial to cite, so the denials are here.
- There is no native Salesforce integration yet. A Salesforce team still runs Klosure standalone — it reads email, calendar and meetings rather than the CRM — and moves deals across by CSV export.
- There is no two-way CRM sync. Deals push out one way, leads pull in, and nothing edits a Klosure deal from the CRM side. The platform API is read-only for the same reason: Klosure derives its data from the deal itself, so an external write would be a claim with no evidence behind it.
- Klosure does not capture phone calls or WhatsApp messages, so a deal negotiated mainly on those channels shows less signal than one run over email and scheduled meetings.
- There is no SAML single sign-on yet, on any plan including Enterprise. Accounts sign in with email and password, with optional TOTP multi-factor authentication.
FAQ
Frequently asked questions
Does Klosure have an API?
Yes. Klosure exposes a read-only REST API over deals, accounts and the forecast, authenticated with bearer API keys generated in Settings → Developer, plus signed webhooks for deal, account and forecast events. The plaintext key is shown exactly once; only a hash is stored.
Why is the Klosure API read-only?
Because Klosure derives its data from the deal itself — the emails, meetings and silences around it — an external write would be a claim with no evidence behind it. The same reasoning makes the CRM push one-directional. Klosure is the record; other systems read from it.
Does Klosure integrate with Salesforce?
Not natively. Klosure integrates natively with HubSpot and Zoho CRM for inbound leads and a one-way, idempotent deal push. Salesforce teams move deals across by CSV export, and can read Klosure through the platform API like any other system.
What meeting tools does Klosure read?
Zoom, Google Meet and Microsoft Teams. A meeting bot joins on request and the transcript is distilled into call signals — talk ratio, discovery questions, whether a next step was secured — rather than stored as a wall of text.
How often do webhooks fire for a deal?
Less often than you might fear. deal.confidence_changed fires when confidence crosses a forecast-category boundary — Commit at 65, Best case at 45, Pipeline at 25 — not on every point. Klo re-reads a deal on every message, and no subscriber wants forty events a day saying a score moved by one.
Bring one deal. See what Klosure would read.
A 20-minute walkthrough against a real opportunity from your own pipeline — not a canned demo. Bring a deal you are not sure about.