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

# Eloihernandeztarrago Abitari Housekeeping Integration API for Guest Facing

Abitari Housekeeping Integration API for Guest Facing. The API exposes 6 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically create a petition to the hotel made by a guest, create a new connection to the API. Covers 6 operations with oauth2 authentication.

## Scope

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

## Capabilities

- Create a petition to the hotel made by a guest
- Starts a pending connection
- Subscribe to a new webhook
- Change webhook url
- Unsubscribe from an existing webhook

## Use cases

### Developer Tools Operations

Use the Abitari Housekeeping Integration API for Guest Facing to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including create a petition to the hotel made by a guest, create a new connection to the API, starts a pending connection.

Example prompt: Call POST /api/guestpetition to create a petition to the hotel made by a guest

### Automated Messaging Management

Automate messaging operations by combining multiple Abitari Housekeeping Integration API for Guest Facing endpoints. Agents can create a new connection to the API and then starts a pending connection in a single workflow.

Example prompt: Call POST /autoinstall/connect to create a new connection to the API, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Abitari Housekeeping Integration API for Guest Facing 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 oauth2 tokens manually.

Example prompt: Search Jentic for 'create a petition to the hotel made by a guest', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/guestpetition | Create a petition to the hotel made by a guest |
| POST | /autoinstall/connect | Create a new connection to the API |
| POST | /autoinstall/connect/start | Starts a pending connection |
| POST | /webhooks | Subscribe to a new webhook |
| PUT | /webhooks/{topic} | Change webhook url |
| DELETE | /webhooks/{topic} | Unsubscribe from an existing webhook |

## Key resources

- **Messaging** — Operations related to Messaging
- **Setup** — Operations related to Setup

## Why Jentic

- **Setup:** Wiring the Abitari Housekeeping Integration API for Guest Facing by hand means implementing its OAuth2 authorization-code flow against Abitari's identity host, managing token refresh, and handling webhook registration yourself. Through Jentic you install once, import the Abitari Housekeeping Integration API for Guest Facing from the API Directory, store the OAuth2 credential once, and your agent calls it.
- **Permission scoping:** This API sends its targets in the request body for operations like creating a guest petition and registering a webhook, so scope your agent to the operations it needs rather than to one record: you choose the operations it may call, so webhook removal is not included unless you add it.
- **Credential handling:** Your Abitari OAuth2 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 petition to the hotel' or 'register a housekeeping webhook', and Jentic returns the matching Abitari Housekeeping Integration API for Guest Facing 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 for Guest Facing use?

The Abitari Housekeeping Integration API for Guest Facing uses OAuth 2.0 for authorization. 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 petition to the hotel made by a guest with the Abitari Housekeeping Integration API for Guest Facing?

Yes. Use the POST /api/guestpetition 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 for Guest Facing?

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 petition to the hotel made by a guest through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a petition to the hotel made by a guest'. Jentic returns the matching Abitari Housekeeping Integration API for Guest Facing 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 for Guest Facing have?

The Abitari Housekeeping Integration API for Guest Facing exposes 6 endpoints covering messaging, setup operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Abitari operations and credentials the agent may use, and this API sends its targets in the request body rather than scoping to a single record, so you control access at the operation level. You might allow only creating a guest petition and connecting the integration while withholding webhook operations, or permit subscribing and changing a webhook URL without granting the DELETE that removes a webhook. The agent can call only the operations you have explicitly enabled, and the encrypted OAuth2 credential is injected at execution time without entering the agent context.