canonical: https://jentic.com/apis/swaggerhub.telkomdev-reva/baleku---reservation-service

# Telkomdev Reva BALEKU - Reservation Service

API Endpoint untuk backend Reservation Service di website BALEKU. The API exposes 17 endpoints.

## For AI agents

Programmatically get kode booking, insert reservasi. Covers 17 operations.

## Scope

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

## Capabilities

- get kode booking
- insert reservasi
- update reservasi
- reservasi founded
- delete reservasi

## Use cases

### E-Commerce Operations

Use the BALEKU - Reservation Service to perform e commerce operations programmatically. The API provides 17 endpoints covering core functionality including get kode booking, insert reservasi, update reservasi.

Example prompt: Call GET /getBookingId to get kode booking

### Automated Avaibility Management

Automate avaibility operations by combining multiple BALEKU - Reservation Service endpoints. Agents can insert reservasi and then update reservasi in a single workflow.

Example prompt: Call POST /reservasi to insert reservasi, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call BALEKU - Reservation Service 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 'get kode booking', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/getBookingId` | get kode booking |
| POST | `/reservasi` | insert reservasi |
| PUT | `/reservasi/1809040031` | update reservasi |
| GET | `/reservasi/1809050002` | reservasi founded |
| DELETE | `/reservasi/1809060003` | delete reservasi |
| GET | `/reservasiOrder` | reservasi order |
| POST | `/reservasiRoom` | reservasi room |
| GET | `/reservasifilter/18` | ?date1=2018-09-01&date2=2018-09-20&chanel=1&tanggal=1&keyword=18&page=1&limit=10 |

## Key resources

- **Avaibility** — Operations for avaibility
- **File** — Operations for file
- **Getbookingid** — Operations for getBookingId
- **Reservasi** — Operations for reservasi
- **Reservasiorder** — Operations for reservasiOrder

## Why Jentic

- **Setup:** Wiring the BALEKU Reservation Service by hand means standing up its base path, mapping the reservation endpoints, and handling calls and retries yourself. Through Jentic you install once, import BALEKU Reservation Service from the API Directory, and your agent calls it.
- **Permission scoping:** The BALEKU Reservation Service takes most of its targets in the request body, so scope the agent to the operations it needs, such as getting a booking id or creating a reservation. You choose which operations it may call, so anything you leave out stays unavailable to the agent.
- **Credential handling:** This API is configured without a credential, so there is no secret for the agent to expose; if a credential is added later it is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get a booking code' or 'create a reservation', and Jentic returns the matching BALEKU Reservation Service 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 BALEKU - Reservation Service use?

The BALEKU - Reservation Service 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 get kode booking with the BALEKU - Reservation Service?

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

### What are the rate limits for the BALEKU - Reservation Service?

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 get kode booking through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get kode booking'. Jentic returns the matching BALEKU - Reservation Service operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the BALEKU - Reservation Service have?

The BALEKU - Reservation Service exposes 17 endpoints covering avaibility, file, getbookingid operations.

### Can I limit what my agent is allowed to do with the BALEKU Reservation Service?

Yes. Because you run Jentic One yourself, you decide which BALEKU Reservation Service operations the agent may call, and anything you leave out stays unavailable to it. For example, you can allow it to get a booking id with GET /getBookingId while blocking POST /reservasi, or permit creating reservations without granting the ability to delete them. Since this API takes most of its targets in the request body, your rules govern exactly which endpoints and credentials the agent is permitted to use.