vCita Weekly availability API
The Weekly availability API from vCita — 2 operation(s) for weekly availability.
The Weekly availability API from vCita — 2 operation(s) for weekly availability.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.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.curl "https://apis.io/api/v1/apis/vcita:vcita-weekly-availability-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a 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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Scheduling Weekly availability API
description: Unified OpenAPI specification for scheduling domain
version: '3.0'
x-generated:
sourceFiles:
- legacy_v1_scheduling.json
- scheduling.json
- availability.json
- availability_slots.json
- resource_management.json
pathNormalizations:
- file: legacy_v1_scheduling.json
basePath: /platform/v1
transformations:
- original: /scheduling/appointments
normalized: /platform/v1/scheduling/appointments
basePath: /platform/v1
- original: /scheduling/appointments/{appointment_id}
normalized: /platform/v1/scheduling/appointments/{appointment_id}
basePath: /platform/v1
- original: /scheduling/bookings
normalized: /platform/v1/scheduling/bookings
basePath: /platform/v1
- original: /scheduling/bookings/cancel
normalized: /platform/v1/scheduling/bookings/cancel
basePath: /platform/v1
- original: /scheduling/bookings/{booking_uid}/update_rsvp_state
normalized: /platform/v1/scheduling/bookings/{booking_uid}/update_rsvp_state
basePath: /platform/v1
- original: /scheduling/event_attendances/{event_attendance_uid}
normalized: /platform/v1/scheduling/event_attendances/{event_attendance_uid}
basePath: /platform/v1
- original: /scheduling/event_instance/{event_instance_id}
normalized: /platform/v1/scheduling/event_instance/{event_instance_id}
basePath: /platform/v1
- original: /scheduling/scheduling_forms/get_form
normalized: /platform/v1/scheduling/scheduling_forms/get_form
basePath: /platform/v1
- original: /scheduling/waitlist
normalized: /platform/v1/scheduling/waitlist
basePath: /platform/v1
- original: /scheduling/waitlist/cancel
normalized: /platform/v1/scheduling/waitlist/cancel
basePath: /platform/v1
- original: /services
normalized: /platform/v1/services
basePath: /platform/v1
- original: /staff/availability
normalized: /platform/v1/staff/availability
basePath: /platform/v1
- file: scheduling.json
basePath: /business/scheduling
transformations:
- original: /v1/appointments
normalized: /business/scheduling/v1/appointments
basePath: /business/scheduling
- original: /v1/bookings
normalized: /business/scheduling/v1/bookings
basePath: /business/scheduling
- original: /v1/bookings/accept
normalized: /business/scheduling/v1/bookings/accept
basePath: /business/scheduling
- original: /v1/bookings/cancel
normalized: /business/scheduling/v1/bookings/cancel
basePath: /business/scheduling
- original: /v1/bookings/complete
normalized: /business/scheduling/v1/bookings/complete
basePath: /business/scheduling
- original: /v1/bookings/{booking_id}
normalized: /business/scheduling/v1/bookings/{booking_id}
basePath: /business/scheduling
- original: /v1/external_calendar_items/bulk_create
normalized: /business/scheduling/v1/external_calendar_items/bulk_create
basePath: /business/scheduling
- original: /v1/external_calendar_items/bulk_deactivate
normalized: /business/scheduling/v1/external_calendar_items/bulk_deactivate
basePath: /business/scheduling
- original: /v1/external_calendar_items/connect
normalized: /business/scheduling/v1/external_calendar_items/connect
basePath: /business/scheduling
- original: /v1/external_calendar_items/deactivate_external_calendar
normalized: /business/scheduling/v1/external_calendar_items/deactivate_external_calendar
basePath: /business/scheduling
- original: /v1/external_calendar_items/disable
normalized: /business/scheduling/v1/external_calendar_items/disable
basePath: /business/scheduling
- original: /v1/external_calendar_items/disconnect
normalized: /business/scheduling/v1/external_calendar_items/disconnect
basePath: /business/scheduling
- original: /v1/external_calendar_items/report_sync_status
normalized: /business/scheduling/v1/external_calendar_items/report_sync_status
basePath: /business/scheduling
- original: /v1/external_calendar_items/start_export
normalized: /business/scheduling/v1/external_calendar_items/start_export
basePath: /business/scheduling
- original: /v1/external_calendar_items/stop_import
normalized: /business/scheduling/v1/external_calendar_items/stop_import
basePath: /business/scheduling
- original: /v1/time_slots
normalized: /business/scheduling/v1/time_slots
basePath: /business/scheduling
- original: /v1/time_slots/{time_slot_uid}
normalized: /business/scheduling/v1/time_slots/{time_slot_uid}
basePath: /business/scheduling
pathConflicts: []
componentConflicts: []
totalPaths: 35
totalComponents: 4
servers:
- url: https://api.vcita.biz
description: Unified API Gateway server
tags:
- name: Weekly availability
paths:
/business/scheduling/v1/time_slots:
post:
description: '## Overview
General availability - Create new time slot. Available for **Staff and App tokens**.
## Prerequisites
You need a `weekly_availability_uid` which can be obtained from the staff or service availability settings.
**Important**: The `business_id` parameter is required in the request body for staff token authorization. Without it, the endpoint returns 401 Unauthorized because the backend cannot resolve the business context from the token alone.'
parameters: []
responses:
'201':
description: Success
content:
application/json:
example:
data:
general_availability:
id: 123
time_slots_by_day:
- day: 0
enabled: true
slots:
- end_time: '22:00'
id: 40ci67hckste9xax
start_time: '20:00'
- day: 1
enabled: true
slots:
- end_time: '17:00'
id: phmiv974egfuyx84
start_time: 09:00
- day: 2
enabled: false
slots: []
- day: 3
enabled: false
slots: []
- day: 4
enabled: false
slots: []
- day: 5
enabled: false
slots: []
- day: 6
enabled: false
slots: []
uid: sjq2twnw8z0h33f0
success: true
summary: General availability - Create new time slot
tags:
- Weekly availability
x-amazon-apigateway-auth:
type: NONE
x-amazon-apigateway-integration:
httpMethod: POST
responses:
default:
statusCode: '201'
type: http_proxy
uri: https:///business/scheduling/v1/time_slots
x-auth-type: Application & Application User
requestBody:
content:
application/json:
schema:
properties:
business_id:
description: Business uid. Required for staff token authorization context resolution.
type: string
x-reference-to: business
day:
description: A number representing the day of the week (0 = Sunday, 6 = Saturday).
type: integer
minimum: 0
maximum: 6
end_time:
description: End time in HH:MM format (e.g., '17:00').
type: string
start_time:
description: Start time in HH:MM format (e.g., '09:00').
type: string
weekly_availability_uid:
description: Weekly availability UID. Obtain from staff or service availability settings.
type: string
x-reference-to: weekly_availability
required:
- business_id
- weekly_availability_uid
- day
- start_time
- end_time
type: object
security:
- Bearer: []
operationId: postBusinessSchedulingV1TimeSlots
x-operation-id-source: derived
/business/scheduling/v1/time_slots/{time_slot_uid}:
delete:
description: '## Overview
General availability - Remove time slot Available for **Staff and App tokens**.'
parameters:
- description: time slot uid
in: path
name: time_slot_uid
required: true
schema:
type: string
responses:
'200':
description: Success
content:
application/json:
example:
data:
general_availability:
id: 123
time_slots_by_day:
- day: 0
enabled: false
slots: []
- day: 1
enabled: true
slots:
- end_time: '17:00'
id: h6v5fxwr3f0xe4vf
start_time: 09:00
- day: 2
enabled: false
slots: []
- day: 3
enabled: false
slots: []
- day: 4
enabled: false
slots: []
- day: 5
enabled: false
slots: []
- day: 6
enabled: false
slots: []
uid: 63q3l1lex42awyzc
success: true
summary: General availability - Remove time slot
tags:
- Weekly availability
x-amazon-apigateway-auth:
type: NONE
x-amazon-apigateway-integration:
httpMethod: DELETE
responses:
default:
statusCode: '200'
type: http_proxy
uri: https:///business/scheduling/v1/time_slots/{time_slot_uid}
x-auth-type: Application & Application User
security:
- Bearer: []
operationId: deleteBusinessSchedulingV1TimeSlotsByTimeSlotUid
x-operation-id-source: derived
put:
description: '## Overview
General availability - Update time slot. Available for **Staff and App tokens**.
## Prerequisites
You need a valid `time_slot_uid` from an existing time slot, and the `start_time` and `end_time` for the updated schedule.
**Important**: The `business_id` parameter is required in the request body for staff token authorization. Without it, the endpoint returns 401 Unauthorized because the backend cannot resolve the business context from the token alone.'
parameters:
- description: Time slot UID
in: path
name: time_slot_uid
required: true
schema:
type: string
responses:
'200':
description: Success
content:
application/json:
example:
data:
general_availability:
id: 123
time_slots_by_day:
- day: 0
enabled: false
slots: []
- day: 1
enabled: true
slots:
- end_time: '17:00'
id: 0p92ib1eqvmybmdq
start_time: 09:00
- end_time: '22:00'
id: zbjrl4i2v946uyek
start_time: '20:00'
- day: 2
enabled: false
slots: []
- day: 3
enabled: false
slots: []
- day: 4
enabled: false
slots: []
- day: 5
enabled: false
slots: []
- day: 6
enabled: false
slots: []
uid: 7qyp5axp610aq39b
success: true
summary: General availability - Update time slot
tags:
- Weekly availability
x-amazon-apigateway-auth:
type: NONE
x-amazon-apigateway-integration:
httpMethod: PUT
responses:
default:
statusCode: '200'
type: http_proxy
uri: https:///business/scheduling/v1/time_slots/{time_slot_uid}
x-auth-type: Application & Application User
requestBody:
content:
application/json:
schema:
properties:
business_id:
description: Business uid. Required for staff token authorization context resolution.
type: string
x-reference-to: business
end_time:
description: End time in HH:MM format (e.g., '17:00').
type: string
start_time:
description: Start time in HH:MM format (e.g., '09:00').
type: string
weekly_availability_uid:
description: Weekly availability UID. Obtain from staff or service availability settings.
type: string
x-reference-to: weekly_availability
required:
- business_id
- weekly_availability_uid
- start_time
- end_time
type: object
security:
- Bearer: []
operationId: putBusinessSchedulingV1TimeSlotsByTimeSlotUid
x-operation-id-source: derived
components:
securitySchemes:
Bearer:
type: http
scheme: bearer
bearerFormat: JWT
description: 'Provide a valid bearer token in the Authorization header. Example: ''Authorization: Bearer {app_token}'''
x-provenance:
method: searched
source: https://developers.intandem.tech:443/reference
harvested: '2026-11-15'
tool: harvest-readme-openapi.py
note: Assembled verbatim from the OpenAPI definition ReadMe embeds in each operation page of the provider's developer portal; paths and components merged by API title, nothing authored.
assembled_from:
- https://developers.intandem.tech/reference/delete_business-scheduling-v1-time-slots-time-slot-uid.md
- https://developers.intandem.tech/reference/delete_v3-scheduling-resource-types-uid.md
- https://developers.intandem.tech/reference/delete_v3-scheduling-resources-uid.md
- https://developers.intandem.tech/reference/get_platform-v1-scheduling-appointments-appointment-id.md
- https://developers.intandem.tech/reference/get_platform-v1-scheduling-appointments.md
- https://developers.intandem.tech/reference/get_platform-v1-scheduling-bookings.md
- https://developers.intandem.tech/reference/get_platform-v1-scheduling-event-attendances-event-attendance-uid.md
- https://developers.intandem.tech/reference/get_platform-v1-scheduling-event-instance-event-instance-id.md
- https://developers.intandem.tech/reference/get_platform-v1-scheduling-scheduling-forms-get-form.md
- https://developers.intandem.tech/reference/get_platform-v1-services-1.md
- https://developers.intandem.tech/reference/get_platform-v1-staff-availability.md
- https://developers.intandem.tech/reference/get_v3-scheduling-availability-slots.md
- https://developers.intandem.tech/reference/get_v3-scheduling-resource-types-uid.md
- https://developers.intandem.tech/reference/get_v3-scheduling-resource-types.md
- https://developers.intandem.tech/reference/get_v3-scheduling-resources-uid.md
- https://developers.intandem.tech/reference/get_v3-scheduling-resources.md
- https://developers.intandem.tech/reference/post_business-scheduling-v1-appointments.md
- https://developers.intandem.tech/reference/post_business-scheduling-v1-bookings-accept.md
- https://developers.intandem.tech/reference/post_business-scheduling-v1-bookings-complete.md
- https://developers.intandem.tech/reference/post_business-scheduling-v1-bookings.md
- https://developers.intandem.tech/reference/post_business-scheduling-v1-time-slots.md
- https://developers.intandem.tech/reference/post_platform-v1-scheduling-bookings-cancel.md
- https://developers.intandem.tech/reference/post_platform-v1-scheduling-bookings.md
- https://developers.intandem.tech/reference/post_platform-v1-scheduling-waitlist.md
- https://developers.intandem.tech/reference/post_v3-scheduling-resource-types.md
- https://developers.intandem.tech/reference/post_v3-scheduling-resources.md
- https://developers.intandem.tech/reference/put_business-scheduling-v1-bookings-booking-id.md
- https://developers.intandem.tech/reference/put_business-scheduling-v1-bookings-cancel.md
- https://developers.intandem.tech/reference/put_business-scheduling-v1-external-calendar-items-bulk-create.md
- https://developers.intandem.tech/reference/put_business-scheduling-v1-external-calendar-items-bulk-deactivate.md
- https://developers.intandem.tech/reference/put_business-scheduling-v1-external-calendar-items-connect.md
- https://developers.intandem.tech/reference/put_business-scheduling-v1-external-calendar-items-deactivate-external-calendar.md
- https://developers.intandem.tech/reference/put_business-scheduling-v1-external-calendar-items-disable.md
- https://developers.intandem.tech/reference/put_business-scheduling-v1-external-calendar-items-disconnect.md
- https://developers.intandem.tech/reference/put_business-scheduling-v1-external-calendar-items-report-sync-status.md
- https://developers.intandem.tech/reference/put_business-scheduling-v1-external-calendar-items-start-export.md
- https://developers.intandem.tech/reference/put_business-scheduling-v1-external-calendar-items-stop-import.md
- https://developers.intandem.tech/reference/put_business-scheduling-v1-time-slots-time-slot-uid.md
- https://developers.intandem.tech/reference/put_platform-v1-scheduling-bookings-booking-uid-update-rsvp-state.md
- https://developers.intandem.tech/reference/put_platform-v1-scheduling-waitlist-cancel.md
- https://developers.intandem.tech/reference/put_v3-scheduling-resource-types-uid.md
- https://developers.intandem.tech/reference/put_v3-scheduling-resources-uid.md
- https://developers.intandem.tech:443/reference/delete_business-scheduling-v1-time-slots-time-slot-uid.md
- https://developers.intandem.tech:443/reference/delete_v3-scheduling-resource-types-uid.md
- https://developers.intandem.tech:443/reference/delete_v3-scheduling-resources-uid.md
- https://developers.intandem.tech:443/reference/get_platform-v1-scheduling-appointments-appointment-id.md
- https://developers.intandem.tech:443/reference/get_platform-v1-scheduling-appointments.md
- https://developers.intandem.tech:443/reference/get_platform-v1-scheduling-bookings.md
- https://developers.intandem.tech:443/reference/get_platform-v1-scheduling-event-attendances-event-attendance-uid.md
- https://developers.intandem.tech:443/reference/get_platform-v1-scheduling-event-instance-event-instance-id.md
- https://developers.intandem.tech:443/reference/get_platform-v1-scheduling-scheduling-forms-get-form.md
- https://developers.intandem.tech:443/reference/get_platform-v1-services-1.md
- https://developers.intandem.tech:443/reference/get_platform-v1-staff-availability.md
- https://developers.intandem.tech:443/reference/get_v3-scheduling-availability-slots.md
- https://developers.intandem.tech:443/reference/get_v3-scheduling-resource-types-uid.md
- https://developers.intandem.tech:443/reference/get_v3-scheduling-resource-types.md
- https://developers.intandem.tech:443/reference/get_v3-scheduling-resources-uid.md
- https://developers.intandem.tech:443/reference/get_v3-scheduling-resources.md
- https://developers.intandem.tech:443/reference/post_business-scheduling-v1-appointments.md
- https://developers.intandem.tech:443/reference/post_business-scheduling-v1-bookings-accept.md
- https://developers.intandem.tech:443/reference/post_business-scheduling-v1-bookings-complete.md
- https://developers.intandem.tech:443/reference/post_business-scheduling-v1-bookings.md
- https://developers.intandem.tech:443/reference/post_business-scheduling-v1-time-slots.md
- https://developers.intandem.tech:443/reference/post_platform-v1-scheduling-bookings-cancel.md
- https://developers.intandem.tech:443/reference/post_platform-v1-scheduling-bookings.md
- https://developers.intandem.tech:443/reference/post_platform-v1-scheduling-waitlist.md
- https://developers.intandem.tech:443/reference/post_v3-scheduling-resource-types.md
- https://developers.intandem.tech:443/reference/post_v3-scheduling-resources.md
- https://developers.intandem.tech:443/reference/put_business-scheduling-v1-bookings-booking-id.md
- https://developers.intandem.tech:443/reference/put_business-scheduling-v1-bookings-cancel.md
- https://developers.intandem.tech:443/reference/put_business-scheduling-v1-external-calendar-items-bulk-create.md
- https://developers.intandem.tech:443/reference/put_business-scheduling-v1-external-calendar-items-bulk-deactivate.md
- https://developers.intandem.tech:443/reference/put_business-scheduling-v1-external-calendar-items-connect.md
- https://developers.intandem.tech:443/reference/put_business-scheduling-v1-external-calendar-items-deactivate-external-calendar.md
- https://developers.intandem.tech:443/reference/put_business-scheduling-v1-external-calendar-items-disable.md
- https://developers.intandem.tech:443/reference/put_business-scheduling-v1-external-calendar-items-disconnect.md
- https://developers.intandem.tech:443/reference/put_business-scheduling-v1-external-calendar-items-report-sync-status.md
- https://developers.intandem.tech:443/reference/put_business-scheduling-v1-external-calendar-items-start-export.md
- https://developers.intandem.tech:443/reference/put_business-scheduling-v1-external-calendar-items-stop-import.md
- https://developers.intandem.tech:443/reference/put_business-scheduling-v1-time-slots-time-slot-uid.md
- https://developers.intandem.tech:443/reference/put_platform-v1-scheduling-bookings-booking-uid-update-rsvp-state.md
- https://developers.intandem.tech:443/reference/put_platform-v1-scheduling-waitlist-cancel.md
- https://developers.intandem.tech:443/reference/put_v3-scheduling-resource-types-uid.md
- https://developers.intandem.tech:443/reference/put_v3-scheduling-resources-uid.md
merge:
pages: 84
deduped: 128
conflicts_kept_first: 0