Mindbody · Schema

AddClientToClassRequest

Implementation of the 'AddClientToClassRequest' model.

FitnessWellnessBeautySchedulingBookingPoint-of-SaleStudiosSalonsSpasWebhook

Properties

Name Type Description
ClientId string The ID of the client who is being booked into the class
ClassId integer The ID of the class into which the client is being booked
Test boolean When `true`, indicates that input information is validated, but not committed.
When `false`, the information is committed and the database is affected.
Default: **false**
RequirePayment boolean When `true`, the client must have an active, usable pricing option on their account.
When `false` or omitted, an active pricing option is not required to complete the client’s booking.
Waitlist boolean When `true`, indicates that the client should be added to a specific class waiting list.
When `false`, the client should not be added to the waiting list.
SendEmail boolean When `true`, the subscriber’s configured Booking Confirmation automatic email is sent to the client. Note that an email is sent only if the client has an email address and automatic emails have been s
WaitlistEntryId integer The ID of the waiting list entry from which you are moving a client into a class.
ClientServiceId integer The ID of the pricing option on the client’s account that you want to use to pay for this booking, if payment is required at the time of the update.
CrossRegionalBooking boolean When `true`, cross regional series are checked and used if applicable.
CrossRegionalBookingClientServiceSiteId integer If the request is cross regional, use a purchased pricing option from this specified site. If omitted, an attempt is made to use an applicable pricing option from the local site.
UniqueId integer The UniqueID of the client who is being booked into the class
View JSON Schema on GitHub

JSON Schema

public-api-v6-add-client-to-class-request-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/mindbody/refs/heads/main/json-schema/public-api-v6-add-client-to-class-request-schema.json",
  "title": "AddClientToClassRequest",
  "description": "Implementation of the 'AddClientToClassRequest' model.",
  "type": "object",
  "properties": {
    "ClientId": {
      "type": "string",
      "description": "The ID of the client who is being booked into the class",
      "example": "example-value"
    },
    "ClassId": {
      "type": "integer",
      "format": "int32",
      "description": "The ID of the class into which the client is being booked",
      "example": 123456
    },
    "Test": {
      "type": "boolean",
      "description": "When `true`, indicates that input information is validated, but not committed.<br /> When `false`, the information is committed and the database is affected.<br /> Default: **false**",
      "example": true
    },
    "RequirePayment": {
      "type": "boolean",
      "description": "When `true`, the client must have an active, usable pricing option on their account.<br /> When `false` or omitted, an active pricing option is not required to complete the client\u2019s booking.",
      "example": true
    },
    "Waitlist": {
      "type": "boolean",
      "description": "When `true`, indicates that the client should be added to a specific class waiting list.<br /> When `false`, the client should not be added to the waiting list.",
      "example": true
    },
    "SendEmail": {
      "type": "boolean",
      "description": "When `true`, the subscriber\u2019s configured Booking Confirmation automatic email is sent to the client. Note that an email is sent only if the client has an email address and automatic emails have been set up.<br /> When `false`, indicates that the client does not receive emails.<br /> Default: **false** **Note**: When the Authorization header is passed and the SendEmail is set to `true`, then an email will be sent. When the Authorization header is passed and the SendEmail is set to `false`, then a",
      "example": true
    },
    "WaitlistEntryId": {
      "type": "integer",
      "format": "int32",
      "description": "The ID of the waiting list entry from which you are moving a client into a class.",
      "example": 123456
    },
    "ClientServiceId": {
      "type": "integer",
      "format": "int32",
      "description": "The ID of the pricing option on the client\u2019s account that you want to use to pay for this booking, if payment is required at the time of the update.",
      "example": 123456
    },
    "CrossRegionalBooking": {
      "type": "boolean",
      "description": "When `true`, cross regional series are checked and used if applicable.",
      "example": true
    },
    "CrossRegionalBookingClientServiceSiteId": {
      "type": "integer",
      "format": "int32",
      "description": "If the request is cross regional, use a purchased pricing option from this specified site. If omitted, an attempt is made to use an applicable pricing option from the local site.",
      "example": 123456
    },
    "UniqueId": {
      "type": "integer",
      "format": "int32",
      "description": "The UniqueID of the client who is being booked into the class",
      "example": 123456
    }
  }
}

Work with this as data

Every JSON Schema 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 schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema 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 JSON Schema
curl "https://apis.io/api/v1/json-schemas/public-api-v6-add-client-to-class-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?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.