API Changelog: Release Notes
Sign-up question in the account export (November 2026)
Section titled “Sign-up question in the account export (November 2026)”- The sign-up form now asks, optionally, how you heard about Klozeo.
GET /account/exportaddssignup_heard_from: the account owner’s answer, ornullwhen there is none. Existing fields are unchanged. → Export your account
Time zones in Settings (November 2026)
Section titled “Time zones in Settings (November 2026)”- The workspace owner and admins, an admin without lead access included, can change the workspace’s time zone in Settings, under Workspace time zone.
this_monthfollows the new zone from the next call; alerts follow it from their next check, within 15 minutes. No API route or assistant tool changes the zone. - Each person can also set their own time zone in Settings, under Your time zone. It sets the times shown in the dashboard and in e-mails about their own account; it changes no workspace calculation.
Time zone in stats and alert settings (November 2026)
Section titled “Time zone in stats and alert settings (November 2026)”GET /statsandGETandPUT /api-keys/{id}/alertnow returntime_zone, the workspace’s time zone as an IANA name such asEurope/Paris: the zonethis_monthandactive_daysare counted in. It is read-only. The account export includes it too. → LeadStats
Monthly lead count in the workspace’s time zone (November 2026)
Section titled “Monthly lead count in the workspace’s time zone (November 2026)”this_monthinGET /statsnow counts the leads created since 00:00 on the 1st of the month in the workspace’s time zone, instead of in UTC. The assistant toolget_statsreturns the same count. → LeadStats- Existing workspaces start on Europe/Paris. In that zone, the month starts at 23:00 UTC in winter or 22:00 UTC in summer, on the last day of the previous month. New workspaces use their creator’s stored time zone, or Europe/Paris if none is stored.
- Lead-flow alerts: active days and the paused clock now follow the workspace’s time zone instead of Paris time. Their timing stays the same for workspaces on Europe/Paris. → How it works
Lock policy in the SDKs (November 2026)
Section titled “Lock policy in the SDKs (November 2026)”- The TypeScript and Python SDKs (0.4.0) read and replace the workspace lock policy:
client.lockPolicy.get()andclient.lockPolicy.replace({ fields, attributes })in TypeScript,client.get_lock_policy()andclient.replace_lock_policy(fields, attributes)in Python. A replace sends the whole policy, both lists, and needs an API key with thefullscope. When the policy cannot be saved right now, the SDKs retry, then raise aKlozeoErrorwith the codesave_temporarily_unavailable; nothing is saved. → Lock policy - New types
LockPolicyandLockPolicyEntry(name, andeffectiveAtin TypeScript,effective_atin Python), andAccountExportfor the account export document, withlock_policyandstatusesoptional. The account export still returns raw bytes, aBlobin TypeScript. → TypeScript, Python
Lock custom attributes in the SDKs (November 2026)
Section titled “Lock custom attributes in the SDKs (November 2026)”- The TypeScript and Python SDKs (0.3.0) lock and unlock a lead’s custom attribute:
client.leads.lockAttribute(id, attrId)andclient.leads.unlockAttribute(id, attrId)in TypeScript,client.lock_attribute(lead_id, attr_id)andclient.unlock_attribute(lead_id, attr_id)in Python. Both return the attribute and need an API key with thefullscope. → Lock Attribute - Attributes read from the API carry
locked,trueon a locked attribute. It is read-only.AttributeChange.reasonnow names its values:locked,type_mismatchandambiguous_name. A merge that sends a locked attribute lists it asignoredwith the reasonlocked. → TypeScript, Python
Lock custom attributes from the MCP server (November 2026)
Section titled “Lock custom attributes from the MCP server (November 2026)”- The classic MCP endpoint (
https://mcp.klozeo.com/mcp) addscreate_lead_attribute_lockanddelete_lead_attribute_lock(38 tools). They take thelead_idand theattr_idfromget_leadorlist_attributes, return the attribute, and need an API key with thefullscope.get_leadandlist_attributesshow"locked": trueon each locked attribute. The Claude and ChatGPT connectors do not get these tools. → MCP tools
Workspace lock policy (November 2026)
Section titled “Workspace lock policy (November 2026)”- Owners and admins can list fields and custom attributes to freeze after their first value. On leads created afterwards, the first non-empty value is locked automatically, from any channel. An explicit
PUT /leads/{id}can still change it, and a lock removed on a lead is not set again. Existing leads are never locked by the policy. → Lock policy
Lock custom attributes (November 2026)
Section titled “Lock custom attributes (November 2026)”- Lock a lead’s custom attribute with
POST /leads/{id}/attributes/{attr_id}/lock(unlock withDELETE). Duplicate merges, imports, inbound sources and company enrichment then never write it, and the merge response lists it inattribute_changesasignoredwith the reasonlocked. An explicitPUT /leads/{id}/attributes/{attr_id}still changes it, and it stays locked. → Lock Attribute - When a person changes an existing attribute’s value or type in the dashboard, Klozeo now locks that attribute, as it already does for fields. Writes from an API key, an assistant connection, an inbound source or an import never lock an attribute. → Attribute locks
- A locked attribute carries
"locked": trueinGET /leads/{id},GET /leads/{id}/attributes,POST /leads/{id}/attributesand JSON exports. The dashboard does not show attribute locks. Locking or unlocking fires no webhook.
Dashboard corrections are kept (November 2026)
Section titled “Dashboard corrections are kept (November 2026)”- When a person edits a lead in the dashboard, Klozeo now locks the fields that changed. The next merge, import or company enrichment no longer overwrites the correction, and the merge response lists the field in
skipped_locked_fields. Writes from an API key, an assistant connection, an inbound source or an import never lock a field. An explicitPUT /leads/{id}can still change a locked field, and a lock can be removed by anyone who can set one. → Field locks
Creation dates in lead.created webhooks (November 2026)
Section titled “Creation dates in lead.created webhooks (November 2026)”- Webhooks:
lead.creatednow carries the lead’screated_at,updated_atandlast_interaction_at, in Unix seconds, aslead.updateddoes. Nothing else in the payload changes. → Payload format
Alerts when leads stop arriving (November 2026)
Section titled “Alerts when leads stop arriving (November 2026)”- Set an alert on an API key: a maximum gap without new leads, from 1 to 720 hours, the days it applies to (Paris time), and a snooze of up to 7 days. Once a key has 14 days of leads and 8 sessions, Klozeo suggests a gap and never applies it for you. →
GETandPUT /api-keys/{id}/alert GET /api-keys/healthshows each key’s state (ok,silent,snoozed,no_lead_received,unmonitored,disabled) and its last lead received;GET /api-keys/incidentslists silences of the last 13 months.- New webhook events
source.silentandsource.recovered, sent only to webhooks that name them, never through"*". → Lead-flow alert events - For now the alerts are webhook events only, ready for Slack, n8n or Make; alert emails come in a later release. → Get alerted when leads stop arriving
Test a connection with any API key (November 2026)
Section titled “Test a connection with any API key (November 2026)”- New endpoint
GET /me: it returns the calling API key (id,name,scope,expires_at) and its account (id,name,plan). Every key scope can call it, including write-only keys. → Test a connection
Invalid emails no longer merge or block leads (November 2026)
Section titled “Invalid emails no longer merge or block leads (November 2026)”- Every lead write stores the email without surrounding spaces and in lowercase, including
PUT /leads/{id}andPUT /leads/batch.Jean Dupont <[email protected]>is stored as[email protected]. - An invalid email, such as
n/aor[email protected]; [email protected], no longer merges unrelated leads and never fails the request: the lead is written without it, and an update keeps the stored email. → Valid emails - New response field
warnings, for example[{ "field": "email", "code": "invalid_email" }], onPOST /leads, each item ofPOST /leads/batch,PUT /leads/{id},PUT /leads/batchand the assistantsave_leadsreceipt. It names the field and the reason, never the value, and is absent when there is nothing to report. - Webhooks: in
lead.created,emailis the stored address, ornullwhen the email sent was invalid.
Dashboard search now filters your leads (November 2026)
Section titled “Dashboard search now filters your leads (November 2026)”- Search by lead name also filters the status counts and exports.
One editable Free workspace per owner (November 2026)
Section titled “One editable Free workspace per owner (November 2026)”- If you own two or more Free workspaces, only one stays editable: your first workspace if it is on Free, otherwise the oldest. The others become read-only for every member. Nothing is deleted. Changes to leads, scoring rules and the status list are refused, including with API keys, with
403and the codeworkspace_read_onlyunless an earlier scope or access check returns its own error. Reading, export, members, API keys, webhooks and assistant connections keep working. Subscribing a read-only workspace to Pro or Scale restores editing in it. → When a Free workspace becomes read-only - The trial reminder email says so when it applies.
Lead history and safe retries in the SDKs (November 2026)
Section titled “Lead history and safe retries in the SDKs (November 2026)”- The TypeScript and Python SDKs (0.2.0) read a lead’s history:
client.leads.listChanges(id)in TypeScript,client.list_changes(lead_id)in Python. Each entry has its action, date, the member or API key that acted,beforeandafter,reason,assigneeandchannel.limit(1 to 100, default 50) andactions(for example["created", "merged"]) narrow the list. → List Lead Changes - Lead create, batch create and note create take an
Idempotency-Key:{ idempotencyKey }in TypeScript (leads.create,leads.batchCreate,notes.create),idempotency_key=in Python (create,batch_create,create_note). The SDKs never pick a key for you. Their automatic retries send the same key again. The new errors arrive asKlozeoErrorwith the codeidempotency_key_reused,idempotency_key_in_progressorNOTE_ALREADY_DELETED. → Retries and idempotency
Status counts follow your filters (November 2026)
Section titled “Status counts follow your filters (November 2026)”GET /statusesaccepts thefilterparameters ofGET /leads. Its counts then cover only the leads that list returns, andunlistednames only the values those leads hold. Withoutfilter, the response is unchanged. → Statuses API- In the dashboard, Group by status shows, for each status, the number of leads that match your filters, not the workspace total.
Retry creates safely with Idempotency-Key (November 2026)
Section titled “Retry creates safely with Idempotency-Key (November 2026)”POST /leads,POST /leads/batchandPOST /leads/{id}/notesaccept an optionalIdempotency-Keyheader. Send the same lead request with the same key again and you get the first response, with the headerIdempotent-Replayed: true, and nothing is written twice. On a note, a replay returns the note as it is now. Klozeo keeps a key for 30 days. A key does not change matching: a new request still creates or merges as before. → Retries and idempotency- New errors:
400 invalid_idempotency_key,409 idempotency_key_reused,409 idempotency_key_in_progressand, on notes,410 note_already_deleted.
Lead access for admins, given by the owner (November 2026)
Section titled “Lead access for admins, given by the owner (November 2026)”- An admin sees no leads until the workspace owner gives lead access for 24 hours, 7 days or with no limit, from the Team page. The owner can end it at any time. An admin without access can request it. → Lead access
- API keys and webhooks keep working, including the ones an admin created.
- A dashboard or assistant request from an admin without lead access returns
403with the codelead_access_required. API keys never get it.
History of deleted leads is erased after 30 days (November 2026)
Section titled “History of deleted leads is erased after 30 days (November 2026)”- The history of a deleted lead is kept for 30 days. A daily job then erases
before,after(including note text) andassignee, so the values are gone within 31 days of the deletion. Each entry keeps its action, date, the member or API key that acted,channelandreason, and gainschanged_fields, the names of the fields that changed. → List Lead Changes - The history of a lead that is not deleted is not erased. → Audit trail
See all your workspaces on one page (November 2026)
Section titled “See all your workspaces on one page (November 2026)”- A new page, Your workspaces, lists every workspace you belong to, in any role. Open it with All workspaces in the workspace selector, shown when you belong to two or more. Each row shows your role, the plan, with its end date when it has one, the number of leads, the last change in the lead history (automatic score updates excluded) and the webhook deliveries that failed in the last 7 days. Only an owner, or an admin on Pro or Scale, sees the failure count. The page does not change billing: that stays with each workspace’s owner. → Choose a workspace
Note authors and a history tab in the dashboard (November 2026)
Section titled “Note authors and a history tab in the dashboard (November 2026)”- Each note in the dashboard now shows who wrote it and when, or the API key it was written with. Every member of the workspace sees it. Some older notes, and notes whose author deleted their account, show no byline, only their date. → Note authors and the history tab
- A lead has a new history tab with its 50 most recent changes, each with its date and who made it. Automatic score updates are not listed; the API lists them.
GET /leads/{id}/changesaddschannelto the entries a create or a duplicate merge recorded: how the lead arrived (api,api_batch,mcp_classic,dashboard,importorsave_leads). Klozeo sets it from your credential and the route. Older entries have none. → List Lead Changes
Assignee and note authors in the SDKs and the classic MCP endpoint (November 2026)
Section titled “Assignee and note authors in the SDKs and the classic MCP endpoint (November 2026)”- On the classic MCP endpoint (
https://mcp.klozeo.com/mcp),create_lead,update_lead,batch_create_leadsandbatch_update_leadsdeclareassignee. The Claude and ChatGPT connectors are unchanged. → MCP tools - The TypeScript and Python SDKs add
assigneeto leads and to create, update and batch inputs,authorandapiKeyId(api_key_idin Python) to notes, and anassignee()filter withme(). In Python,UpdateLeadInput(assignee=None)unassigns the lead.
Assign leads in the dashboard (November 2026)
Section titled “Assign leads in the dashboard (November 2026)”- The owner, admins and editors can now assign a lead to the owner or to any active member from the dashboard. The leads list has an Assignee column, the scope All leads, My leads or Unassigned, and an Assignee filter that accepts me. A lead has an Assigned to picker, and Assign on a selection assigns many leads to one person. Members who cannot write leads see the assignee but cannot change it. The leads of a removed member stay assigned and show Former member. The dashboard does not unassign in bulk. → Assign leads
Your own lead statuses (November 2026)
Section titled “Your own lead statuses (November 2026)”- Each workspace now has its own list of lead statuses, in order, each with a value, a label and a color. The five statuses you know are the defaults. The owner and admins edit the list in Dashboard → Settings → Statuses (on Free, the owner). Renaming a status changes its label only: exports and webhooks carry the value, so your scenarios keep working. Deleting a status leaves leads unchanged, flagged “Not in the list”. The leads table can group leads by status. → Lead statuses
GET /statusesreturns the list with lead counts and the values leads hold outside it.PUT /statusesreplaces the list.GET /leadsandGET /leads/exportacceptsort_by=status, in list order. → Statuses API- On the Claude connector (
https://mcp.klozeo.com/v1/mcp) and the classic endpoint (https://mcp.klozeo.com/mcp), a new read tool,list_statuses, returns the list, andupdate_leadtakes any status up to 50 characters instead of the five defaults only. The ChatGPT connector is unchanged. - The TypeScript SDK adds
client.statuses.list()andclient.statuses.replace(), and the Python SDK addslist_statuses()andreplace_statuses(). Both acceptstatusas a sort field.
Filter and export leads by assignee (November 2026)
Section titled “Filter and export leads by assignee (November 2026)”GET /leadsandGET /leads/exportaccept anassigneefilter:eq,neqorinwith an email orme, oris_emptyandis_not_empty.meis you; with an API key, it is the workspace owner.neqalso returns unassigned leads. CSV and XLSX exports gain anassigneecolumn afternotes, so everyattr:column moves one position to the right. Read attribute columns by their header. → Filter operators
Members see each other’s emails (November 2026)
Section titled “Members see each other’s emails (November 2026)”- Everyone in a workspace, in any role and on any plan, now sees the email of the owner and of every active member: in the dashboard wherever it names a person, and, as a lead’s assignee or a note’s author, in the API, the MCP server and exports. In the dashboard, a removed member appears as a former member. Their email stays in the API, the MCP server and exports on the leads assigned to them, on the notes they wrote and on the assigned entries of the history until their account is deleted. Other members do not see pending invitations. No account outside the workspace sees these emails. → Team access
Who wrote each note (November 2026)
Section titled “Who wrote each note (November 2026)”- Notes add
authorandapi_key_id, wherever the API returns a note:GET /leads/{id}/notes, note create and update responses, and leads exported as JSON.authoris the email of the member who wrote the note, or the workspace owner’s email for a note written with an API key; it is null once that person’s account has been deleted, and for some notes written before November 2026.api_key_idis the API key the note was written with. Editing a note changes neither. Webhook payloads and lead history never includeauthor. → Notes
Assign a lead to a member (November 2026)
Section titled “Assign a lead to a member (November 2026)”- A lead has an
assignee: the email of the workspace owner or of an active member, ornull. Set it onPOST /leads,PUT /leads/{id}andPOST /leads/batch, or for many leads at once withPUT /leads/batch.nullor""removes it. Any other email returns400with the codeassignee_not_member. A merge, in a single call or a batch, never changes the assignee of the existing lead. Each change adds anassignedorunassignedentry to the lead’s history. Webhooks do not carry the assignee. → Create Lead
See and cut what reaches a workspace (November 2026)
Section titled “See and cut what reaches a workspace (November 2026)”- Dashboard → Team has a new card, Access to this workspace, for the owner on any plan, and for admins when the workspace is on a paid plan. It lists the workspace’s API keys, webhooks and assistant connections with who set up each one, and revokes a key, deletes a webhook or removes the workspace from a connection in one click. After a transfer, it is where the new owner reviews what the previous owner left in place. → Hand a workspace to your client
The dashboard names the key behind a change (November 2026)
Section titled “The dashboard names the key behind a change (November 2026)”- In a lead’s Do not contact panel, a change made with an API key now reads “via the key “Make prod”” instead of naming the account owner. Every member of the workspace sees the key’s name; a revoked key keeps its name, marked “(revoked)”. API-key changes recorded before
api_key_idwas introduced still show the recorded actor instead of a key. → Audit trail
Delete a workspace (November 2026)
Section titled “Delete a workspace (November 2026)”- The owner of a workspace can now delete it from Dashboard → Settings → Delete workspace, by typing its name. The deletion removes the workspace’s leads, notes, attributes and history, scoring rules, API keys, webhooks, members and invitations. Assistants lose the workspace and keep their other workspaces. Klozeo refuses while a subscription has not ended, while a paid period still runs, while a payment is in progress, while a transfer offer is pending, and for the only workspace you can access. The workspace created when an account signs up cannot be deleted on its own, even after a transfer. → Team access
Leave a workspace (November 2026)
Section titled “Leave a workspace (November 2026)”- Any member except the owner can now leave a workspace from Dashboard → Team. Access stops at once, and the member’s assistants lose access to that workspace only. Coming back needs a new invitation. The owner cannot leave: Klozeo refuses with
403and the codeteam_owner_leave, and the owner transfers the workspace first. Removing a member or an invitation now asks for confirmation. When an admin leaves, or a member is removed, the dialog lists the API keys and webhooks that person created, unselected: unselected ones stay as they are, and selected keys are revoked and selected webhooks deleted. → Team access
API keys with a scope and an expiry (November 2026)
Section titled “API keys with a scope and an expiry (November 2026)”- In Dashboard → API Keys, a new key takes an access and an expiry. Access is Full access (the default), Read-only (
read) or Write-only (write). Expiry is Never (the default), 30, 90 or 365 days. An expired key stays in the list until you revoke it, and it no longer authorizes any request, on the REST API and on the MCP server alike. Existing keys are unchanged. → Access and expiry
Transfer a paid workspace (November 2026)
Section titled “Transfer a paid workspace (November 2026)”- A workspace with an active subscription can now be transferred. When the client accepts, the previous owner’s subscription for it stops, with no refund and no further charge. The workspace keeps its plan until the end of the period already paid. The client can subscribe at any time from Settings, and is first charged on that date, or at once if less than an hour remains. If nobody subscribes, the workspace moves to Free on that date. Transfer refusals add
transfer_billing_unsettled(an unpaid or pending payment) andtransfer_billing_unavailable(the subscription could not be stopped; nothing changed).transfer_subscription_liveis no longer returned. → Hand a workspace to your client
A subscription per workspace (November 2026)
Section titled “A subscription per workspace (November 2026)”- The owner of any workspace can now subscribe it to Pro or Scale from Settings. Each workspace has its own plan and subscription, billed to its owner. A workspace you create starts on Free, without a trial, and every workspace except your first pays the standard price. On
/api/auth/subscription/*,referenceIdnames the workspace and defaults to your first one. A caller who does not own that workspace gets403with the codebilling_workspace_not_owned, orbilling_workspace_transferredif they used to own it. → Team access
Admins manage editors and viewers (November 2026)
Section titled “Admins manage editors and viewers (November 2026)”- On a paid plan, an admin can now invite editors and viewers from Dashboard → Team, remove them or cancel their invitation, and switch a member between editor and viewer. The invitation email names the admin who sent it. Only the owner invites, promotes, changes or removes an admin. → Team access
Connect an assistant to several workspaces (November 2026)
Section titled “Connect an assistant to several workspaces (November 2026)”- On the Claude connector (
https://mcp.klozeo.com/v1/mcp, and browser login onhttps://mcp.klozeo.com/mcp), the consent screen now lets you tick several workspaces. One connection reaches exactly the workspaces you ticked, each with your role there, and the dashboard lists them under the connection. Unticking a workspace on a later consent removes it from the connection. Adding a workspace asks for your consent again and starts the whole connection in read-only. Writing is offered only when your role allows it in every ticked workspace. Workspaces where you are anadminare now offered, on the ChatGPT screen too. The ChatGPT connector still takes one workspace per connection. → MCP authorization
Who created each key and webhook (November 2026)
Section titled “Who created each key and webhook (November 2026)”- Webhook objects add
created_by: the user ID of the person who created the webhook. It appears inGET /webhooks, in the responses ofPOST /webhooksandPATCH /webhooks/{id}, in the account export, and in the MCPlist_webhookstool. A webhook created with an API key records the account owner.created_byisnullonce that person’s account is deleted. Existing webhooks record the account owner. GET /api-keysaddscreated_byto each key, with the same meaning.- In the dashboard, the API keys and Webhooks pages show who created each item. The owner, and admins on a paid plan, create, list and revoke keys and webhooks in the selected workspace.
Choose the workspace in Claude (November 2026)
Section titled “Choose the workspace in Claude (November 2026)”- The Claude connector (
https://mcp.klozeo.com/v1/mcp) has an eleventh tool,list_workspaces: the workspaces the connection reaches, with each one’sid,nameand your role there. Every other tool accepts an optionalworkspace_id. A connection with one workspace works exactly as before. When a connection reaches several workspaces, a call withoutworkspace_idreturnsWORKSPACE_REQUIRED, and each result names the workspace it acted in. Aworkspace_idoutside the connection returnsRESOURCE_NOT_FOUND. The ChatGPT connector and API keys are unchanged. → MCP
API key scopes (November 2026)
Section titled “API key scopes (November 2026)”GET /api-keysaddsscopeandexpires_atto each key.scopeisfull,readorwrite. Every existing key isfulland works as before, and so is a key created in the dashboard.expires_atis the key’s expiry in Unix seconds, ornullwhen it never expires. Existing fields are unchanged.- The API enforces a key’s scope, through the REST API and the MCP server with a key. A
readkey reads like a viewer member: it cannot write, and it cannot read webhooks, API keys or the account export. Awritekey can create and update leads (single and batch), add and edit notes, and add and edit custom attribute values. It cannot read, list, export or delete anything, and it cannot change a configuration. A request a scope does not allow answers403with codeforbidden. Areadkey’s refused write says “This API key is read-only”; awritekey’s refused request says “This API key can only create and update leads”. Afullkey is unchanged.
Invite an admin from the dashboard (November 2026)
Section titled “Invite an admin from the dashboard (November 2026)”- The owner can now invite a member as
adminfrom Dashboard → Team, and switch a member to or fromadmin. In the dashboard, an admin manages API keys and webhooks, deletes leads in batch and recalculates the scores of all leads. Only the owner manages the team. → Team access
Which API key wrote each change (November 2026)
Section titled “Which API key wrote each change (November 2026)”- Lead history entries, in
GET /leads/{id}/changesand in the account export, addapi_key_id: theidof the API key behind a change made with a key, through the REST API or the MCP server. It stays after the key is revoked; entries written before this release have none. For such a changeactor_idis still the account owner. A change made in the dashboard has noapi_key_id. A change made by an assistant connected through OAuth has none either, and itsactor_idis the member who connected the assistant. Existing fields and webhooks are unchanged. → Audit trail
The admin member role in the API (November 2026)
Section titled “The admin member role in the API (November 2026)”- The API recognizes a new member role,
admin, for the people who wire a workspace: an admin manages API keys and webhooks, deletes leads in batch and rescores leads. The team, the account export, billing, ownership and workspace deletion stay with the owner. No member can be given theadminrole yet. - In the account export, a member’s
rolecan now beadmin, besideseditorandviewer. → Export your account - The
403message of these endpoints is now “Only the workspace owner or an admin can perform this action”. Theforbiddencode is unchanged.
SDKs wait before retrying a rate-limited request (November 2026)
Section titled “SDKs wait before retrying a rate-limited request (November 2026)”- On a
429withoutRetry-After, the Python SDK now waits 10 seconds before retrying, andRateLimitedError.retry_afteris10instead of0. → Rate limits - Both SDKs raise
RateLimitedErrorwith coderate_limit_exceededfor every429, even when its body is not JSON. The TypeScript SDK also falls back to its 60-second wait whenRetry-Afteris not a number of seconds.
Account rate limit (November 2026)
Section titled “Account rate limit (November 2026)”- All API keys, assistant connections and dashboard sessions of one account now also share an account budget per 10-minute window: Free 2,500, Pro 62,500, Scale 250,000 requests, or more when the account keeps more keys and assistant connections than its plan allows. Per-key limits are unchanged. → Rate limits
- A new
X-RateLimit-Scopeheader says which limit theX-RateLimit-*headers describe:credentialoraccount. → Rate limits
Attribute and note changes in the lead history (November 2026)
Section titled “Attribute and note changes in the lead history (November 2026)”GET /leads/{id}/changesnow records every custom attribute and note change with the member who made it (for an API key, the account owner). Adding, changing or removing an attribute writes anupdatedentry withreasonattribute:<name>and the lead before and after. Adding, editing or removing a note writes anote.created,note.updatedornote.deletedentry holding the note before and after. Thecreatedentry now includes the attributes sent with the lead, and deleting a lead keeps its attributes in thedeletedentry and writes anote.deletedentry (reasonlead:deleted) for each of its notes. These entries also appear in the account export. Webhooks are unchanged. → Audit trail
First-visit source in the account export (November 2026)
Section titled “First-visit source in the account export (November 2026)”GET /account/exportaddssignup_first_touch: where the account owner came from on their first visit, as recorded at sign-up (referrer,landingand theutm_*tags), ornullwhen nothing was recorded. Existing fields are unchanged. → Export your account
Workspace id in lead history (November 2026)
Section titled “Workspace id in lead history (November 2026)”- Lead history entries, from
GET /leads/{id}/changesand in the account export, now includeworkspace_id, the workspace the entry belongs to.user_idstays, with the same value asworkspace_id. → List lead changes
Timestamped webhook signatures and secret rotation (November 2026)
Section titled “Timestamped webhook signatures and secret rotation (November 2026)”- Webhooks with a secret now also send
Klozeo-Signature: t=<unix seconds>,v1=<signature>, an HMAC-SHA256 of<t>.<raw body>. Rejecting a timestamp older than 5 minutes stops replayed requests.X-Webhook-Signatureis unchanged. → Webhooks PATCH /webhooks/{id}accepts a newsecret. The previous secret keeps signingKlozeo-Signaturefor 24 hours, so you can rotate without dropping events. → Webhooks- The TypeScript SDK adds
verifyWebhookSignature(rawBody, header, secret), the Python SDKverify_webhook_signature(raw_body, header, secret), both with a 300-second default tolerance. - The dashboard generates a signing secret for each new webhook and can rotate it.
Redeliver webhook events (November 2026)
Section titled “Redeliver webhook events (November 2026)”POST /webhooks/deliveries/{id}/redeliverqueues adeaddelivery again, with the same event ID and body and a new delivery ID, within 72 hours of the event, one queued redelivery per event, and up to 100 redeliveries per hour per account. → Webhooks- A
deaddelivery now keeps its payload 72 hours after its event so it can be redelivered; it used to be cleared at once. Delivered payloads are still cleared at once, and a delivered redelivery clears its original’s payload too. - Delivery receipts gain
redelivery_of. The dashboard’s recent deliveries list has a Redeliver button. The TypeScript SDK addswebhooks.redeliver(deliveryId), the Python SDKredeliver_webhook_delivery(delivery_id).
Edit and pause webhooks (November 2026)
Section titled “Edit and pause webhooks (November 2026)”PATCH /webhooks/{id}changes a webhook’surl,eventsoractivestate without deleting it. Absent fields keep their value. → Webhooks"active": falsepauses a webhook: nothing is sent, and queued deliveries and events raised while paused appear in the delivery history asdeadwith reasonpaused."active": trueresumes delivery of new events. The dashboard’s Webhooks page has Edit and Pause/Resume buttons.- The TypeScript SDK adds
webhooks.update(id, input), the Python SDKupdate_webhook(webhook_id, update).
Full account export (November 2026)
Section titled “Full account export (November 2026)”- New
GET /account/export, owner only: one JSON file with your scoring rules, webhooks (never their secrets), members, every lead with its attributes and notes, and the history of your current leads. The TypeScript SDK addsclient.account.export()and the Python SDKexport_account(). → Account - The dashboard’s Settings page has a Download export button for the owner. → Export your account
Complete pages with empty sort values (November 2026)
Section titled “Complete pages with empty sort values (November 2026)”GET /leadswithnext_cursorno longer skips leads whose sort field is empty. Sorted by city, rating or score, the leads without a value come last in ascending order and first in descending order, and every one of them is now returned. Leads without a creation date are no longer lost after the first page of the default sort. MCPlist_leads, the SDKs and exports page the same way. → Leads
Notes and custom attributes in exports (November 2026)
Section titled “Notes and custom attributes in exports (November 2026)”GET /leads/exportnow includes custom attributes and notes. JSON nestsattributesandnotesin each lead. CSV and XLSX keep every existing column in place and append anotescolumn, then oneattr:<name>column per attribute name used in your account, sorted by name. The dashboard export gets them too. → Export- Exports are streamed. A failure once the download has started interrupts it instead of returning an error status.
Oldest first in lead lists (November 2026)
Section titled “Oldest first in lead lists (November 2026)”GET /leadsnow honours an explicitsort_order=ascwithsort_by=created_at, or with nosort_by, and lists oldest first. It used to return newest first. Withoutsort_orderthe order is unchanged: newest first forcreated_at, ascending for other fields. MCPlist_leadsand the SDKs passsort_orderthrough and get the same fix. → Leads- Pagination follows the requested direction:
next_cursorfrom an oldest-first page continues oldest first.
Score changes in the audit trail (November 2026)
Section titled “Score changes in the audit trail (November 2026)”- Every change to a lead’s stored score now adds a
scoredentry toGET /leads/{id}/changes, with who caused it and why inreason:score:refreshafter a lead or custom attribute write,score:recalculateforPOST /leads/{id}/scoreandPOST /leads/score/batch,score:rulesfor the automatic rescore after a scoring rule change (noactor_id). A recalculation that leaves the score unchanged adds nothing. Scores, webhooks and exports are unchanged. → Audit trail GET /leads/{id}/changesacceptsaction, a comma-separated list of actions to keep, applied beforelimit. Without it the response is unchanged. → Leads
Browser login on /mcp (November 2026)
Section titled “Browser login on /mcp (November 2026)”https://mcp.klozeo.com/mcpaccepts browser login (OAuth) in addition to dashboard API keys. A client that supports MCP authorization signs in through Klozeo and gets the same ten tools, scopes and consent as/v1/mcp; an API key still gives all 35 tools. → MCP- Browser authorization no longer creates an API key. Existing API keys, including keys created by earlier browser connections, keep working until revoked.
- A request to
/mcpwith no credential now receives401with an OAuth discovery challenge instead of an anonymous session.
Any MCP client can sign in with its published identity (November 2026)
Section titled “Any MCP client can sign in with its published identity (November 2026)”- MCP OAuth accepts every client that publishes an HTTPS Client ID Metadata Document, such as Claude Code and VS Code, not only Claude and ChatGPT. A callback on
localhostor127.0.0.1may use any port. Dynamic registration still works. → MCP
SDKs identify themselves (November 2026)
Section titled “SDKs identify themselves (November 2026)”- The TypeScript and Python SDKs now send
User-Agent: klozeo-sdk-typescript/<version>andklozeo-sdk-python/<version>on every request. Nothing else changes.
Blank lead names refused (November 2026)
Section titled “Blank lead names refused (November 2026)”- A lead
namemade only of spaces now counts as missing.POST /leads,POST /leads/batchand MCPcreate_lead/batch_create_leadsalready refused an empty name; they now also refuse" "withname is required(400, or a per-item error in a batch). Such a name used to be stored as an empty name. PUT /leads/{id},PUT /leads/batch, MCPupdate_leadandupdate_leadon the ChatGPT connector now remove surrounding spaces fromnameand refuse a blank one the same way, leaving the lead unchanged. They used to store it as sent. → Leads
Pro and Scale prices (November 2026)
Section titled “Pro and Scale prices (November 2026)”- Pro is $30 per month (€30 in the eurozone) and Scale $80 (€80), excl. VAT, per account. They were $29 and $79. → FAQ
Founder prices at checkout (November 2026)
Section titled “Founder prices at checkout (November 2026)”- While the founder offer is open, Checkout applies the founder price of the current tier to Pro and Scale. It is kept for as long as the subscription stays active, Pro or Scale, and ends on cancellation; a later subscription gets the tier available then. An unfinished Checkout holds its place until it expires after one hour; a new Checkout replaces the previous one. → FAQ
Trial end reminders (November 2026)
Section titled “Trial end reminders (November 2026)”- The account owner gets an email 3 days and then 1 day before the 14-day Pro trial ends, with the end date and what changes on Free. No reminder is sent once the account has subscribed.
save_leads keeps tags as sent (November 2026)
Section titled “save_leads keeps tags as sent (November 2026)”save_leadson the Claude connector stores tags exactly as sent, as every other write already does. It used to reject a lead whose tags contained a comma, brace, quote or backslash, or wereNULL. Tags still need 1–64 characters each, at most 20 per lead (invalid_tags). → MCP
Save leads from Claude (November 2026)
Section titled “Save leads from Claude (November 2026)”- The Claude connector (
https://mcp.klozeo.com/v1/mcp) has a tenth tool,save_leads: paste or type up to 50 contacts and Claude saves them in one step. Existing leads with the same email, or the same phone and a similar name, are updated instead of duplicated: only non-empty fields change, tags are added, locked fields and do-not-contact are kept. A lead with the same name and city, or the same phone but a name too different to merge (such as an added legal form), is created and flagged as a possible duplicate of the existing lead, so you decide. The result lists what was created, merged, flagged as a possible duplicate or rejected, without repeating contact details. Retries with the same key never save twice. Saves fire yourleads.createdandleads.updatedwebhooks. The ChatGPT connector is unchanged. → MCP - On an empty workspace,
list_leadsandget_statson the Claude connector return anext_stepline telling Claude what to offer first: paste contacts to save, or, with read-only access, that the workspace owner adds leads. → MCP
Lead create keeps status and tags (November 2026)
Section titled “Lead create keeps status and tags (November 2026)”POST /leadsandPOST /leads/batchnow store thestatusthey receive, asPUT /leads/{id}already did. Previously it was ignored and every new lead wasnew. A lead created withoutstatusis stillnew. A duplicate merge still never changes the status. Thelead.createdwebhook carries the storedstatus. → Leads- A
statuslonger than 50 characters is rejected with the messagestatus must be at most 50 characters:400onPOST /leads,PUT /leads/{id}and MCPupdate_lead, and a per-item error onPOST /leads/batchandPUT /leads/batch. Updates used to fail with500or a generic item error, and creates used to ignore it. - Tags sent on create are stored exactly as sent. Previously a tag containing a comma was split in two, a tag
NULLwas stored as a null value, and a tag containing a quote, brace or backslash failed the request. This applies toPOST /leads,POST /leads/batchand MCPcreate_lead/batch_create_leads.
TypeScript and Python SDK response fixes (November 2026)
Section titled “TypeScript and Python SDK response fixes (November 2026)”- TypeScript filters preserve empty values such as
city().eq("")when sending requests. - Leads returned by both SDKs now include contact-opposition metadata and embedded notes. Python accepts empty collections returned as
nullin lead pages, batch results, merge receipts, notes, attributes, scoring rules, and webhooks. Read-only lead fields are excluded from Python create and batch-create requests.
14-day Pro trial, one user on Free (November 2026)
Section titled “14-day Pro trial, one user on Free (November 2026)”- Every new account, including one created from ChatGPT or Claude, starts with a 14-day Pro trial: Pro limits (50,000 leads, 2,500 requests per 10 minutes, team seats), no card. Settings and the dashboard sidebar show the days left. Existing accounts are unchanged.
- When the trial ends without an upgrade, the account moves to Free. Nothing is deleted; leads stay readable and editable; only new leads above 2,500 are refused. Upgrading later from Settings restores Pro at once. A subscription canceled after a trial ends on Free.
- Free has one user. A Free account cannot send invitations (
403 team_member_limit,limit: 0). Members of a Free account keep read-only access, whatever their stored role; they get their role back when the owner subscribes. → Team access
VAT at checkout (November 2026)
Section titled “VAT at checkout (November 2026)”- Paid plan prices exclude VAT. Checkout now asks for a billing address and adds VAT where it applies (20% in France). Businesses in the EU outside France can enter their VAT number to have VAT reverse-charged. Plan changes in Settings → Manage billing apply the same rule, and invoices show the VAT breakdown.
Paid plans kept during payment retries (November 2026)
Section titled “Paid plans kept during payment retries (November 2026)”- A Pro or Scale subscription keeps its limits while Stripe retries a failed payment (
past_due). The account returns to Free (2,500 leads, 250 requests per 10 minutes) when the subscription ends: canceled, or unpaid after the last retry. This replaces the earlier rule that a failed payment downgraded immediately. - After Checkout, Settings shows that the plan is activating until Stripe confirms it. Former subscribers on Free keep access to their invoices through Settings → Manage billing.
ChatGPT default OAuth settings (November 2026)
Section titled “ChatGPT default OAuth settings (November 2026)”- MCP OAuth accepts ChatGPT’s published client identity (
https://chatgpt.com/oauth/client.json), so a ChatGPT app created with the default OAuth settings connects; dynamic registration keeps working. Every authorization response redirected to the client now carriesiss(RFC 9207), and the authorization server metadata advertisesauthorization_response_iss_parameter_supported: true. → MCP
Webhooks committed with their write (November 2026)
Section titled “Webhooks committed with their write (November 2026)”- Every write that sends a webhook (leads, batches, notes, do not contact, field locks, enrichment, scores, MCP writes) now queues its deliveries in the same database transaction: a committed write always has its event queued, and a write that is rolled back queues none. If the event cannot be queued, the write is rolled back and fails with
500. A request that ends without a response may still have committed, so retrying it may repeat the write and its event. Note writes now answer500instead of404for failures other than a missing note or lead. → Webhooks
Custom attributes kept on merge (November 2026)
Section titled “Custom attributes kept on merge (November 2026)”- A duplicate merge (
POST /leads,POST /leads/batch, MCPcreate_lead/batch_create_leads) adds the incoming custom attributes that the lead does not have yet and updates the ones it has with the same type. The response lists each incoming attribute inattribute_changesasadded,updatedorignoredwith areason. The MCP toolscreate_leadandbatch_create_leadsnow acceptattributes. Audit snapshots and thelead.updatedwebhook include the merged attributes. → Deduplication
Field locks (November 2026)
Section titled “Field locks (November 2026)”- Lock a lead’s field with
POST /leads/{id}/locks/{field}(unlock withDELETE): duplicate merges and imports (POST /leads,POST /leads/batch, MCPcreate_lead/batch_create_leads) and company enrichment never overwrite it, and the merge response lists the skipped fields inskipped_locked_fields. Explicit updates still write locked fields. Leads exposelocked_fields. Each lock and unlock is recorded in the lead’s audit trail with the acting user and fireslead.updated.lead.createdandlead.updatedpayloads carrylocked_fields. CSV and XLSX exports add alocked_fieldscolumn. → Deduplication - MCP: the classic catalogue adds
create_lead_field_lockanddelete_lead_field_lock(35 tools).get_leadreturnslocked_fieldson both catalogues, as do classiclist_leadssummaries, and mergedcreate_lead/batch_create_leadsresults listskipped_locked_fields. The nine-tool OpenAI and Claude connector catalogue does not change. → MCP - SDKs (TypeScript and Python):
leads.lockField/leads.unlockFieldandlock_field/unlock_field,lockedFields/locked_fieldson leads,skippedLockedFields/skipped_locked_fieldson create and batch create results. → TypeScript, Python - Dashboard: the lead panel shows locked fields and lets owners and editors lock or unlock them; viewers see them read-only. → Deduplication
Tags kept on merge (November 2026)
Section titled “Tags kept on merge (November 2026)”- A duplicate merge (
POST /leads,POST /leads/batch, MCPcreate_lead/batch_create_leads) now adds the incoming tags to the existing lead instead of replacing them. An explicitPUT /leads/{id}still replaces the list. → Deduplication
Do not contact (November 2026)
Section titled “Do not contact (November 2026)”- Leads expose
do_not_contact,do_not_contact_at,do_not_contact_originanddo_not_contact_by. Set the opposition withPOST /leads/{id}/do-not-contactor"do_not_contact": trueon create/import. Merges, imports, updates and MCP tools never lift it; onlyDELETE /leads/{id}/do-not-contactdoes, recorded in the lead’s audit trail. Filter withfilter=and.eq.do_not_contact.true; exports add two columns.lead.createdandlead.updatedwebhooks carrydo_not_contact(always),do_not_contact_atanddo_not_contact_origin, never the authordo_not_contact_by: read it withGET /leads/{id}. Audit snapshots keep the opposition, date and origin but never the member identifier: the actor isactor_id, cleared when that member deletes their account. → Deduplication
Launch pricing (November 2026)
Section titled “Launch pricing (November 2026)”-
Free stores 2,500 leads. Pro stores 50,000 for $29/month; Scale stores 250,000 for $79/month. Prices are per account; team seats are included.
-
API budgets per 10 minutes: Free 250, Pro 2,500, Scale 5,000. Batch sizes remain 100 on Free and 500 on Pro/Scale.
-
Active or trialing Pro/Scale subscriptions apply the corresponding limits. Past-due/unpaid or deleted subscriptions return to Free (2,500 leads), with no grace period. Scheduled cancellations keep access until period end. Existing leads are preserved after a downgrade; new leads cannot be added above the limit.
-
At storage capacity,
POST /leads/batchreturns 207 Multi-Status, including when every item fails (previously 403). Each new lead fails with a quota error; duplicate merges still succeed. SinglePOST /leadsreturns 403leads_limit_reached. Existing leads are retained after a downgrade.
Security update (October 2026)
Section titled “Security update (October 2026)”- Key lists and MCP configuration pages never return an existing raw key. The staged storage cleanup retains legacy raw prefixes during the reversible rollout, then removes them after production validation.
- The classic MCP catalog now has 32 tools. API key creation is available in the dashboard (the REST creation endpoint returns 405); no MCP tool creates keys or redirects to key creation. Listing and revocation remain available.
- Dashboard requests use an authenticated internal channel; the API rechecks current team membership on each request. During rollout, legacy proxy headers can only reduce permissions after that same membership check.
- Banned accounts lose REST, MCP and dashboard data access. Temporary-ban and API-key timestamp timezone migration is tracked separately.
- Billing policy: an
activeortrialingPro subscription grants Pro access.past_dueorunpaidbecomes Free (100 leads) at the next subscription webhook, with no grace period. Rolling back an image does not restore the prior stored plan. - Existing REST API keys remain valid during the storage migration. If you no longer have a saved key, create a replacement in the dashboard, update your integration, then revoke the old key.
v1.4.0 (August 2026)
Section titled “v1.4.0 (August 2026)”You can now invite teammates to the workspace, prove every merge in an audit trail, and rely on clearer batch HTTP status codes, without changing how n8n or the SDKs authenticate.
- Team seats: roles
owner/editor/viewer. Viewers get403on mutations; API key management stays owner-only. Direct API-key callers (n8n, SDKs, cURL) remain owners (full backward compatibility). → Team access - Lead audit trail:
GET /leads/{id}/changesreturnscreated/updated/merged/deletedentries with before/after snapshots anddedup:…reasons on merges. → Deduplication - Batch status codes:
PUT/DELETE /leads/batchreturn207 Multi-Statuson partial failure (walkresults[]); emptyids/leadsarrays return400. → Batch operations - Conflict on create/update:
POST /leadsandPUT /leads/{id}return409when email orsource_idcollides with another lead (including rare unique-index races on create that cannot be merged). - Rate limit reset: every response includes
X-RateLimit-Reset(Unix timestamp of the next free slot in the sliding window). - Webhook semantics: a dedup merge fires
lead.updated(notlead.created); batch create may emit bothleads.createdandleads.updated.
v1.3.0 (April 2026)
Section titled “v1.3.0 (April 2026)”You can now track where each lead stands in your pipeline without opening a dialog or writing a line of code.
- Lead status: every lead now has a status field:
new,contacted,qualified,disqualified,converted. Update it directly from the leads table with a single click: no form to open, no page to reload. - Filter by status: add a status filter to any view to focus on the leads that matter right now. Works with all existing filters and exports.
- API + MCP support: set or update status via
PATCH /leads/:id, any of the four SDKs, or directly from your AI assistant with theupdate_leadtool.
v1.2.0 (April 2026)
Section titled “v1.2.0 (April 2026)”The MCP server expanded from 18 tools. Additions included:
- Batch operations:
batch_create_leads,batch_update_leads,batch_delete_leads. Create or update up to 500 leads in one call. Deduplication runs per item in batch create, so you can safely re-import data without worrying about duplicates. - Attributes CRUD:
list_attributes,create_attribute,update_attribute,delete_attribute. Manage custom fields on any lead directly from your AI assistant. - Scoring management:
create_scoring_rule,get_scoring_rule,update_scoring_rule,delete_scoring_rule,update_all_scores. Build and iterate on scoring rules without opening the dashboard. - API Key management:
list_api_keys,delete_api_key(creation is dashboard-only). - Note editing:
update_noteto edit note content after the fact.
Batch webhook events (leads.created, leads.updated, leads.deleted, leads.scored) fire a single grouped notification per operation instead of N individual ones.
v1.1.0 (April 2026)
Section titled “v1.1.0 (April 2026)”You can now integrate Klozeo directly from your language’s package manager, no raw HTTP needed.
- TypeScript / JavaScript:
npm install @klozeo/sdk - Python:
pip install klozeo - Go:
go get github.com/lbframe/klozeo-sdk-go - Rust:
cargo add klozeo
All four clients share the same API surface: a fluent filter builder, automatic pagination, batch operations, and typed errors. Pages are fetched transparently as you iterate; you never write cursor logic yourself.
→ TypeScript SDK documentation · Python · Go · Rust
The MCP integration now exposes 18 tools, up from 13 at launch. The five additions cover scoring and webhooks: you can now list and apply scoring rules, and manage webhook endpoints, all from your AI assistant without leaving the conversation.
v1.0.0 (March 2026)
Section titled “v1.0.0 (March 2026)”Initial release.
- Leads API: full CRUD (create, read, update, delete). Fields include name, email, phone, city, website, source, rating, tags, score, and custom attributes.
- Notes API: attach and manage timestamped notes on any lead.
- Attributes API: extend any lead with typed custom fields (text, number, boolean, list) without schema migrations.
- Scoring Rules API: define expression-based rules to compute a 0–100 score per lead automatically.
- Webhooks API: subscribe to lead events and receive real-time HTTP notifications.
- Export: download your full lead database as CSV, JSON, or XLSX with full filter and sort support.
- Cursor-based pagination: keyset pagination with
limit,cursor,sort_by, andsort_orderparameters. Opaque cursors, no offset math. - Filtering: 20+ operators covering text, numeric, tag arrays, location radius, and dynamic attributes. Multiple filters combine with AND/OR logic.
- Auto-deduplication: 4-tier duplicate detection on every
POST /leads(by email, source ID, phone+name similarity, or name+city). Merges use Last Touch Wins strategy. - Batch operations: create, update, or delete up to 100 leads per request (500 on Pro).
- MCP integration: 13 tools at launch for Claude, Cursor, Cline, and any MCP-compatible client. OAuth 2.0 + PKCE authorization, no manual key copy-paste required.