canonical: https://jentic.com/apis/skaala.ai/skaala

# Skaala API

AI-powered receptionist platform API for managing bookings, calls, contacts, and more. The API exposes 15 endpoints secured with apiKey authentication.

## For AI agents

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

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- POST /conversations
- GET /conversations
- Integrate Skaala API into automated workflows
- Query and filter Skaala API records by parameters
- Monitor Skaala API operational status and events

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

| 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}` |

## Key resources

- **Bookings** — Booking management
- **Calls** — Call management
- **Conversations** — Conversation management
- **Webhooks** — Webhook management

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 13 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 49 / 100
  - Developer Experience & Jentic Compatibility: 67 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 2 / 100
- **View full report:** https://jentic.com/apis/skaala.ai/skaala/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Skaala API by hand means setting up its key in the Authorization header and carrying it across every conversation, call, and booking request yourself. Through Jentic you install once, import Skaala from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Skaala puts the booking id in the URL path (`/bookings/{bookingId}`), so a rule can pin your agent to one booking: it can read and update that booking and nothing else. You choose the operations it may call, so creating new bookings or reading conversations is not included unless you add it.
- **Credential handling:** Your Skaala API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list conversations' or 'read a booking', and Jentic returns the matching Skaala operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the Skaala API?

Yes. Because you run Jentic One yourself, your own rules decide which Skaala operations and credentials the agent may use. Since Skaala puts the booking id in the URL path (`/bookings/{bookingId}`), you can pin the agent to a single booking so it can read and update that one booking and nothing else. Any other operation, such as creating new bookings or reading conversations, stays off limits unless you explicitly grant it.