Changelog
Every change across the developer surfaces you build on — the SDK, React components, Partner API, and MCP server — in one place. We ship constantly.
- APIFindable Assistant2026-11-17
Server-side diagnostics for streaming Assistant requests are now emitted as structured single-line log records with the request id. Errors during a stream still surface the same way to you: the request keeps its status code, and a failed stream sends the same error event as before. Request and response shapes are unchanged.
- APIFindable Assistant2026-11-12
The 400 returned for use_agentic_rag=false now reads "…every Assistant request now uses agentic RAG…" where it said "every Ask request". The status code and the request and response shapes are unchanged, so this only matters if your code matches on the message text.
- MCPMCP Server2026-11-11
`ask_findable` is now `ask_assistant`, titled "Findable Assistant", with the same input and output. Use `ask_assistant` from now on. `ask_findable` is no longer listed but still works and will keep working, so cached schemas and saved instructions that name it are not broken, and a `threadId` from either name continues under the other. Calls under either name count against the same rate limits. Other tool descriptions and `fallbackGuidance` now point at `ask_assistant`. Earlier entries in this list that mention `ask_findable` mean the same tool. Refresh cached tool schemas.
ask_assistantask_findablesearch_documentsget_documentlist_project_documentsget_portfoliowhoami - MCPMCP Server2026-11-10
ask_findable now answers an organisation whose free trial has ended with a trial_ended error that says so, instead of a general failure.
ask_findable - MCPMCP Server2026-11-10
ask_findable now answers an organisation on a free trial that has used all its Assistant questions with a trial_limit_reached error that says so, instead of a general failure.
ask_findable - APIDocuments2026-11-10
Large bursts of uploads are now processed in batch. When one API key requests more than 100 upload URLs for the same building within 10 minutes, the documents after the first 100 are processed in batch instead of one at a time. They upload as before, but can take a few hours longer to finish processing. Smaller bursts and uploads spread over time are unaffected. Request and response shapes are unchanged.
- MCPMCP Server2026-11-09
get_document and get_document_metadata now open a document on the same rule as Findable itself: you can open a document shared with you directly, or through a collection, even without access to its whole building, and a file someone attached to their own Ask chat is no longer opened for other people in the building.
get_documentget_document_metadata - MCPMCP Server2026-11-06
prepare_red_flag_generation now talks about a building's red flag instead of a red flag report, in its title, description and input help, matching the rest of Findable. It works exactly as before. Nothing to reconnect for.
prepare_red_flag_generation - MCPMCP Server2026-11-06
The find_resources and get_collection descriptions no longer point to a document-listing tool that does not exist. To find documents, use search_documents scoped to a building or portfolio. Inputs and responses are unchanged.
find_resourcesget_collection - MCPMCP Server2026-11-05
The relaxed retry on an empty search now asks for the documents matching the most of its terms in one search, best matches first, so it is faster and finds documents that match some but not all of the words. Those results have relaxed.step most_terms and relaxed.query null, and each hit lists the terms it matched in matchedTerms. Searches that find documents are unchanged.
search_documents - MCPMCP Server2026-11-04
Internal usage-analytics fix only: ask_findable now records when the answer text finished arriving, which the step timings added earlier today missed. No change to inputs, response shape, or behaviour; agents need take no action.
ask_findable - MCPMCP Server2026-11-04
Internal usage-analytics change only: ask_findable calls now record how long each step took and which conversation they belong to, so slow answers can be traced. No change to inputs, response shape, or behaviour; agents need take no action.
ask_findable - MCPMCP Server2026-11-04
documentType on search_documents now only takes drawing or document (drawings, tegning, dokument and other plain spellings of the two are accepted). Any other value, such as fdv-rapport, used to be ignored without a word and returned unfiltered results; it now returns an invalid_input error. To narrow by kind of document, use category or the query.
search_documents - MCPMCP Server2026-11-04
The relaxed retry on an empty search now always finishes within four seconds and runs at most two of its one-term searches at a time. Inputs and the response shape are unchanged; agents need take no action.
search_documents - MCPMCP Server2026-11-04
When no document matches every term of a query, search_documents now retries with fewer terms (stopwords dropped, then the most specific terms, then each term on its own) and returns those hits as relaxed matches: each hit has relaxedMatch true and matchedTerms, and the result has a relaxed object with the step, the query used and whether more matches exist. Check that a relaxed match fits before relying on it, and call ask_findable if none do. Searches that find documents are unchanged.
search_documents - MCPMCP Server2026-11-04
Ask and the tools that prepare a proposal now have a per-person rate limit, set well above normal use. A call over it returns an error with error: rate_limited, the limit and its windowSeconds, retryAfter in seconds and resetAt, and the same fields come back on an HTTP 429 from the server itself. Wait retryAfter seconds and try again. Inputs and normal results are unchanged.
ask_findableprepare_work_item_actionprepare_red_flag_generation - MCPMCP Server2026-11-04
Internal usage-analytics change only: a call that fails because another service answered with an error is now counted under the status code it answered with. Applies to every tool; logged under whoami because the changelog rule is machine-enforced on the shared instrumentation file. No change to inputs, response shape, or behaviour; agents need take no action.
whoami - APIFindable Assistant2026-11-04
Each API key can now run one Ask request at a time, on /ask and /assistant at both building and owner level, including session tokens minted from the key. A request sent while another is still running is rejected with 429 and a Retry-After header; send the next question when the previous answer has finished. Request and response shapes are unchanged.
- MCPMCP Server2026-11-03
Internal usage-analytics change only: tool calls now record which kind of client made them, how many results a list or search returned, how many buildings a search or ask covered, which ask mode ran, and a more specific code when a call fails. Applies to every tool; logged under whoami because the changelog rule is machine-enforced on the tool files. No change to inputs, response shape, or behaviour; agents need take no action.
whoami - APIReports2026-11-02
The reports endpoints and the report document endpoints now return 403 when the organisation has switched the Red Flag Report module off. Before, these calls kept working, and generating a report kept starting runs.
- APIFindable Assistant2026-11-02
Ask is now the Findable Assistant. New paths: POST /v1/building_owners/{buildingOwnerId}/assistant, POST /v1/building_owners/{buildingOwnerId}/buildings/{buildingId}/assistant and /v1/building_owners/{buildingOwnerId}/assistant-sharepoint/*, with the same requests and responses. The old /ask and /ask-sharepoint paths still work and are deprecated, with no removal date; they now return Deprecation and Link headers pointing to the new ones. The reference moved from /api/ask to /api/assistant, and the old URL redirects.
- MCPMCP Server2026-10-23
`prepare_work_item_action` `create_checklist` now takes the whole checklist in one proposal: `data.items` lists up to 200 items in order, each with `title`, optional `description`, an optional `section` that files it in a folder of that name, and `itemType: "question"` with `answerOptions` (label and disposition; ids optional) for question items. `data.settings_frequencyEnabled` and `data.settings_requireApproval` set the checklist settings. Items are created in the given order and the approval card shows the item count, the first items and the sections. The change still needs human review in Findable. Refresh cached tool schemas.
prepare_work_item_action - APIDocuments2026-10-22
Request Upload URL accepts an optional fileSize (the file size in bytes). When you send it, the returned upload URL only accepts a file of exactly that size, and a different size is rejected by storage with 403. Send it now: fileSize will become required in a later release. Without it, uploads work as before.
- MCPMCP Server2026-10-16
`prepare_work_item_action` can propose `export_checklist_pdf` with `buildingId` and `checklistId` to create a new PDF document of that building checklist in the building's Checklists folder, in any approval state; the PDF states the approval state. It needs edit access to the checklist and upload access to the Checklists folder (or, when it does not exist yet, where it is created). The PDF shows only what you can read when it is created and is marked incomplete when some evidence is hidden from you; everyone who can read the Checklists folder can read it. The result names the new document, and repeating an approved run returns that same document. Checklists with more than 1000 items are refused. The change still needs human review in Findable. Refresh cached tool schemas.
prepare_work_item_action - MCPMCP Server2026-10-16
`prepare_work_item_action` can propose `reopen_checklist` with `buildingId` and `checklistId` to return an approved building checklist to in progress so it can be edited again. It needs administration access to the checklist in that building and is refused unless the checklist is approved. If the approver was given read access when the checklist was sent for approval, that access is withdrawn while access they hold some other way is kept; the approval card says so. The change still needs human review in Findable. Refresh cached tool schemas.
prepare_work_item_action - MCPMCP Server2026-10-15
`prepare_work_item_action` can propose `attach_checklist_item_document` with `buildingId`, `checklistId`, `itemId` and `documentId` to attach one existing document from the same building to that checklist item. It needs upload access to the item and administration access to the document, and is refused while the checklist awaits approval or is approved. Everyone with read, edit or administrate access to the item gets the same access to the document; the approval card says so. The change still needs human review in Findable. Refresh cached tool schemas.
prepare_work_item_action - MCPMCP Server2026-10-15
`query_work_items` has a `checklist_item_notes` operation: pass `checklistId`, `itemId` and exactly one building to read that checklist item's notes (`checklist_item_note` rows, oldest first) in that building. `prepare_work_item_action` can propose `add_checklist_item_note` with `buildingId`, `checklistId`, `itemId` and `content`; notes can be added even while the checklist awaits approval or is approved. The change still needs human review in Findable. Refresh cached tool schemas.
query_work_itemsprepare_work_item_action - MCPMCP Server2026-10-15
`prepare_work_item_action` `add_comment` accepts a routine occurrence that has no row of its own yet: pass its occurrence `taskId` from `query_work_items`. On approval the occurrence is saved on its own and the comment is added to it. The change still needs human review in Findable. No schema change.
prepare_work_item_action - MCPMCP Server2026-10-15
`prepare_work_item_action` can propose linking a task to a system: `create_task` and `update_task` `data` accept `systemId`, the id of a system in the same building, and `update_task` takes `systemId: null` to unlink it. The change still needs human review in Findable. Refresh cached tool schemas.
prepare_work_item_action - APIIntegrations2026-10-15
GET /v1/building_owners/{buildingOwnerId}/integration-status now returns, for every building, how you group it: affiliation (the building's Affiliation field — owner, location or any other grouping, null when unset) and portfolios, each with its id and name (empty when the building is in none). Both sit alongside the existing document count and integration entries, so one call can be grouped by school, location or portfolio in a dashboard without a second lookup. No existing field changed.
- MCPMCP Server2026-10-14
Internal usage-analytics change only: a tool call that returns an error is now counted as a failure. Applies to every tool; logged under whoami because the changelog rule is machine-enforced on the shared instrumentation file. No change to inputs, response shape, or behaviour; agents need take no action.
whoami - APIDocuments2026-10-14
Documents uploaded with Request Upload URL now record the API key that uploaded them: in Findable they show Source 'API · <key name>' and the key as uploader, and files unpacked from an uploaded email or ZIP carry the same. Request and response shapes are unchanged.
- MCPMCP Server2026-10-12
`find_resources` now names a result's parent only when you can read that parent; otherwise `parent` is null. Every candidate, including super-admin name scans, is read-checked, and candidates are ranked before the 200-per-type cap on every path. An access check that cannot be evaluated now fails the call instead of hiding a match. The description now says to call `find_resources` again when the user picks an option that is not in `results`.
find_resources - APIIntegrations2026-10-09
New endpoint: GET /v1/building_owners/{buildingOwnerId}/integration-status returns, for every building the API key can read, its document count (number_of_files) and one entry per connected integration — SharePoint, Interaxo, Plania, Famac, Dalux, Dalux Box or Google Drive — with the status of the most recent sync run, when a full sync last completed, and the export folder where the integration writes back. Connecting a building to another integration adds an entry rather than needing a new endpoint. It replaces GET /v1/building_owners/{buildingOwnerId}/sharepoint-status, which is removed: SharePoint state is now the 'sharepoint' entry under integrations, and the building's external_id is unchanged.
- APIDocuments2026-10-08
New endpoint: GET /v1/building_owners/{buildingOwnerId}/documents/deleted?deleted_since=... lists documents deleted since a point in time across all buildings the key can read, oldest first, so an integration can mirror deletions without re-reading every document. List Documents also accepts include_url=true (with limit up to 200), which adds the signed url and previewUrl to each document so files can be downloaded without one Get Document call each.
- MCPMCP Server2026-10-07
`get_building` now reads the same building profile the Findable app assistant uses. The response fields are unchanged; a missing building now returns `forbidden`, like one you cannot read, instead of `not_found`.
get_building - APIReports2026-10-07
Adding or removing a document on a report now returns 404 unless the report, the document and the existing link all belong to the building in the path. Previously a report or document from another building could be named by id. Requests within the building are unaffected and response shapes are unchanged.
- APIAsk2026-10-06
Non-streaming Ask returns 503 for retryable Smart Search transport failures, including failures while collecting an answer, so integrations can distinguish service unavailability from an internal server error. Streaming Ask keeps its established HTTP 200 response and sends an in-band error event.
- MCPMCP Server2026-10-05
`list_integrations` now also reports Dalux Box (`provider: "dalux-box"`, import only): its connection status with `customerId`, and with `buildingId` whether the building is linked to a Dalux Box file area plus its last import. Refresh cached tool schemas to filter by the new provider.
list_integrations - APISharePoint2026-10-05
New endpoint: GET /v1/building_owners/{buildingOwnerId}/sharepoint-status returns per-building SharePoint sync state — connected or not, the configured export destination folder, the status of the most recent sync run, and when a full sync last completed — for every building the API key can read. Each entry carries the building's external_id (your own identifier for the building) so the data joins cleanly against external systems. Built for joining sync coverage into external dashboards such as Power BI.
- MCPMCP Server2026-10-01
`list_integrations` with `customerId` now returns `{ connections, buildings, nextCursor, truncated, accessFiltered }`: credential status for all six integrations (FAMAC, Dalux, Plania, Interaxo, SharePoint, Google Drive) and the buildings you can read that are linked to each, with `import` and `export` document-sync links (`linked`, `not_linked`, `unknown`, `unsupported`); filter with `provider`, page with `limit` and `cursor`. With `buildingId` it returns `{ integrations }`, one row per integration with its last sync and failures, each status `available`, `unsupported`, `unavailable` or `not_linked`. `get_sharepoint_sync_status` now returns `{ import, export, sync, importFailures, accessFiltered }` (import failures are recorded best effort: `bestEffort: true`) and `list_sharepoint_subscriptions` returns `{ import, subscriptions, accessFiltered }` with per-subscription site/library/folder resolution; the old `siteId`, `driveId`, `rootFolderIds` and `errorMessage` fields are gone. A building you cannot read returns `not_found`. Refresh cached tool schemas.
list_integrationsget_sharepoint_sync_statuslist_sharepoint_subscriptions - MCPMCP Server2026-09-30
`ask_findable` now refuses a `threadId` for a conversation you did not start (or one from another customer) with a `forbidden` error, instead of continuing it. Continue only threads returned to you by an earlier `ask_findable` call; omit `threadId` to start a new one.
ask_findable - APIDocuments2026-09-29
Getting a document now returns previewUrl: a signed link to the generated full PDF when one is available, or null otherwise. The existing url still points to the original file. Documents that are already PDFs have no separate generated PDF preview.
- APIAsk for SharePoint2026-09-29
Resolving a building from SharePoint site and drive context now skips live subscription health checks. The endpoint still returns the same resolution result, but avoids waiting on Microsoft Graph health fan-out for a lookup that only needs stored subscription data.
- MCPMCP Server2026-09-28
`search_documents` now runs the same search as the Findable app assistant: `documentType: "drawing"` also matches documents filed in the drawing categories, every hit is checked against your own read access, and the filename-only fallback for queries the index does not match is gone (use `ask_findable` for that). `totalHits` is `null` when the index count could include documents you cannot open. A page may return fewer than `limit` hits while `hasMore` is still true; keep following `nextOffset`. `windowReached: true` means the first 10,000 matches were exhausted; narrow the query or filters. When both `buildingId` and `portfolioId` are given, only `buildingId` is searched. A missing or inaccessible building or portfolio returns `not_found`, and a portfolio with more than 1,000 buildings returns `invalid_input`.
search_documents - MCPMCP Server2026-09-28
`list_folder_children` now shows only the sub-folders you can open or that lead to a folder shared with you, and only documents you can read yourself. A folder you cannot open now returns `not_found`, like a missing one, instead of `forbidden`. A folder you can only pass through with more than 1,000 sub-folders to check returns `invalid_input`; open a sub-folder by id or search instead. A documents page may hold fewer than `documents_limit` entries while `documentsHasMore` is true; keep following `documentsNextCursor`.
list_folder_children - MCPMCP Server2026-09-27
Users whose access is building- or project-scoped (for example Building Collaborators, with no read on the organisation itself) now get their projects and portfolios from `list_projects` and `list_portfolios`, unscoped or with a `customerId` or `customerName` for any customer they hold a grant inside. Every row is still filtered by the user's own read access.
list_projectslist_portfolios - MCPMCP Server2026-09-27
A `customerName` that matches no customer you can read now returns the same error whether or not such a customer exists: `No customer named "<name>" that you can read.` (it used to say "No access to customer" for a customer that exists but is not yours).
list_buildingslist_collections - MCPMCP Server2026-09-27
Users whose access is building-scoped (for example Building Collaborators, with no read on the organisation itself) now get their buildings and collections from `list_buildings` and `list_collections`, and `find_resources` finds their buildings, portfolios, projects and collections without a `customerId`. Both list tools also accept a `customerId` or `customerName` for any customer the user holds a grant inside, instead of returning "No access to customer". Every row is still filtered by the user's own read access.
list_buildingslist_collectionsfind_resources - MCPMCP Server2026-09-24
New: `list_project_documents(projectId, limit, cursor)` lists the documents you can read in a project's folders (the project folder and its subfolders) as `{ documents: [{ id, filename, buildingId, folderId, createdAt, path }], nextCursor, truncated }`. A project you cannot read returns `not_found`, like a missing one. Refresh cached tool schemas.
list_project_documents - MCPMCP Server2026-09-24
`list_projects`, `list_portfolios` and `get_portfolio` are now cursor-paginated: while `truncated` is true, call again with `cursor` = the previous `nextCursor` and the same filters. `list_projects` and `list_portfolios` accept `limit` up to 100 (was 500) and no longer return `total`; a `customerName` that cannot be resolved in one call returns `scope_required` (pass `customerId`). `list_projects` with `buildingId` lists the projects you can read in that building even without building access, and an unknown building returns an empty list instead of `forbidden`. `get_portfolio` returns up to 50 buildings per call, and its `building_count` is null when the count is unknown (a later page, or a roster too large for one call). `get_project` and `get_portfolio` return `not_found` both for missing records and for records you cannot read (no more `forbidden`). Names and addresses longer than 256 characters are shortened with a trailing ellipsis. Refresh cached tool schemas.
list_projectslist_portfoliosget_portfolioget_project - MCPMCP Server2026-09-24
`generate_red_flag` is removed: MCP can no longer start a red flag report generation directly. Where enabled, `prepare_red_flag_generation` proposes one for a building you administrate and returns an `approvalUrl`; the generation starts only after you review and approve it in Findable. It returns `already_in_progress` while a run is underway and `unsupported_country` for countries without a red flag report. `get_red_flag` no longer reports a run that has not progressed for 30 minutes as `in_progress`, because a new generation would take it over. Refresh cached tool schemas.
prepare_red_flag_generationgenerate_red_flagget_red_flag - MCPMCP Server2026-09-23
Red-flag reads now count only documents you can open. Attached documents, `documentCount`, per-item document counts and the in-review status of items without an explicit status ignore documents in folders you cannot read. Item `status` (and the `status` filter) is now the effective status: the stored status, else `in_review` when you can read one of its documents, else `not_delivered`. It is never null, counts use the same statuses as `percentComplete`, and the always-zero `unset` count is gone. A building you cannot read and a missing building now return the same `forbidden` result, and the tools return `forbidden` when an organisation admin has disabled the red flag report module. Refresh cached tool schemas.
get_red_flaglist_red_flag_itemsget_red_flag_item - MCPMCP Server2026-09-23
`prepare_work_item_action` can propose changes to one building checklist: answer a question item (`answer_checklist_item`), set a document date (`set_checklist_item_date`), assign or unassign an item, send the checklist for approval, approve, reject or withdraw. Each still needs human review in Findable. `query_work_items` checklist results now include `itemType`, `selectedAnswerId`, the assigned user, the approver, and one `answer_option` row per answer option. Refresh cached tool schemas.
prepare_work_item_actionquery_work_items - APIAsk2026-09-21
Ask requests now carry a signed, read-only identity for the API key end to end, so the answer engine refuses any request that arrives without one. Answers stay confined to the documents the key can read. Request and response shapes are unchanged; no integrator action is needed.
- MCPMCP Server2026-09-18
`ask_findable` accepts an optional `mode`: `fast`, `balanced` or `deep`. `fast` is roughly 15x cheaper and several times faster than the default, with shallower synthesis across many documents - prefer it for lookups and single-document questions. `balanced` is what you get when `mode` is omitted; `deep` is the most thorough and most expensive. `reasoningEffort` is deprecated in favour of `mode`: `high` behaves like `deep`, and `low` and `medium` both behave like `balanced`. Refresh cached tool schemas.
ask_findable - APIReports2026-09-18
Generating a deficiency report now rejects an invalid body with 400, as the reference always documented. The body was not actually validated: a country other than NO or GB, a missing country, or an unknown version was accepted and started a report, and an unknown country was handled as Norway. Adding a document to a report without a body now also returns 400 rather than 500. Valid requests are unaffected.
- APIAsk2026-09-18
Ask accepts an optional mode: fast, balanced or deep. fast is roughly 15x cheaper and several times faster than the default, with shallower synthesis across many documents. balanced is what you get when mode is omitted; deep is the most thorough and most expensive. reasoning_effort is deprecated in favour of mode: high behaves like deep, and low and medium both behave like balanced, so reasoning_effort=low never made a request cheaper. Omit mode and nothing changes.
- MCPMCP Server2026-09-17
Red-flag tools now treat legacy buildings with no stored country as Norwegian (`NO`) for automation eligibility and generation instead of reporting `unsupported_country`; buildings with an explicit unsupported country still remain unsupported. Refresh cached tool schemas.
get_red_flaggenerate_red_flag - MCPMCP Server2026-09-17
`search_documents` zero-result responses now include machine-readable `zeroReason: "keyword_terms_may_need_cooccurrence"` and `guidance` fields in structured output, so clients that only read JSON still know to try ask_findable before treating a multi-term keyword miss as proof no relevant documents exist. Refresh cached tool schemas.
search_documents - APIBuilding Owners2026-09-17
Building owners created through the Partner API now explicitly use Norway (NO) as their default country, matching the previous implicit behaviour.
- MCPMCP Server2026-09-13
Read tasks, routines, checklists and available assignees with query_work_items. Where enabled, prepare_work_item_action proposes CRUD changes and returns a Findable review link; the user must approve and execute there. ask_findable remains read-only. Refresh cached tool schemas.
query_work_itemsprepare_work_item_actionask_findable - MCPMCP Server2026-09-11
Task reads now support assignee and date-range filters, expanded routine occurrences, and cursor pagination (25 items by default, maximum 100). Both tools return items/nextCursor/truncated instead of the previous task payload; follow cursors with unchanged filters. Task detail includes comments, filenames, tags and activity actions; raw activity field diffs and storage keys are omitted. Task feature access plus building read or operations access is required. Refresh cached tool schemas.
list_tasksget_task - MCPMCP Server2026-09-09
`search_documents` now describes itself as keyword-backed document discovery instead of hybrid semantic search, and empty result pages explicitly tell agents to use `ask_findable` for semantic topical recall before concluding that no relevant documents exist.
search_documents - MCPMCP Server2026-09-03
No change to inputs, response shape, or behaviour. The tool now sends Ask a signed, short-lived delegation assertion for the signed-in user so Ask can offer read-only agent tooling on the MCP lane once that tooling ships; agents need take no action.
ask_findable - MCPMCP Server2026-09-01
Internal refactor only — no change to inputs, response shape, or behaviour. The Lucene-style filter encoding for `category` / `floor` / `fileType` / `asBuilt` moved out of this tool into @findable/shared so AI-assisted document discovery in Extract shares one implementation of what a category filter means. `search-documents.query.ts` now re-exports it. Logged because the changelog rule is machine-enforced on any tool-file change; agents need take no action.
search_documents - MCPMCP Server2026-09-01
Search results for documents in a building root folder now report the folder as `Root folder` instead of leaking the internal root marker.
search_documents - MCPMCP Server2026-08-24
Documents passed in `attachedDocumentIds` are now permission-checked individually. Previously only the building was checked, so an attached document you could not otherwise open — one in a private folder, or in another building — could still be used to answer. Attaching a document you lack read access to now returns a forbidden error naming the offending ids. No change to inputs or response shape; callers attaching documents they can read see no difference.
ask_findable - APISearch2026-08-20
sort_by=filename now orders on the stored filename, so the order matches what you see. It previously ordered on a normalised copy with common words removed, which could differ noticeably - a code like "SER" was dropped when it happened to be a word in the document language. Sorting is case- and accent-sensitive: uppercase precedes lowercase, and Norwegian æ/ø/å sort after z.
- APIAuthentication2026-08-14
API keys can now be scoped to individual buildings rather than whole building owners. A building-scoped key sees only its own buildings on owner-level endpoints: building_owners lists just the owners it can reach, /buildings returns just its buildings, and /status and /search cover just those buildings. Owner-level changes still require access to the whole building owner. Nothing changes for existing keys.
- APISearch2026-08-13
Search max_results now serves the full requested page, up to 1000. It was previously truncated to 100 regardless of what you asked for. A large page costs barely more than a small one, so prefer one big request over many sequential pages - this supersedes the 2026-06-29 note.
- APIAsk2026-07-20
Agentic retrieval is now the only Ask path. Omit use_agentic_rag; an explicit false returns 400.
- APIAsk2026-07-16
Ask requests now default to agentic retrieval when use_agentic_rag is omitted.
- APISearch2026-06-29
Search max_results is capped at 100; paginate with start_index for larger result sets.
- APIAsk for SharePoint2026-05-05
Added building, drive-item, folder, and citation resolution endpoints for SharePoint Ask integrations.
- APICompatibility2026-04-10
Restored backwards-compatible pagination defaults and the established Partner API response shape.
- APIAuthentication2026-03-22
Added scoped session-token exchange for browser SDK and React integrations.