> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aioncx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Callbacks and processing status

> Connect supported inbound deliveries and follow Mach-1 processing through the published status interfaces.

Mach-1 accepts supported source deliveries and processes conversations asynchronously. Use the published status and result reads to determine when an admitted request is ready.

## Inbound deliveries

[Build Sources](https://build.aioncx.com/build/sources) provides managed Zoom setup and a native Deepgram callback destination.

Deepgram delivers a completed transcript to the one-time Basic Auth callback URL shown during setup. The optional `dg-token` check is configured for that connection. Destination and selected-analysis changes apply to future admissions.

See [sources and transcript producers](https://docs.aioncx.com/mach1/sources.md) for credential rotation, pause behavior, and existing transcript imports.

## Follow a conversation

Retain the admitted interaction ID. Poll `GET /api/ingest/interactions/{interactionId}/status` with the scoped key, then retrieve its transcript and results.

An agent can use `mach1_get_status` and the read tools. Follow returned `next_actions` and retain the input/transcript revision across pages.

## Follow a forecast

Retain the submitted `run_id`. Read `GET /api/forecasts/{runId}` or call `mach1_get_forecast` until it completes or fails. See [forecasting](https://docs.aioncx.com/mach1/forecasting.md).

## Outbound application events

The published contracts use status reads for processing completion. A general customer-managed completion-webhook subscription and signing catalog is not part of those contracts. Use the status flow above for an integration built against this release.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.