MakePlans API

Name: MakePlans API
Brand: MakePlans API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar SchedulingapiKey70 EndpointsREST

For Agents

Manage MakePlans appointment bookings, services, resources, and providers. Used by agents that schedule, confirm, cancel, or look up appointments and class sign-ups for service businesses.

Install Jentic One Beta

Connect the MakePlans API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MakePlans API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MakePlans API.

Search available slots for a service over a chosen date range and book one

Confirm, decline, or cancel a specific booking by ID

Create recurring bookings tied to a single collection ID for batch updates

GET STARTED

Start building with MakePlans API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use MakePlans API for, with concrete tasks.

★ Online Appointment Booking

Service businesses (clinics, salons, studios) need to expose available slots to customers and capture bookings. The MakePlans slots and bookings endpoints return availability for a given service, then create the booking against a chosen slot, provider, and customer record. Confirmation, decline, and cancel endpoints close the loop with the customer.

Query slots for service haircut on the requested date, POST /bookings against the chosen slot with the customer person ID, and PUT /bookings/{id}/confirm.

Recurring Class Sign-Ups

Yoga studios, language schools, and similar businesses run recurring classes that customers sign up for once and attend weekly. The MakePlans recurring-bookings endpoints create a series tied to a single collection ID, so cancellations and updates can apply across the whole series. Resource and provider linkage keeps capacity management simple.

POST /bookings/recurring with the weekly schedule for a 12-week yoga course and capture the collection ID for later updates.

Webhook-Driven Booking Sync

Integrations that mirror MakePlans bookings into a CRM, email tool, or calendar need push delivery. The MakePlans webhook endpoints register a callback URL that fires on booking events (created, updated, cancelled) and the response carries booking and person details so the receiver can update its own record without an additional fetch.

POST /webhooks with the booking-created event and the receiver URL, then verify by creating a test booking and inspecting the callback payload.

AI Agent Booking Concierge

Reception and concierge agents handle a flow of 'book me in', 'move my appointment', 'what's available'. Through Jentic the agent searches by intent, loads the schema, and executes the right MakePlans operation with the API key kept in the vault. The same loop powers customer-facing chat agents and internal call-deflection assistants.

Use Jentic to search 'book a slot on makeplans', execute POST /bookings with the resolved service, slot, and customer, and confirm with PUT /bookings/{id}/confirm.

Key Endpoints

70 endpoints — jentic publishes the only available openapi specification for makeplans api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/bookings

Create a new booking

GET

/bookings/upcoming

List upcoming bookings

PUT

/bookings/{booking_id}/confirm

Confirm a booking

PUT

/bookings/{booking_id}/cancel

Cancel a booking

POST

/bookings/recurring

Create recurring bookings

GET

/bookings/recent

List recent bookings

POST

/bookings

Create a new booking

GET

/bookings/upcoming

List upcoming bookings

PUT

/bookings/{booking_id}/confirm

Confirm a booking

PUT

/bookings/{booking_id}/cancel

Cancel a booking

POST

/bookings/recurring

Create recurring bookings

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The MakePlans API key is stored encrypted in the Jentic vault. Agents call the API through a scoped execution token and Jentic injects the Authorization header server-side, so the raw key never enters the agent context.

Intent-based discovery

Agents search by intent (e.g., 'book an appointment') and Jentic returns the right MakePlans endpoint with its input schema, removing the need to keep all 70 operations in prompt context.

Time to first call

Direct MakePlans integration: a couple of days to wire auth, slot search, booking creation, and webhook handling. Through Jentic: under 2 hours — search, load, execute.

FAQs

Specific to using MakePlans API through Jentic.

Why is there no official OpenAPI spec for MakePlans API?

MakePlans does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MakePlans API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the MakePlans API use?

MakePlans uses an API key passed in the Authorization header against a per-account subdomain. Through Jentic the key is encrypted in the vault and injected at execute time so the agent never sees the raw value.

Can I create a booking through the API?

Yes. POST /bookings with the service, slot, person, and provider IDs returns the new booking. Follow up with PUT /bookings/{booking_id}/confirm to confirm it.

How do I create a recurring booking series?

Call POST /bookings/recurring with the schedule and the underlying booking template. The response returns a collection ID that can be used to fetch or cancel every occurrence in the series.

What are the rate limits for the MakePlans API?

The OpenAPI spec does not declare numeric rate limits — they depend on your MakePlans plan and account subdomain. Confirm with MakePlans support before driving high-volume integrations.

How do I cancel a booking through Jentic?

Run pip install jentic, search 'cancel a makeplans booking', load the schema for PUT /bookings/{booking_id}/cancel, and execute with the booking ID. Jentic injects the Authorization header from the encrypted vault.

MakePlans API

Connect the MakePlans API to your agent

Capabilities

Start building with MakePlans API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs