Mindbody · Arazzo Workflow

Mindbody Browse Services and Checkout

Version 1.0.0

List sellable services, check out a cart for a client, and confirm the sale.

1 workflow 1 source API 1 provider
View Spec View on GitHub FitnessWellnessBeautySchedulingBookingPoint-of-SaleStudiosSalonsSpasWebhookArazzoWorkflows

Provider

mindbody

Workflows

browse-services-checkout
Discover sellable services, check out a cart, and confirm the sale.
Lists the services available for sale, checks out a shopping cart for the client, and then confirms the sale was recorded in the sales ledger.
3 steps inputs: apiKey, authorization, clientId, items, payments, siteId, startSaleDateTime outputs: cartId, sales, services
1
listServices
List the services available for sale at the site so a sellable item can be selected for the cart.
2
checkout
Check out the shopping cart for the client with the supplied items and payments, committing the transaction.
3
confirmSale
Read the sales list for the date range to confirm the checkout was recorded as a committed sale.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Mindbody Browse Services and Checkout
  summary: List sellable services, check out a cart for a client, and confirm the sale.
  description: >-
    A retail flow for selling pricing options and services. The workflow lists
    the services available for sale at the site, checks out a shopping cart of
    items and payments for the client, and confirms the resulting sale in the
    sales ledger. Every step inlines the Mindbody API-Key, SiteId, and staff
    authorization headers along with its request body so the flow can be read
    and executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: saleApi
  url: ../openapi/mindbody-sale-api-openapi.yml
  type: openapi
workflows:
- workflowId: browse-services-checkout
  summary: Discover sellable services, check out a cart, and confirm the sale.
  description: >-
    Lists the services available for sale, checks out a shopping cart for the
    client, and then confirms the sale was recorded in the sales ledger.
  inputs:
    type: object
    required:
    - apiKey
    - siteId
    - authorization
    - clientId
    - items
    - payments
    properties:
      apiKey:
        type: string
        description: The Mindbody-issued API key sent in the API-Key header.
      siteId:
        type: string
        description: The ID of the site processing the sale.
      authorization:
        type: string
        description: A staff user authorization (OAuth bearer) token.
      clientId:
        type: string
        description: The RSSID of the client making the purchase.
      items:
        type: array
        description: A list of the items in the cart (CheckoutItemWrapper objects).
      payments:
        type: array
        description: A list of payment information objects to apply to the cart.
      startSaleDateTime:
        type: string
        description: Start of the date range used to confirm the sale.
  steps:
  - stepId: listServices
    description: >-
      List the services available for sale at the site so a sellable item can
      be selected for the cart.
    operationId: getServices
    parameters:
    - name: version
      in: path
      value: '6'
    - name: API-Key
      in: header
      value: $inputs.apiKey
    - name: siteId
      in: header
      value: $inputs.siteId
    - name: authorization
      in: header
      value: $inputs.authorization
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      services: $response.body#/Services
  - stepId: checkout
    description: >-
      Check out the shopping cart for the client with the supplied items and
      payments, committing the transaction.
    operationId: checkoutShoppingCart
    parameters:
    - name: version
      in: path
      value: '6'
    - name: API-Key
      in: header
      value: $inputs.apiKey
    - name: siteId
      in: header
      value: $inputs.siteId
    - name: authorization
      in: header
      value: $inputs.authorization
    requestBody:
      contentType: application/json
      payload:
        ClientId: $inputs.clientId
        Items: $inputs.items
        Payments: $inputs.payments
        Test: false
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      cartId: $response.body#/ShoppingCart/Id
  - stepId: confirmSale
    description: >-
      Read the sales list for the date range to confirm the checkout was
      recorded as a committed sale.
    operationId: getSales
    parameters:
    - name: version
      in: path
      value: '6'
    - name: API-Key
      in: header
      value: $inputs.apiKey
    - name: siteId
      in: header
      value: $inputs.siteId
    - name: authorization
      in: header
      value: $inputs.authorization
    - name: request.startSaleDateTime
      in: query
      value: $inputs.startSaleDateTime
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      sales: $response.body#/Sales
  outputs:
    services: $steps.listServices.outputs.services
    cartId: $steps.checkout.outputs.cartId
    sales: $steps.confirmSale.outputs.sales

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/mindbody-browse-services-checkout-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.