API Changelog

New routes, parameters and fields, and changes in behaviour, for the REST API and the MCP server.

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: false when API access is off.
  • Incremental sync on /v1/accounts, /v1/contacts and /v1/signals: createdAfter, updatedAfter and a keyset cursor afterId, with meta.nextCursor on ascending createdAt/updatedAt sorts. See Keeping a Copy in Sync.
  • Contacts return createdAt and updatedAt and 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_found or multiple_matches.
  • Idempotency-Key header on POST /v1/accounts: a retry with the same key and body within 24 hours returns the original response with Idempotent-Replayed: true; the same key with a different body returns 422 (idempotency_conflict).
  • Company news filters: afterDate, beforeDate and textQuery on /v1/companies/{companyId}/news-articles.
  • X-Request-Id on every /v1 response, equal to meta.requestId, error.requestId and requestId in /v1/usage/requests.
  • RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset (seconds) headers, and Retry-After on 429. /v1/usage adds windowType and windowDays.
  • meta.totalCountIsEstimate on lists, and meta.cappedCounts and meta.countLimit on /v1/signals/counts.
  • Account insights: profile.companyId, and id on every included contact and signal.
  • Documented fields: hubspotUrl and employeeCountDetails on accounts, employeeCountDisplay and employeeCountAlternatives on companies, and the all and accounts counters.

Changed

  • Errors share one body: { error: { code, message, param?, allowedValues?, requestId }, message, statusCode }. error is now an object; on some errors it used to be a string such as "Forbidden". message, statusCode and the validation errors list are unchanged keys. Messages are clearer: an unknown parameter suggests a close match, an invalid value lists the allowed values.
  • Unknown /v1 paths 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.
  • POST and DELETE /v1/accounts with 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/contacts and /v1/signals filtered by accountId leave out removed accounts, like the unfiltered lists.
  • Lists of contacts, signals and company news count exactly up to 500 rows; above that, totalCount is an estimate flagged by meta.totalCountIsEstimate. Signal textQuery now reports a real totalCount. /v1/signals/counts counts each type up to 500 and lists capped types in meta.cappedCounts.
  • Timestamps end in Z: createdAt, updatedAt, addedOn, lastRefreshAt, signal relevance.assessedOn, news datePublished and earnings-call happenedAt (when it has a time). Signal date and other calendar days keep no offset. See Dates and Times.
  • Contact textQuery matches a first and last name ("Jane Doe"), and onlyWithFields=talkingPoints works 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 said mainScore.
  • OpenAPI document only, requests and responses unchanged: readable operationIds (e.g. listAccounts), one tag per resource, required relaxed to id on entity schemas because onlyWithFields can leave out any other field, a shared Error schema with 400/401/403/404/429/504 on every route, and bearerFormat as 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_radar and get_company_tags, and the trial_watch skill.
  • add_accounts for 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_accounts with a read-and-write key.
  • Account IDs, company IDs and "Open in Salesmotion" links on accounts, contacts and signals; owner names, and mine=true for 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