How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Amigo M42 API

The M42 API from Amigo — 19 operation(s) for m42.

Amigo M42 API is one of 72 APIs that Amigo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include M42. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 19 operations across 19 paths, and defines 41 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 5 base URLs: https://api.amigo.ai, https://internal-api.amigo.ai, https://api-eu-central-1.amigo.ai, https://api-ap-southeast-2.amigo.ai, https://api-ca-central-1.amigo.ai.

19 operations 19 paths 41 schemas 19 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.amigo.ai
Authentication
HTTP Bearer, API Key, HTTP Basic
Resource Areas
1

Authentication & Security 3

Amigo M42 API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (Bearer-Authorization). An API key is passed in the header as X-ORG-ID (Bearer-Authorization-Organization). It accepts HTTP basic authentication (Basic). By default, every request must be authenticated.

  • Bearer-Authorization — Amigo issued JWT token that identifies an user. It's issued either after logging in through the frontend, or manually through the [SignInWithAPIKey](sign-in-wi…
  • Bearer-Authorization-Organization — An optional organization identifier that indicates from which organization the token is issued. This is used in rare cases where the user to authenticate is ma…
  • Basic — The username should be set to {orgid}{userid}, and the password should be the Amigo issued JWT token that identifies the user.

Paths & Operations 19

Across 19 paths, the API surfaces 19 operations — 19 GET. Each is listed below with its method, path, parameters, and response codes.

M42 19
GET
/v1/{workspace_id}/m42/patient-topology
List Patient Topology
list_patient_topology_v1__workspace_id__m42_patient_topology_get 5 params → 200422
GET
/v1/{workspace_id}/m42/district-metrics
List District Metrics
list_district_metrics_v1__workspace_id__m42_district_metrics_get 3 params → 200422
GET
/v1/{workspace_id}/m42/anomaly-alerts
List Anomaly Alerts
list_anomaly_alerts_v1__workspace_id__m42_anomaly_alerts_get 4 params → 200422
GET
/v1/{workspace_id}/m42/forecast-fan
List Forecast Fan
list_forecast_fan_v1__workspace_id__m42_forecast_fan_get 5 params → 200422
GET
/v1/{workspace_id}/m42/positive-signals
List Positive Signals
list_positive_signals_v1__workspace_id__m42_positive_signals_get 3 params → 200422
GET
/v1/{workspace_id}/m42/anomalies/ranked
List Anomalies Ranked
list_anomalies_ranked_v1__workspace_id__m42_anomalies_ranked_get 4 params → 200422
GET
/v1/{workspace_id}/m42/clusters/summary
List Cluster Summary
list_cluster_summary_v1__workspace_id__m42_clusters_summary_get 3 params → 200422
GET
/v1/{workspace_id}/m42/clusters/forecast
List Cluster Forecast
list_cluster_forecast_v1__workspace_id__m42_clusters_forecast_get 4 params → 200422
GET
/v1/{workspace_id}/m42/forecast-fan/draws
List Forecast Draws
list_forecast_draws_v1__workspace_id__m42_forecast_fan_draws_get 4 params → 200422
GET
/v1/{workspace_id}/m42/model-registry
List Model Registry
list_model_registry_v1__workspace_id__m42_model_registry_get 3 params → 200422
GET
/v1/{workspace_id}/m42/stratified-fits
List Stratified Fits
list_stratified_fits_v1__workspace_id__m42_stratified_fits_get 4 params → 200422
GET
/v1/{workspace_id}/m42/patients/{patient_id}/labs
List Patient Labs
list_patient_labs_v1__workspace_id__m42_patients__patient_id__labs_get 4 params → 200422
GET
/v1/{workspace_id}/m42/patients/{patient_id}/note
Get Patient Note
get_patient_note_v1__workspace_id__m42_patients__patient_id__note_get 2 params → 200422
GET
/v1/{workspace_id}/m42/notes/rollup
Get Notes Rollup
get_notes_rollup_v1__workspace_id__m42_notes_rollup_get 3 params → 200422
GET
/v1/{workspace_id}/m42/catalog
List Catalog
list_catalog_v1__workspace_id__m42_catalog_get 1 param → 200
GET
/v1/{workspace_id}/m42/catalog/{table}/columns
Describe Table
describe_table_v1__workspace_id__m42_catalog__table__columns_get 2 params → 200422
GET
/v1/{workspace_id}/m42/catalog/{table}/sample
Sample Table
sample_table_v1__workspace_id__m42_catalog__table__sample_get 3 params → 200422
GET
/v1/{workspace_id}/m42/features
List Features
list_features_v1__workspace_id__m42_features_get 1 param → 200
GET
/v1/{workspace_id}/m42/features/distribution
Feature Distribution
feature_distribution_v1__workspace_id__m42_features_distribution_get 3 params → 200422

Schemas 41

The contract defines 41 schemas that model the data the API accepts and returns. The most detailed are PatientTopologyRow (24 properties), RankedAnomalyRow (15 properties), DistrictMetricsRow (13 properties), AnomalyAlertRow (12 properties). Each schema is shown below with its type and property counts.

PatientNoteExtractions
object
9 properties 3 required
ModelRegistryResponse
object
3 properties 3 required
ModelRegistryRow
object
11 properties 2 required
StratifiedFitsResponse
object
3 properties 3 required
ColumnsResponse
object
3 properties 3 required
PatientNoteResponse
object
6 properties 4 required
PatientLabRow
object
6 properties 2 required
ClusterForecastResponse
object
3 properties 3 required
HistogramBin
object
4 properties 4 required
NoteRollupCategoryEntry
object
5 properties 5 required
ForecastFanResponse
object
3 properties 3 required
PositiveSignalResponse
object
3 properties 3 required
FeatureDistributionResponse
object
6 properties 6 required
DistrictMetricsResponse
object
3 properties 3 required
ForecastDrawsResponse
object
3 properties 3 required
AnomalyAlertRow
object
12 properties 3 required
ForecastFanPointRow
object
10 properties 4 required
CatalogEntry
object
5 properties 5 required
NoteRollupResponse
object
8 properties 8 required
HTTPValidationError
object
1 property
DistrictMetricsRow
object
13 properties 2 required
ClusterForecastPointRow
object
10 properties 3 required
ValidationError
object
5 properties 3 required
ClusterSummaryResponse
object
3 properties 3 required
ColumnInfo
object
3 properties 2 required
RankedAnomalyRow
object
15 properties 1 required
StratifiedFitRow
object
11 properties 4 required
AnomalyAlertResponse
object
3 properties 3 required
ClusterSummaryRow
object
9 properties 2 required
SampleResponse
object
3 properties 3 required
ForecastDrawPoint
object
3 properties 3 required
NoteRollupSdoh
object
3 properties 3 required
PatientLabsResponse
object
3 properties 3 required
PatientTopologyResponse
object
3 properties 3 required
DecompositionRow
object
7 properties 2 required
PositiveSignalRow
object
9 properties 2 required
FeaturesResponse
object
3 properties 3 required
PatientTopologyRow
object
24 properties 5 required
M42CatalogResponse
object
3 properties 3 required
FeatureDef
object
2 properties 2 required
RankedAnomalyResponse
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

amigo-m42-api-openapi.yml Raw ↑

Other APIs Amigo publishes across the network.

Amigo Account API
Amigo Admin API
Amigo Agent Definitions API
Amigo Agent Runs API
Amigo Agents API
Amigo Analytics API
Amigo API Keys API
Amigo Audit API
Amigo Auth API
Amigo Billing API
Amigo Calls API
Amigo Command Center API
Where this information came from

This is an independent, third-party profile of Amigo M42 API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.