canonical: https://jentic.com/apis/swaggerhub.eloihernandeztarrago/abitari-housekeeping-integration-api

# Eloihernandeztarrago Abitari Housekeeping Integration API

Abitari Housekeeping Integration API. The API exposes 15 endpoints.

## For AI agents

Programmatically create a guest profile, update a guest profile. Covers 15 operations.

## Scope

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

## Capabilities

- Create a guest profile
- Update a guest profile
- Register a new interface
- Query and filter Abitari Housekeeping Integration API records by parameters
- Monitor Abitari Housekeeping Integration API operational status and events

## Use cases

### Developer Tools Operations

Use the Abitari Housekeeping Integration API to perform developer tools operations programmatically. The API provides 15 endpoints covering core functionality including create a guest profile, update a guest profile, register a new interface.

Example prompt: Call POST /guest to create a guest profile

### Automated Configuration (External system to Abitari) Management

Automate configuration (external system to abitari) operations by combining multiple Abitari Housekeeping Integration API endpoints. Agents can update a guest profile and then register a new interface in a single workflow.

Example prompt: Call PUT /guest to update a guest profile, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Abitari Housekeeping Integration 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 none tokens manually.

Example prompt: Search Jentic for 'create a guest profile', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /guest | Create a guest profile |
| PUT | /guest | Update a guest profile |
| POST | /interface | Register a new interface |
| POST | /lostandfound | Create a lost and found object issue. |
| PUT | /lostandfound | Update a lost and found object issue |
| POST | /reservation | Create a resevation |
| PUT | /reservation | Update a guest reservation |
| PUT | /resort | Update a resort |

## Key resources

- **Configuration (External system to Abitari)** — Operations related to Configuration (External system to Abitari)
- **Messaging** — Operations related to Messaging

## Why Jentic

- **Setup:** Wiring the Abitari Housekeeping Integration API by hand means reading its schema, coding each guest, reservation, and room request against the Abitari host, and handling responses yourself. Through Jentic you install once, import the Abitari Housekeeping Integration API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** This API carries its targets in the request body for operations like creating a guest, updating a reservation, and registering a resort, so scope your agent to the operations it needs rather than to one record: you choose the operations it may call, so writes like reservation updates are not included unless you add them.
- **Credential handling:** Any Abitari access credential 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 a guest profile' or 'log a lost and found item', and Jentic returns the matching Abitari Housekeeping Integration API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Abitari Housekeeping Integration API use?

The Abitari Housekeeping Integration API uses no authentication. 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 a guest profile with the Abitari Housekeeping Integration API?

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

### What are the rate limits for the Abitari Housekeeping Integration 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 a guest profile through Jentic?

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

### How many endpoints does the Abitari Housekeeping Integration API have?

The Abitari Housekeeping Integration API exposes 15 endpoints covering configuration (external system to abitari), messaging operations.

### Can I limit what my agent is allowed to do with the Abitari Housekeeping Integration API?

Yes. Because you run Jentic One yourself, your own rules decide which Abitari operations and credentials the agent may use. This API carries its targets in the request body, so you scope by operation rather than by record: you can allow read and create calls like POST /guest and POST /lostandfound while withholding writes such as PUT /reservation, POST /interface, or PUT /resort. The agent can only call the operations you have granted it.