Azure Healthcareapis Healthcare Apis

Connector for the azure-healthcareapis-healthcare-apis API, generated deterministically from its OpenAPI spec (endpoints, auth, and methods match the spec exactly — nothing is invented).

• Base URL: https://management.azure.com
• Auth: OAuth 2.0 (user-delegated) — attach an InTouch oauth credential. Mint one with itcli.py /oauth <provider> (device-code) or /google-auth (Google); the server auto-refreshes the access token before each run, so the connector never handles or stores tokens.

Operations

• operations_list — GET /providers/Microsoft.HealthcareApis/operations — Lists all of the available Healthcare service REST API operations.
• operationresults_get — GET /subscriptions/{subscriptionId}/providers/Microsoft.HealthcareApis/locations/{locationName}/operationresults/{operationResultId} — Get the operation result for a long running operation.
• services_list — GET /subscriptions/{subscriptionId}/providers/Microsoft.HealthcareApis/services — Get all the service instances in a subscription.
• services_listbyresourcegroup — GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HealthcareApis/services — Get all the service instances in a resource group.
• services_get — GET /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HealthcareApis/services/{resourceName} — Get the metadata of a service instance.
• services_checknameavailability — POST /subscriptions/{subscriptionId}/providers/Microsoft.HealthcareApis/checkNameAvailability — Check if a service instance name is available.

Inputs

• a linked oauth credential (no key inputs) — the server injects a fresh Authorization: Bearer from it
• operation — one of the operations above
• path parameters when an operation's path contains {...}
• query — optional JSON object of query params
• body — JSON object for create/update ops

Example

operation: operations_list
# (attach an 'oauth' credential to the task — no inline secrets)