canonical: https://jentic.com/apis/vyte.in/vyte

# Vyte In Vyte API

Vyte scheduling API for managing events, users, slots, and appointment booking. The API exposes 18 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create an event, list all events. Covers 18 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Create an event
- List all events
- Get event details
- Update an event
- Confirm an event
- Cancel an event
- Add invitees to event

## Use cases

### E-Commerce Operations

Use the Vyte API to perform e commerce operations programmatically. The API provides 18 endpoints covering core functionality including create an event, list all events, get event details.

Example prompt: Call POST `/v2/events` to create an event

### Automated Events Management

Automate events operations by combining multiple Vyte API endpoints. Agents can list all events and then get event details in a single workflow.

Example prompt: Call GET `/v2/events` to list all events, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Vyte 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 'create an event', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v2/events` | Create an event |
| GET | `/v2/events` | List all events |
| GET | `/v2/events/{event_id}` | Get event details |
| PUT | `/v2/events/{event_id}` | Update an event |
| POST | `/v2/events/{event_id}/confirm` | Confirm an event |
| POST | `/v2/events/{event_id}/cancel` | Cancel an event |
| POST | `/v2/events/{event_id}/invitees` | Add invitees to event |
| POST | `/v2/events/{event_id}/invitees/{invitee_id}` | Remove invitee from event |

## Key resources

- **Events** — Operations related to Events
- **Slots** — Operations related to Slots
- **Users** — Operations related to Users

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 76 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/vyte.in/vyte/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 Vyte API by hand means putting your key in the Authorization header, pointing at api.vyte.in, and threading it through every scheduling call yourself. Through Jentic you install once, import the Vyte API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The Vyte API puts the event id in the URL path (`/v2/events/{event_id}`), so a rule can pin your agent to one event. You choose the operations it may call, so you can allow creating events and confirming them while a destructive one like cancelling an event is not included unless you add it.
- **Credential handling:** Your Vyte 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 'create an event' or 'add an invitee to an event', and Jentic returns the matching Vyte API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Vyte API use?

The Vyte 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 create an event with the Vyte API?

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

### What are the rate limits for the Vyte 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 create an event through Jentic?

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

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

The Vyte API exposes 18 endpoints covering events, slots, users operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Vyte API operations your agent may call, so you can allow it to create events (POST `/v2/events`) and confirm them (POST `/v2/events/{event_id}/confirm`) while leaving a destructive operation like cancelling an event out unless you choose to add it. Since the Vyte API carries the event id in the URL path (`/v2/events/{event_id}`), a rule can also pin the agent to a single event. Your API key is held only by your Jentic One instance and injected at call time, so the agent never sees the raw credential.