Vital · Arazzo Workflow

Vital Cancel a Lab Order and Send the User a Portal Link

Version 1.0.0

Cancel an order, confirm the cancellation, then mint a communications portal URL deeplinked to it.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub Health DataWearablesLab TestingDigital HealthHealth TechHealthcareHIPAAHealthKitHealth ConnectEHREMRBiomarkersDiagnosticsContinuous Glucose MonitoringSleepActivityHeart RateWebhookPhlebotomyLab OrdersArazzoWorkflows

Provider

vital-io

Workflows

cancel-order-notify-portal
Cancel an order, confirm it, and create a communications portal URL for the user.
Cancels a lab order, verifies the cancellation by reading the order, then mints a communications portal URL deeplinked to the order for the user.
3 steps inputs: apiKey, orderId, userId outputs: finalStatus, orderId, portalUrl
1
cancelOrder
Cancel the order and capture the returned status message.
2
confirmCancelled
Read the order back and confirm its latest event reports a cancelled status.
3
createPortalUrl
Generate a long-lived communications portal URL deeplinked to the cancelled order so it can be sent to the user over email or SMS.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Vital Cancel a Lab Order and Send the User a Portal Link
  summary: Cancel an order, confirm the cancellation, then mint a communications portal URL deeplinked to it.
  description: >-
    A remediation flow for when an order must be pulled back. The workflow
    cancels the order, reads it back to confirm the latest event is cancelled,
    and then generates a long-lived communications portal URL deeplinked to the
    cancelled order so it can be emailed or texted to the end user. Every step
    spells out its request inline, including the x-vital-api-key header, so the
    flow can be read and executed without opening the underlying OpenAPI
    description.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-2860.10
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-2860.10
      capability_name: Laboratory Services Management
      spec: vital-io-order-api-openapi.yml
      confidence: 0.7
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: orderApi
  url: ../openapi/vital-io-order-api-openapi.yml
  type: openapi
- name: userApi
  url: ../openapi/vital-io-user-api-openapi.yml
  type: openapi
workflows:
- workflowId: cancel-order-notify-portal
  summary: Cancel an order, confirm it, and create a communications portal URL for the user.
  description: >-
    Cancels a lab order, verifies the cancellation by reading the order, then
    mints a communications portal URL deeplinked to the order for the user.
  inputs:
    type: object
    required:
    - apiKey
    - orderId
    - userId
    properties:
      apiKey:
        type: string
        description: Your Vital API key, sent in the x-vital-api-key header.
      orderId:
        type: string
        description: The Vital Order ID to cancel.
      userId:
        type: string
        description: The Vital user_id the order belongs to.
  steps:
  - stepId: cancelOrder
    description: Cancel the order and capture the returned status message.
    operationId: cancel_order_v3_order__order_id__cancel_post
    parameters:
    - name: x-vital-api-key
      in: header
      value: $inputs.apiKey
    - name: order_id
      in: path
      value: $inputs.orderId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      orderId: $response.body#/order/id
      status: $response.body#/status
      message: $response.body#/message
  - stepId: confirmCancelled
    description: >-
      Read the order back and confirm its latest event reports a cancelled
      status.
    operationId: get_order_v3_order__order_id__get
    parameters:
    - name: x-vital-api-key
      in: header
      value: $inputs.apiKey
    - name: order_id
      in: path
      value: $inputs.orderId
    successCriteria:
    - condition: $statusCode == 200
    - context: $response.body
      condition: $.last_event.status == 'cancelled'
      type: jsonpath
    outputs:
      lastEventStatus: $response.body#/last_event/status
  - stepId: createPortalUrl
    description: >-
      Generate a long-lived communications portal URL deeplinked to the cancelled
      order so it can be sent to the user over email or SMS.
    operationId: create_user_portal_url_v2_user__user_id__create_portal_url_post
    parameters:
    - name: x-vital-api-key
      in: header
      value: $inputs.apiKey
    - name: user_id
      in: path
      value: $inputs.userId
    requestBody:
      contentType: application/json
      payload:
        context: communications
        order_id: $inputs.orderId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      url: $response.body#/url
      expiresIn: $response.body#/expires_in
  outputs:
    orderId: $steps.cancelOrder.outputs.orderId
    finalStatus: $steps.confirmCancelled.outputs.lastEventStatus
    portalUrl: $steps.createPortalUrl.outputs.url

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/vital-io-cancel-order-notify-portal-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.