> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/api-reference/change-logs/api-history/amigo-api-history-02.md).

# Concurrence API: Archive 2

Retained API history, archive 2, with original entry headings and links back to current integration guidance.

This archive includes warehouse intake, world model serving, and timeline reads. Entries retain their original release context; they do not establish current availability. Use [Current Upgrade Guidance](https://docs.concurrence.com/api-reference/change-logs/upgrade-guide.md) before applying an older example.

[Previous archive](https://docs.concurrence.com/api-reference/change-logs/api-history/amigo-api-history-01.md) · [Archive index](https://docs.concurrence.com/api-reference/change-logs/amigo-api.md#archive-index) · [Next archive](https://docs.concurrence.com/api-reference/change-logs/api-history/amigo-api-history-03.md)

<details>

<summary>Platform: Data Warehouse Connector Source Type (July 2026)</summary>

#### Data Warehouse Connector Source Type <a href="#data-warehouse-connector-source-type" id="data-warehouse-connector-source-type"></a>

The connector framework now supports data warehouse sources as a first-class source type, enabling direct ingestion from analytics marts into the world model.

**What changed:**

* **New warehouse source type.** Data sources can now be configured with a warehouse source type that reads from analytics mart tables over HTTP-based SQL APIs. The connector authenticates using key-pair JWT with an RSA private key stored in the platform's secret manager - no password or interactive credential flow is required.
* **Full-snapshot polling with diff-based emission.** Each configured query returns the complete current contents of a mart table on every poll cycle. The platform diffs each snapshot against the prior poll and emits only created and updated records, keeping downstream processing efficient without requiring incremental query logic in the mart.
* **Per-query cadence and safety ceilings.** Each query within a warehouse data source has its own poll cadence and a configurable row ceiling. If a result exceeds the ceiling the poll fails rather than silently truncating, because a partial snapshot would cause the diff to misidentify present rows as removed.
* **Removal detection without false cancellations.** When a row leaves the snapshot between polls, the platform logs the removal but does not emit a cancellation event. Rows leave analytics marts for many reasons - the underlying record was completed, aged out of a rolling window, or was legitimately cancelled - and the platform cannot distinguish these cases. The last-known state of the record is preserved.
* **Confidence-aware entity emission.** Resources derived from a warehouse mart are emitted at a lower confidence tier than records read directly from an EHR API. This prevents a sparse warehouse projection from overwriting richer demographic data that arrived through a primary clinical connector.
* **Connection configuration is fully declarative.** Account, user, role, warehouse, database, schema, and per-query SQL are all specified in the data source connection configuration. Onboarding a new warehouse tenant requires a configuration entry, not a code change.

**What you need to do:**

* **No action required for existing data sources.** This is a new source type. Existing connectors and data sources are unaffected.
* **To connect a warehouse:** Work with your platform operator to register a warehouse data source with the appropriate connection details and RSA key-pair credential. Share the public key with your warehouse administrator for service-user registration.

</details>

<details>

<summary>Platform: Keyless Credential for Google Drive Intake Sources (July 2026)</summary>

#### Keyless Credential for Google Drive Intake Sources <a href="#keyless-credential-for-google-drive-intake-sources" id="keyless-credential-for-google-drive-intake-sources"></a>

Google Drive intake sources now authenticate using a unified platform-managed service account with no key material to provision, store, or rotate.

**What changed:**

* **No per-source credential provisioning.** Newly registered Drive intake sources authenticate as the platform's unified intake service account. There is no secret key to upload, no parameter path to manage, and no out-of-band provisioning step. Share the target folder with the service account email provided by your platform operator, or configure domain-wide delegation if your organization's policy requires it.
* **`credential_ssm_param_path` is now optional on intake source responses.** Sources registered before this change retain their existing credential path. Sources registered after this change return `null` for this field, indicating keyless authentication.
* **Existing sources continue to work.** Sources that were registered with a per-workspace credential path continue to use that credential. Migration to the keyless model is workspace-scoped and managed by the platform operator.
* **Registration no longer requires a follow-up provisioning step.** Previously, registering a Drive intake source returned a credential path that an operator had to populate before the first sync. New sources are ready to sync as soon as the Drive folder is shared with the platform service account.

**What you need to do:**

* **For new sources:** Share the Drive folder with the platform intake service account email (provided by your platform operator) and register the source. No additional credential setup is needed.
* **If you parse the `credential_ssm_param_path` field:** Update your integration to handle `null` values. A `null` value means the source uses keyless authentication and no secret exists to manage.
* **Existing sources require no changes.** Previously provisioned credentials continue to work.

</details>

<details>

<summary>Platform: Voice Turn Authentication Fix for Multi-Workspace Deployments (July 2026)</summary>

#### Voice Turn Authentication Fix for Multi-Workspace Deployments <a href="#voice-turn-authentication-fix-for-multi-workspace-deployments" id="voice-turn-authentication-fix-for-multi-workspace-deployments"></a>

Voice turn requests now authenticate correctly across all workspaces. Previously, voice turns returned 403 errors for every workspace other than the platform's own home workspace.

**What changed:**

* **Voice turns work for all workspaces.** The voice turn endpoint now correctly validates the caller's authorization against the target workspace. Previously, an internal credential mismatch caused every customer workspace to receive a 403 Forbidden response, effectively breaking voice turns for all external workspaces.
* **Two-layer authorization enforced.** Voice turn requests now carry both the internal service credential and the original caller's authorization. The service credential proves the internal hop, while the caller credential binds the turn to the correct workspace. This matches the authorization contract already used by text turns.

**What you need to do:**

* **No action required.** This is a server-side fix. Voice turn requests that were failing with 403 will now succeed without any client changes. If you implemented workarounds for voice turn failures, those workarounds can be removed.

</details>

<details>

<summary>Platform: AI Metric History Now Accumulates Across Runs (July 2026)</summary>

#### AI Metric History Now Accumulates Across Runs <a href="#ai-metric-history-now-accumulates-across-runs" id="ai-metric-history-now-accumulates-across-runs"></a>

AI-scored metric results now accumulate over time instead of being replaced wholesale on every scheduled run.

**What changed:**

* **Scoped metric writes.** Each scheduled metric computation run now replaces only the workspace-and-metric combinations it actually recomputed, within the time window it evaluated. Previously, every run overwrote the entire results table, so only the most recent run's scores were retained - effectively capping metric history to a single evaluation window.
* **Historical scores preserved.** Judge-based quality metrics and classifier metrics (such as AI-scored call quality and event classification results) now retain results from prior runs. Dashboards and trend views that query these tables can display score progression over days and weeks rather than showing only the latest window.
* **No empty-table resets.** When a run produces no results for a given metric pipeline - for example, because no new eligible interactions arrived - the existing data is left untouched. Previously, an empty run would overwrite the table with zero rows, erasing all prior history.
* **Input validation on metric configuration.** Workspace and metric identifiers used in scheduled metric runs are now validated before evaluation begins. Configurations with malformed identifiers are skipped with a log message rather than causing a run-level failure.

**What you need to do:**

* **No action required.** The change is automatic. If you have dashboards or alerts built on AI metric result tables, you may notice that historical data now persists across runs. Trend analysis and drift detection workflows will see richer history going forward. Data written before this change that was already overwritten cannot be recovered.

</details>

<details>

<summary>Platform: Design Agent Session Collector (July 2026)</summary>

#### Design Agent Session Collector <a href="#design-agent-session-collector" id="design-agent-session-collector"></a>

The platform now captures design agent session transcripts for internal observability. A new write-only endpoint accepts full session transcripts from the design agent tooling and durably persists them for downstream analysis.

**What changed:**

* **Session transcript collection.** A new endpoint accepts complete design agent session transcripts as newline-delimited JSON. Each upload is durably stored before the endpoint returns success, ensuring no session data is silently lost. Uploads that exceed 25 MB are rejected with a 413 status.
* **Write-only authentication.** The collector uses a dedicated shared token separate from platform API keys. This token grants write access to the session collector only and does not provide read access to any platform resources.
* **Region-scoped availability.** The collector endpoint is available in the us-east-1 region only. Requests to other regions return 404.
* **Rate limiting.** The endpoint uses a dedicated rate-limiting bucket with generous headroom for normal usage patterns, independent of the standard write rate limit.
* **Downstream parsing.** Stored transcripts are parsed asynchronously into structured event rows by a scheduled job. Parsing is best-effort and re-runnable - the raw transcript is the source of truth and can be reprocessed if the parsing logic is updated.

**What you need to do:**

* **No action required.** This is an internal observability feature. Design agent tooling submits transcripts automatically when configured. The collector does not affect existing API behavior or workspace resources.

</details>

<details>

<summary>Platform: Per-Source AI Call Attribution for Cost Caps (July 2026)</summary>

#### Per-Source AI Call Attribution for Cost Caps <a href="#per-source-ai-call-attribution-for-cost-caps" id="per-source-ai-call-attribution-for-cost-caps"></a>

The daily AI-call cost cap now tracks usage per pipeline source rather than pooling all AI calls into a single counter per workspace.

**What changed:**

* **Source-level attribution.** Each analytics pipeline - standard metric scoring and topic classification - now records its AI-model calls under its own source label. Daily caps are evaluated per workspace, per UTC day, and per source, so one pipeline reaching its limit does not block another.
* **Topic modeling calls metered independently.** Topic classification AI spend is attributed and metered as a distinct source. This appears as a separate line in the unified metering projection, giving billing and cost dashboards visibility into classifier spend without conflating it with other metric computations.
* **Backward-compatible migration.** Workspaces with existing usage history are migrated automatically. Historical rows that predate source attribution are labeled as unknown and do not count against any specific pipeline's cap.

**What you need to do:**

* **No action required.** The migration is automatic. Existing daily cap configurations continue to apply per workspace per source. If you monitor cost cap behavior through dashboards or alerts, note that totals are now broken out by source rather than aggregated.

</details>

<details>

<summary>Platform: Topic Modeling Gated by Permission (July 2026)</summary>

#### Topic Modeling Gated by Permission <a href="#topic-modeling-gated-by-permission" id="topic-modeling-gated-by-permission"></a>

Topic modeling settings are now controlled by a dedicated permission instead of requiring an Amigo administrator.

**What changed:**

* **New `TopicModeling:Manage` permission.** Reading and updating topic modeling settings now requires the `TopicModeling:Manage` permission on the workspace. This replaces the previous restriction that limited topic modeling changes to Amigo administrators.
* **Admin and owner roles granted by default.** The `TopicModeling:Manage` permission is included in the admin role. Members, operators, and viewers cannot enable or modify topic modeling settings.
* **Amigo-administrator email check removed.** The endpoints no longer verify that the caller's email belongs to the Amigo domain. Any workspace credential with the `TopicModeling:Manage` permission can read or update topic modeling settings.

**What you need to do:**

* **No action required for admin or owner credentials.** These roles already include the new permission.
* **Update integrations that relied on Amigo-administrator access.** If an external workflow previously depended on an Amigo administrator to change topic modeling settings, a workspace admin can now perform the change directly.
* **Grant the permission to custom roles if needed.** If your workspace uses custom roles that need topic modeling access, add `TopicModeling:Manage` to those roles.

</details>

<details>

<summary>Platform: Circuit Breaker on World Events Serving Reads (July 2026)</summary>

#### Circuit Breaker on World Events Serving Reads <a href="#circuit-breaker-on-world-events-serving-reads" id="circuit-breaker-on-world-events-serving-reads"></a>

The world events OLAP serving path now applies a per-pod circuit breaker and a tighter request-budget-aligned timeout to flag-gated serving reads. This prevents a slow or degraded warehouse from pinning request coroutines and cascading latency into unrelated requests.

**What changed:**

* **Tighter timeout for serving reads.** Flag-gated serving reads now use a shorter timeout aligned to the overall request budget. If the warehouse does not respond within that window, the read fails fast rather than holding the connection for the longer diagnostic default.
* **Circuit breaker on repeated failures.** Consecutive warehouse failures or timeouts on the serving path trip a per-pod circuit breaker. While the breaker is open, subsequent serving reads return an immediate 503 instead of attempting the warehouse call, reducing pressure on a degraded backend.
* **Automatic recovery.** After a brief recovery window, the breaker transitions to half-open and allows a probe request through. If the probe succeeds, normal traffic resumes. If it fails, the breaker reopens.
* **Diagnostic and long-running reads unaffected.** Heavier diagnostic queries - such as prompt log scans and trace projections - continue to use their own timeouts and are not routed through the circuit breaker. The raw-ledger read path is also unaffected.

**What you need to do:**

* **No action required.** This is a resilience improvement. If your integration consumes world events through the serving path, be aware that a degraded warehouse may now produce 503 responses more quickly than before. Retry with backoff as you would for any 503.

</details>

<details>

<summary>Platform: Operator Dashboard Timeline Reads Migrated to Optimized Serving Path (July 2026)</summary>

#### Operator Dashboard Timeline Reads Migrated to Optimized Serving Path <a href="#operator-dashboard-timeline-reads-migrated-to-optimized-serving-path" id="operator-dashboard-timeline-reads-migrated-to-optimized-serving-path"></a>

Operator dashboard timeline readers - escalation statistics, escalation event lists, audit event lists, and call transcript lookups - now serve data from the same optimized per-workspace serving path used by the earlier timeline and analytics migrations. The migration is controlled by a per-workspace feature flag and falls back to the previous path when the flag is off.

**What changed:**

* **Dashboard escalation and audit reads use the optimized path.** Daily escalation statistics, escalation event counts (grouped by status, trigger, or operator), escalation event lists, operator audit event lists, and call transcript reads now resolve through the optimized serving layer when the workspace is enrolled. Response shapes are unchanged.
* **Generic data query endpoint no longer exposes the event timeline table.** The generic column-filter-sort data query endpoint previously allowed arbitrary queries against the event timeline mirror. This table has been removed from the generic endpoint. Callers should use the dedicated timeline endpoints (entity timeline, MCP entity timeline) instead, which are already backed by the optimized path.
* **Per-workspace rollout.** The migration is gated by a per-workspace flag. Workspaces that have not been enrolled continue to read from the previous path with no behavior change.

**What you need to do:**

* **No action required for dashboard users.** The operator dashboard reads the same data with the same response shape. Performance may improve for workspaces enrolled in the optimized path.
* **Update integrations that queried the event timeline through the generic data endpoint.** If you used the generic data query endpoint to read event timeline rows with arbitrary column filters, switch to the dedicated entity timeline endpoints. The generic endpoint no longer serves that table.

</details>

<details>

<summary>Platform: Remaining Timeline Readers Migrated to Optimized Serving Path (July 2026)</summary>

#### Remaining Timeline Readers Migrated to Optimized Serving Path <a href="#remaining-timeline-readers-migrated-to-optimized-serving-path" id="remaining-timeline-readers-migrated-to-optimized-serving-path"></a>

Enrichment history, simulation evaluation, research entity timeline, and data source event statistics now support the same optimized per-workspace serving path used by the earlier timeline and analytics migrations.

**What changed:**

* **Per-workspace cutover for remaining timeline readers.** Workspaces enrolled in the migration now read enrichment history, simulation evaluation results, research entity timelines, and data source event counts and daily histories from the optimized materialized view. The cutover is controlled by the same per-workspace feature flag as the earlier timeline and analytics migrations, allowing incremental rollout and instant rollback.
* **Fail-safe default.** Workspaces without the flag enabled, or where flag evaluation encounters an error, continue reading from the existing source. No workspace experiences a change in behavior unless explicitly enrolled.
* **Response shape unchanged.** The optimized path returns the same fields and value shapes as the previous source. Enrichment history entries, simulation evaluation results, entity timeline rows, and data source statistics are identical for API consumers regardless of which path is active.
* **Workspace-scoped access unchanged.** The optimized path enforces the same workspace-scoped access boundaries as the previous source. Cross-workspace reads remain impossible regardless of which path is active.

**What you need to do:**

* **No action required.** The migration is transparent to API consumers. Query results, response shapes, and access controls are unchanged. Workspaces are enrolled by the platform team as the rollout progresses.

</details>

<details>

<summary>Platform: Analytics Summary Reads Migrated to Optimized Serving Path (July 2026)</summary>

#### Analytics Summary Reads Migrated to Optimized Serving Path <a href="#analytics-summary-reads-migrated-to-optimized-serving-path" id="analytics-summary-reads-migrated-to-optimized-serving-path"></a>

Connector health, event velocity, event type summaries, and sense-act loop latency reads now support an optimized per-workspace serving path, controlled by the same per-workspace feature flag used for the timeline migration.

**What changed:**

* **Per-workspace analytics cutover.** Workspaces enrolled in the migration now read connector health, event velocity, event type summaries, and loop latency data from an optimized materialized view. The cutover is controlled by the same per-workspace feature flag as the timeline migration, allowing incremental rollout and instant rollback.
* **Fail-safe default.** Workspaces without the flag enabled, or where flag evaluation encounters an error, continue reading from the existing source. No workspace experiences a change in behavior unless explicitly enrolled.
* **Response shape unchanged.** The optimized path returns the same fields and value shapes as the previous source. Connector health, event velocity, event type summary, and loop latency responses are identical for API consumers regardless of which path is active.
* **Workspace-scoped access unchanged.** The optimized path enforces the same workspace-scoped access boundaries as the previous source. Cross-workspace reads remain impossible regardless of which path is active.

**What you need to do:**

* **No action required.** The migration is transparent to API consumers. Query results, response shapes, and access controls are unchanged. Workspaces are enrolled by the platform team as the rollout progresses.

</details>

<details>

<summary>Platform: Per-Workspace Timeline Read Migration to Materialized View (July 2026)</summary>

#### Per-Workspace Timeline Read Migration to Materialized View <a href="#per-workspace-timeline-read-migration-to-materialized-view" id="per-workspace-timeline-read-migration-to-materialized-view"></a>

The research query service now supports reading timeline data from an optimized materialized view instead of the previous federated mirror, controlled by a per-workspace feature flag.

**What changed:**

* **Per-workspace materialized view cutover.** Workspaces enrolled in the migration read entity event timeline data from a new materialized view that serves the same columns as the previous source. The cutover is controlled by a per-workspace feature flag, allowing incremental rollout and instant rollback.
* **Fail-safe default.** Workspaces without the flag enabled, or where flag evaluation encounters an error, continue reading from the existing source. No workspace experiences a change in behavior unless explicitly enrolled.
* **Workspace-scoped access unchanged.** The materialized view enforces the same workspace-scoped access boundaries as the previous source. Cross-workspace reads remain impossible regardless of which path is active.

**What you need to do:**

* **No action required.** The migration is transparent to API consumers. Query results, column shapes, and access controls are unchanged. Workspaces are enrolled by the platform team as the rollout progresses.

</details>

<details>

<summary>Channel Manager: Automatic Retry for Telephony Provisioning Status Callbacks (July 2026)</summary>

#### Automatic Retry for Telephony Provisioning Status Callbacks <a href="#automatic-retry-for-telephony-provisioning-status-callbacks" id="automatic-retry-for-telephony-provisioning-status-callbacks"></a>

Telephony provisioning status callbacks now retry automatically when the callback arrives before the platform has finished persisting the associated provisioning record.

**What changed:**

* **Automatic redelivery on race conditions.** When a telephony provider sends a provisioning status callback before the platform has committed the matching record, the webhook now returns an error status that triggers the provider to redeliver the callback. Previously, the callback was silently accepted and the status update was lost, requiring manual resolution.
* **Up to five retries.** The provider retries delivery up to five times on any error response, giving the platform time to finish committing the record. Once the record is available, the callback is processed normally.
* **Applies to all provisioning bundles.** The retry behavior covers trust profile, regulatory bundle, messaging profile, caller-ID display, and call authentication provisioning callbacks.

**What you need to do:**

* **No action required.** This is a reliability improvement to telephony provisioning. Provisioning status updates that previously could be lost due to timing are now delivered reliably.

</details>

[Previous archive](https://docs.concurrence.com/api-reference/change-logs/api-history/amigo-api-history-01.md) · [Archive index](https://docs.concurrence.com/api-reference/change-logs/amigo-api.md#archive-index) · [Next archive](https://docs.concurrence.com/api-reference/change-logs/api-history/amigo-api-history-03.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/api-reference/change-logs/api-history/amigo-api-history-02.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
