canonical: https://jentic.com/apis/zeevou.com/zeevou

# Zeevou API

Vacation rental and property management API for deals, bookings, add-ons, agreements, accounting and location management. The API exposes 39 endpoints secured with bearer authentication.

## For AI agents

Programmatically create accounting schema defaults, list accounting schema defaults. Covers 39 operations with bearer authentication.

## Scope

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

## Capabilities

- Create accounting schema defaults
- List accounting schema defaults
- Get accounting schema defaults by ID
- Update accounting schema defaults
- Delete accounting schema defaults

## Use cases

### E-Commerce Operations

Use the Zeevou API to perform e commerce operations programmatically. The API provides 39 endpoints covering core functionality including create accounting schema defaults, list accounting schema defaults, get accounting schema defaults by id.

Example prompt: Call POST `/apis/accounting_schema_defaults` to create accounting schema defaults

### Automated Accounting Schema Defaults Management

Automate accounting schema defaults operations by combining multiple Zeevou API endpoints. Agents can list accounting schema defaults and then get accounting schema defaults by id in a single workflow.

Example prompt: Call GET `/apis/accounting_schema_defaults` to list accounting schema defaults, then verify the result

### AI Agent Integration via Jentic

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/apis/accounting_schema_defaults` | Create accounting schema defaults |
| GET | `/apis/accounting_schema_defaults` | List accounting schema defaults |
| GET | `/apis/accounting_schema_defaults/{id}` | Get accounting schema defaults by ID |
| PUT | `/apis/accounting_schema_defaults/{id}` | Update accounting schema defaults |
| DELETE | `/apis/accounting_schema_defaults/{id}` | Delete accounting schema defaults |
| POST | `/apis/add-ons` | Create add-ons |
| GET | `/apis/add-ons` | List add-ons |
| GET | `/apis/add-ons/{id}` | Get add-ons by ID |

## Key resources

- **Accounting Schema Defaults** — Operations related to Accounting Schema Defaults
- **Add Ons** — Operations related to Add Ons
- **Addon Images** — Operations related to Addon Images
- **Addresses** — Operations related to Addresses
- **Agreement Configs** — Operations related to Agreement Configs

## 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:** 73 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 59 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/zeevou.com/zeevou/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 Zeevou by hand means carrying its bearer token on every call, learning the resource layout under hub.zeevou.com/apis, and coding create, read, update, and delete handling yourself. Through Jentic you install once, import Zeevou from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Zeevou puts the record id in the URL path (`/apis/accounting_schema_defaults/{id}`), so a rule can pin your agent to one record. You choose the operations it may call, so destructive ones like DELETE are not included unless you add them.
- **Credential handling:** Your Zeevou 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 'create accounting schema defaults' or 'list add-ons', and Jentic returns the matching Zeevou 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 Zeevou API use?

The Zeevou 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 create accounting schema defaults with the Zeevou API?

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

### What are the rate limits for the Zeevou 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 accounting schema defaults through Jentic?

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

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

The Zeevou API exposes 39 endpoints covering accounting schema defaults, add ons, addon images operations.

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

Yes. Jentic One runs self-hosted, so your own rules decide which Zeevou operations and credentials the agent may use. You pick the operations it can call, so destructive ones such as DELETE on `/apis/accounting_schema_defaults/{id}` stay out unless you add them. Because Zeevou puts the record id in the URL path, like `/apis/add-ons/{id}`, a rule can pin the agent to a single record rather than the whole account.