Install Jentic One Beta

Connect the Jammed Bookings API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Jammed Bookings 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fjammedapp.com%2Fjammedapp" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fjammedapp.com%2Fjammedapp" | 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 Jammed Bookings API.

Create, retrieve, and update bookings made against a studio's calendar

Pull lifecycle event lists - cancelled, started, finished, reminder, and updated bookings

List transactions attached to a booking for till and reconciliation reporting

Fetch one-hour-before reminder events to drive notifications and front-of-house prep

GET STARTED

Start building with Jammed Bookings API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Jammed Bookings API for, with concrete tasks.

★ Studio Booking Sync to External Calendars

Studio operators sync Jammed bookings into their own staff calendars and front-of-house dashboards. The /bookings/updated.json feed returns recently changed bookings and individual /bookings/{code}.json calls fetch the full record, letting an integration mirror booking state into Google Calendar or a custom ops dashboard.

GET /bookings/updated.json since last cursor and upsert each returned booking into the staff Google Calendar

Front-of-House Reminder Workflow

Front-of-house teams and customers benefit from a reminder one hour before a booking starts. The /bookings/one_hour_before.json and /bookings/reminder.json endpoints return the bookings due for reminders, which an integration uses to send SMS or email confirmations and to prepare the room.

GET /bookings/one_hour_before.json and dispatch an SMS to each customer with their booking code

Transaction Reconciliation

Studio managers reconcile till takings against booking transactions at end of day. GET /bookings/{code}/transactions.json returns the transactions for a booking and a POST against the same path records new charges, supporting a closing routine that ties payments to specific bookings without manual data entry.

Iterate through today's bookings and GET /bookings/{code}/transactions.json for each, then write the totals to the daily ledger

AI Agent Studio Assistant

An AI assistant for a studio handles booking lookups and reminder dispatch on behalf of front-of-house staff. Through Jentic the agent searches for 'get jammed booking', loads the GET /bookings/{code}.json schema, and executes against the Jammed API with the bearer key managed in your Jentic One instance.

Search Jentic for 'get jammed booking by code', execute GET /bookings/{code}.json, and reply with the booking time, room, and customer name

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/bookings.json

List bookings with filters

POST

/bookings.json

Create a booking

GET

/bookings/{code}.json

Retrieve a booking by code

PATCH

/bookings/{code}.json

Update a booking

GET

/bookings/cancelled.json

List recently cancelled bookings

GET

/bookings/one_hour_before.json

List bookings due to start within an hour

GET

/bookings/{code}/transactions.json

List transactions for a booking

POST

/bookings/{code}/transactions.json

Record a transaction against a booking

GET

/bookings.json

List bookings with filters

POST

/bookings.json

Create a booking

GET

/bookings/{code}.json

Retrieve a booking by code

PATCH

/bookings/{code}.json

Update a booking

GET

/bookings/cancelled.json

List recently cancelled bookings

GET

/bookings/one_hour_before.json

List bookings due to start within an hour

GET

/bookings/{code}/transactions.json

List transactions for a booking

POST

/bookings/{code}/transactions.json

Record a transaction against a booking

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Jammed Bookings API by hand means building its bearer Authorization header and tracking booking lifecycle across many endpoints yourself. Through Jentic you install once, import Jammed from the API Directory, store the key once, and your agent calls it.

Permission scoping

Jammed puts the booking code in the URL path (/bookings/{code}...), so a rule can pin your agent to one booking: it can read that booking and its transactions and nothing else. You choose the operations it may call, so a booking update or a new transaction is not included unless you add it.

Credential isolation

Your Jammed API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a studio booking' or 'list cancelled bookings', and Jentic returns the matching Jammed operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Jammed Bookings API through Jentic.

Why is there no official OpenAPI spec for Jammed Bookings API?

Jammed does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Jammed Bookings API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Jammed Bookings API use?

Jammed accepts an API key as a bearer-style Authorization header. Each key is scoped to a studio account. Through Jentic the key is stored in the credential vault and the Authorization header is added to every outbound request.

Can I create a new booking with the Jammed API?

Yes. POST /bookings.json creates a booking with the customer, room, start time, and duration in the JSON body and returns the booking code used in subsequent /bookings/{code}.json calls.

What are the rate limits for the Jammed Bookings API?

Jammed does not document numeric rate limits in the spec. They publish endpoints as they are added and ask integrators to contact support for high-volume needs; pace polling-based feeds and prefer the /bookings/updated.json cursor over full reloads.

How do I list cancelled bookings through Jentic?

Search Jentic for 'list cancelled jammed bookings', load the GET /bookings/cancelled.json schema, and execute with an optional time filter. Jentic handles the Authorization header injection so the agent only supplies the date range.

Why are these endpoints polled rather than webhook-driven?

The 2.1.0 spec exposes lifecycle feeds (cancelled, started, finished, reminder, updated) as poll endpoints rather than push webhooks. Schedule a regular pull of /bookings/updated.json with a cursor to keep state in sync; this matches the way Jammed currently surfaces lifecycle events.

Can I limit what my agent is allowed to do with the Jammed Bookings API?

Yes. Jentic One is self-hosted, so your own rules decide which Jammed operations and credentials the agent may use. Because the booking code sits in the URL path (/bookings/{code}...), you can pin the agent to a single booking and let it read only that booking and its transactions via GET /bookings/{code}.json and GET /bookings/{code}/transactions.json. You choose the operations it may call, so a PATCH /bookings/{code}.json update or a POST that records a new transaction is excluded unless you add it.

Jammedapp Jammed Bookings API

Name: Jammed Bookings API
Brand: Jammed Bookings API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticProductivityCalendar SchedulingapiKey25 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage rehearsal and recording studio bookings, transactions, and lifecycle webhook events through the Jammed Bookings API.

Use for: I need to create a new booking for a studio, Retrieve a booking by its unique code, List all cancelled bookings in the last 7 days, Get the transactions attached to a specific booking

Not supported: Does not handle payment capture, room hardware control, or marketing email delivery - use for Jammed studio booking and lifecycle lookups only.

Jentic publishes the only available OpenAPI specification for Jammed Bookings API, keeping it validated and agent-ready. Jammed is a booking platform built for music rehearsal and recording studios, and the 2.1.0 API exposes endpoints for managing bookings, transactions, lifecycle webhook reads, and reminder events. The spec covers booking creation, cancellation and finished-state lookups, transaction listing per booking, and the various webhook event feeds that downstream systems poll. Authentication uses a bearer-style API key supplied in the Authorization header.

Jentic One on Github View OpenAPI Document

Connect the Jammed Bookings API to your agent

Capabilities

Start building with Jammed Bookings API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Jammedapp Jammed Bookings API