Mindbody · Arazzo Workflow

Mindbody Client Arrival Check-In

Version 1.0.0

Find a client by search text and log their arrival at a location.

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

Provider

mindbody

Workflows

client-arrival-checkin
Search for a client and record their arrival at a location.
Searches the client directory by search text and, when a client is found, logs the arrival at the supplied location.
2 steps inputs: apiKey, authorization, locationId, searchText, siteId outputs: arrivalAdded, clientId
1
findClient
Search the client directory by the supplied search text and capture the first matching client id.
2
logArrival
Log the matched client's arrival at the supplied location.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Mindbody Client Arrival Check-In
  summary: Find a client by search text and log their arrival at a location.
  description: >-
    A front-desk check-in flow. The workflow searches for a client by name or
    search text, captures the matching client id, and logs the client's
    arrival at the studio location. 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: clientApi
  url: ../openapi/mindbody-client-api-openapi.yml
  type: openapi
workflows:
- workflowId: client-arrival-checkin
  summary: Search for a client and record their arrival at a location.
  description: >-
    Searches the client directory by search text and, when a client is found,
    logs the arrival at the supplied location.
  inputs:
    type: object
    required:
    - apiKey
    - siteId
    - authorization
    - searchText
    - locationId
    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 from which to pull data and write records.
      authorization:
        type: string
        description: A staff user authorization (OAuth bearer) token.
      searchText:
        type: string
        description: Name, email, or other text used to find the client.
      locationId:
        type: integer
        description: The ID of the location where the arrival is logged.
  steps:
  - stepId: findClient
    description: >-
      Search the client directory by the supplied search text and capture the
      first matching client id.
    operationId: getClients
    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.searchText
      in: query
      value: $inputs.searchText
    - name: request.limit
      in: query
      value: 1
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      clientId: $response.body#/Clients/0/Id
    onSuccess:
    - name: clientFound
      type: goto
      stepId: logArrival
      criteria:
      - context: $response.body
        condition: $.Clients.length > 0
        type: jsonpath
    - name: clientMissing
      type: end
      criteria:
      - context: $response.body
        condition: $.Clients.length == 0
        type: jsonpath
  - stepId: logArrival
    description: >-
      Log the matched client's arrival at the supplied location.
    operationId: addArrival
    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: $steps.findClient.outputs.clientId
        LocationId: $inputs.locationId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      arrivalAdded: $response.body#/ArrivalAdded
      clientService: $response.body#/ClientService
  outputs:
    clientId: $steps.findClient.outputs.clientId
    arrivalAdded: $steps.logArrival.outputs.arrivalAdded

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-client-arrival-checkin-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.