Versioning
Version 1 (/v1) grows by addition. We add routes, parameters, fields and headers; we don't remove or rename them, so ignore fields you don't know. Changes in behaviour, such as a clearer status code, and anything that needs action from you are listed here first. The full reference is at /docs, and the machine-readable versions at api.salesmotion.io/llms.txt and openapi.json.
18 November 2026
REST API: Sync, Account Lists, Company Resolution and Consistent Errors
Added
- GET /v1/me: the organization, API key (type and access level) and user behind a key. Not counted against your allowance; answers 200 with
hasApiAccess: falsewhen API access is off. - Incremental sync on
/v1/accounts,/v1/contactsand/v1/signals:createdAfter,updatedAfterand a keyset cursorafterId, withmeta.nextCursoron ascendingcreatedAt/updatedAtsorts. See Keeping a Copy in Sync. - Contacts return
createdAtandupdatedAtand can be sorted by them. - GET /v1/accounts/{accountId}/contacts and GET /v1/accounts/{accountId}/signals.
- GET /v1/account-lists and GET /v1/account-lists/{listId}/accounts, read-only.
- GET /v1/companies/resolve?input= and POST /v1/companies/resolve for 1-25 inputs: domains, URLs, stock symbols, company IDs and names, with
found,not_foundormultiple_matches. Idempotency-Keyheader on POST /v1/accounts: a retry with the same key and body within 24 hours returns the original response withIdempotent-Replayed: true; the same key with a different body returns 422 (idempotency_conflict).- Company news filters:
afterDate,beforeDateandtextQueryon /v1/companies/{companyId}/news-articles. X-Request-Idon every/v1response, equal tometa.requestId,error.requestIdandrequestIdin/v1/usage/requests.RateLimit-Limit,RateLimit-RemainingandRateLimit-Reset(seconds) headers, andRetry-Afteron 429./v1/usageaddswindowTypeandwindowDays.meta.totalCountIsEstimateon lists, andmeta.cappedCountsandmeta.countLimiton/v1/signals/counts.- Account insights:
profile.companyId, andidon every included contact and signal. - Documented fields:
hubspotUrlandemployeeCountDetailson accounts,employeeCountDisplayandemployeeCountAlternativeson companies, and theallandaccountscounters.
Changed
- Errors share one body:
{ error: { code, message, param?, allowedValues?, requestId }, message, statusCode }.erroris now an object; on some errors it used to be a string such as"Forbidden".message,statusCodeand the validationerrorslist are unchanged keys. Messages are clearer: an unknown parameter suggests a close match, an invalid value lists the allowed values. - Unknown
/v1paths return a JSON 404 instead of a 200 HTML page. - A query that runs too long returns 504 (code
timeout) instead of 408. - 401 responses say whether the key is missing, malformed, or invalid or revoked, and carry
WWW-Authenticate: Bearer. POSTandDELETE /v1/accountswith a read-only or service key return 403 even when the body is invalid.GET /v1/contacts/{contactId}with a non-numeric ID returns 400 instead of 500./v1/contactsand/v1/signalsfiltered byaccountIdleave out removed accounts, like the unfiltered lists.- Lists of contacts, signals and company news count exactly up to 500 rows; above that,
totalCountis an estimate flagged bymeta.totalCountIsEstimate. SignaltextQuerynow reports a realtotalCount./v1/signals/countscounts each type up to 500 and lists capped types inmeta.cappedCounts. - Timestamps end in
Z:createdAt,updatedAt,addedOn,lastRefreshAt, signalrelevance.assessedOn, newsdatePublishedand earnings-callhappenedAt(when it has a time). Signaldateand other calendar days keep no offset. See Dates and Times. - Contact
textQuerymatches a first and last name ("Jane Doe"), andonlyWithFields=talkingPointsworks on contacts. - Documentation: the default accounts order is newest first (by ID, descending), and best match first with
textQuery. The behaviour did not change; the reference saidmainScore. - OpenAPI document only, requests and responses unchanged: readable
operationIds (e.g.listAccounts), one tag per resource,requiredrelaxed toidon entity schemas becauseonlyWithFieldscan leave out any other field, a sharedErrorschema with 400/401/403/404/429/504 on every route, andbearerFormatas an API key (sk_…). Regenerate any client generated from the earlier document.
18 November 2026
MCP Server 4.6 and 4.7
Added
- Life Sciences tools for organizations with the Life Sciences pack:
get_clinical_trials,get_trial_radarandget_company_tags, and thetrial_watchskill. add_accountsfor connections made with a personal API key that has read and write access: add up to 25 companies as accounts.- The tool list follows the key: Life Sciences tools appear with the pack,
add_accountswith a read-and-write key. - Account IDs, company IDs and "Open in Salesmotion" links on accounts, contacts and signals; owner names, and
mine=truefor your own accounts; the account name on every signal row; AI analysis on earnings calls.
Changed
- A revoked or invalid key gets HTTP 401, so the assistant asks you to sign in again.
- Sign-in checks that the organization has API and workspace access and otherwise says the MCP server is part of the Enterprise plan.
- Usage analytics keep only enum, ID, date and paging arguments; company and person names, search terms and feedback text are redacted.
- Shorter tool descriptions, one time budget per tool call, and next steps on empty results.
16 November 2026
REST API: Adding and Removing Accounts
Added
- POST /v1/accounts adds up to 25 companies as accounts, and DELETE /v1/accounts/{accountId} removes one. Both need a personal API key created with read and write access; keys are read only unless created that way.