Skaala API

Name: Skaala API
Brand: Skaala API
Availability: InStock

✓ Official Vendor SpecCRMContact ManagementapiKey15 EndpointsREST

For Agents

Programmatically post /conversations, get /conversations. Covers 15 operations with apiKey authentication.

Use for: I need to post /conversations, I want to /conversations, Search for /calls, Find all post /bookings

Install Jentic One Beta

Connect the Skaala API to your agent

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

POST /conversations

GET /conversations

Integrate Skaala API into automated workflows

Query and filter Skaala API records by parameters

GET STARTED

Start building with Skaala API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Skaala API for, with concrete tasks.

★ CRM Operations

Use the Skaala API to perform crm operations programmatically. The API provides 15 endpoints covering core functionality including post /conversations, get /conversations, get /calls.

Call POST /conversations to post /conversations

Automated Bookings Management

Automate bookings operations by combining multiple Skaala API endpoints. Agents can get /conversations and then get /calls in a single workflow.

Call GET /conversations to get /conversations, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Skaala API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'post /conversations', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

15 endpoints — ai-powered receptionist platform api for managing bookings, calls, contacts, and more.

METHOD

PATH

DESCRIPTION

POST

/conversations

POST /conversations

GET

/conversations

GET /conversations

GET

/calls

GET /calls

POST

/bookings

POST /bookings

GET

/bookings

GET /bookings

POST

/webhooks/verify

POST /webhooks/verify

GET

/bookings/{bookingId}

GET /bookings/{bookingId}

PUT

/bookings/{bookingId}

PUT /bookings/{bookingId}

POST

/conversations

POST /conversations

GET

/conversations

GET /conversations

GET

/calls

GET /calls

POST

/bookings

POST /bookings

GET

/bookings

GET /bookings

POST

/webhooks/verify

POST /webhooks/verify

Why Jentic?

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

Credential isolation

Skaala API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'post /conversations') and Jentic returns the matching Skaala API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Skaala API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Skaala API through Jentic.

What authentication does the Skaala API use?

The Skaala API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I post /conversations with the Skaala API?

Yes. Use the POST /conversations endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Skaala API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I post /conversations through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'post /conversations'. Jentic returns the matching Skaala API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Skaala API have?

The Skaala API exposes 15 endpoints covering bookings, calls, conversations operations.

Skaala API

Connect the Skaala API to your agent

Capabilities

Start building with Skaala API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs