Akadadance Akada API

Name: Akada API
Brand: Akada API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentEducationStudent ManagementapiKey235 EndpointsREST

For Agents

Manage dance-studio operations programmatically — accounts, students, enrolments, schedules, attendance, invoices, and saved payment cards (including Stripe attachment).

Install Jentic One Beta

Connect the Akada API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Akada 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 Akada API.

Manage customer accounts including info, contacts, parents, and default school

Maintain student records, enrolments, attendance, and schedule entries

Save, update, and delete customer payment cards and attach Stripe payment methods

GET STARTED

Start building with Akada API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Akada API, keeping it validated and agent-ready. Akada Dance is a school management platform for dance studios — the v4 API covers customer accounts, family and student records, class enrolment, attendance, schedules, payments and saved cards (including Stripe attachment), invoices, communications, and studio admin operations. With 235 endpoints across 180 paths, the surface is large and resource-oriented, grouped by customer, family, student, school, and admin scopes.

Use Cases

Patterns agents use Akada API for, with concrete tasks.

★ Studio customer onboarding

Drive a new-customer signup flow end to end — create the account, capture parent and emergency contacts, set the default school, mark onboarding steps complete, and attach a payment card. Akada exposes each of these as a discrete endpoint, so an agent can step through onboarding and report progress.

POST /api/v4/customer/auth/create-account, then POST /api/v4/customer/account/parents and POST /api/v4/customer/account/onboard/complete for each step

Saved card and Stripe lifecycle

Manage a customer's payment instruments without sending the agent to the studio dashboard. Akada exposes endpoints to update, delete, and view history of saved cards, configure recurring billing, and attach a Stripe payment method via the Stripe setup intent flow.

POST /api/v4/customer/account/card/stripe/setup to start setup, then POST /api/v4/customer/account/card/stripe/attach with the resulting payment method

Self-service account maintenance bot

Power a chatbot that handles routine parent requests — update emergency contacts, change the saved card address, set a default school, view the privacy policy. The bot maps each user request to a single Akada endpoint and confirms success.

POST /api/v4/customer/account/contacts to update the parent's emergency contact list with a new entry

AI agent integration via Jentic

Studios can let an AI assistant handle account-level requests through Jentic — the agent finds the right Akada endpoint by intent, the AkadaApiKey stays in the Jentic vault, and the agent executes the call without ever holding the credential.

Search Jentic for 'update the customer's saved credit card', load the matching Akada operation, and execute with the new card details

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/api/v4/customer/auth/create-account

Create a new customer account

GET

/api/v4/customer/account/info

Get the logged-in customer's info

POST

/api/v4/customer/account/info

Update the customer's info

POST

/api/v4/customer/account/card

Update the saved credit card

DELETE

/api/v4/customer/account/card

Delete the saved credit card

POST

/api/v4/customer/account/card/stripe/setup

Start Stripe card setup

POST

/api/v4/customer/account/card/stripe/attach

Attach a Stripe payment method

POST

/api/v4/customer/auth/create-account

Create a new customer account

GET

/api/v4/customer/account/info

Get the logged-in customer's info

POST

/api/v4/customer/account/info

Update the customer's info

POST

/api/v4/customer/account/card

Update the saved credit card

DELETE

/api/v4/customer/account/card

Delete the saved credit card

Why Jentic?

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

Credential isolation

Akada AkadaApiKey and customer tokens are stored encrypted in the Jentic vault. Agents receive scoped execution capabilities — raw credentials never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'attach a Stripe card to a customer') and Jentic returns the matching Akada operation with its input schema so the agent calls the right endpoint without reading docs.

Time to first call

Direct Akada integration: 3-5 days to wire auth, customer flows, and Stripe attach. Through Jentic: well under an hour for a single operation.

FAQs

Specific to using Akada API through Jentic.

Why is there no official OpenAPI spec for Akada API?

Akada Dance does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Akada 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 Akada API use?

Akada uses an API key in a custom header named AkadaApiKey on every request, plus a customer-level token for the customer login flow. Through Jentic, the AkadaApiKey is stored in the encrypted Jentic vault and injected at execution time.

Can I attach a Stripe payment method to an Akada customer?

Yes. Call POST /api/v4/customer/account/card/stripe/setup to start a Stripe setup intent, complete the setup on the client, then POST /api/v4/customer/account/card/stripe/attach with the resulting payment method id to attach it to the customer.

How do I update a customer's emergency contacts through Jentic?

Use the Jentic search query 'update customer emergency contacts'. Jentic returns the POST /api/v4/customer/account/contacts operation; provide the contact list payload and Jentic injects the AkadaApiKey automatically.

Are there rate limits on the Akada API?

Rate limits are not declared in the OpenAPI spec; usage is governed by your studio plan. The endpoint surface is large (235 operations) but most account-level calls are low-volume per customer.

What customer authentication endpoints are available?

POST /api/v4/customer/auth/create-account creates a new account and POST /api/v4/customer/auth/login/redeem-token issues an authorization token for an existing customer. Other auth endpoints under /customer/auth handle the rest of the login lifecycle.

Akadadance Akada API

Connect the Akada API to your agent

Capabilities

Start building with Akada API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs