canonical: https://jentic.com/apis/slottable.app/slottable

# Slottable App Slottable API

Slottable scheduling and booking management API. Manage tokens, webhooks, contacts, slot types, slot type instances, rosters, and bookings. The API exposes 14 endpoints secured with bearer authentication.

## For AI agents

Programmatically validate API token, create a webhook. Covers 14 operations with bearer authentication.

## Scope

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

## Capabilities

- Validate API token
- Create a webhook
- List webhooks
- Get a webhook
- Delete a webhook

## Use cases

### CRM Operations

Use the Slottable API to perform crm operations programmatically. The API provides 14 endpoints covering core functionality including validate API token, create a webhook, list webhooks.

Example prompt: Call GET `/api/v1/token` to validate API token

### Automated Bookings Management

Automate bookings operations by combining multiple Slottable API endpoints. Agents can create a webhook and then list webhooks in a single workflow.

Example prompt: Call POST `/api/v1/companies/{company_id}/webhooks` to create a webhook, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Slottable 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 bearer tokens manually.

Example prompt: Search Jentic for 'validate API token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/token` | Validate API token |
| POST | `/api/v1/companies/{company_id}/webhooks` | Create a webhook |
| GET | `/api/v1/companies/{company_id}/webhooks` | List webhooks |
| GET | `/api/v1/companies/{company_id}/webhooks/{id}` | Get a webhook |
| DELETE | `/api/v1/companies/{company_id}/webhooks/{id}` | Delete a webhook |
| GET | `/api/v1/companies/{company_id}/contacts` | List contacts |
| GET | `/api/v1/companies/{company_id}/contacts/{id}` | Get a contact |
| GET | `/api/v1/companies/{company_id}/slot-types` | List slot types |

## Key resources

- **Bookings** — Operations related to Bookings
- **Contacts** — Operations related to Contacts
- **Roster** — Operations related to Roster
- **Slot Type Instances** — Operations related to Slot Type Instances
- **Slot Types** — Operations related to Slot Types

## 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:** 70 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 84 / 100
- **View full report:** https://jentic.com/apis/slottable.app/slottable/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 Slottable by hand means handling its bearer auth against slottable.app, fetching a token, and managing retries yourself. Through Jentic you install once, import the Slottable API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Slottable puts the company id in the URL path (`/api/v1/companies/{company_id}/...`), so a rule can pin your agent to one company: it can read that company's contacts, slot types, and webhooks. You choose the operations it may call, so destructive ones like deleting a webhook are not included unless you add them.
- **Credential handling:** Your Slottable token 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 a company's contacts' or 'register a webhook', and Jentic returns the matching Slottable 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 Slottable API use?

The Slottable API uses a Bearer token 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 validate API token with the Slottable API?

Yes. Use the GET `/api/v1/token` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Slottable 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 validate API token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'validate API token'. Jentic returns the matching Slottable API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Slottable API have?

The Slottable API exposes 14 endpoints covering bookings, contacts, roster operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Slottable operations and credentials the agent may use. Since the company id sits in the URL path (`/api/v1/companies/{company_id}/...`), you can pin the agent to a single company and grant only read operations such as listing contacts, slot types, and webhooks. Destructive calls like deleting a webhook stay off unless you explicitly allow them.