> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Silbeck as a data source
> Bring data from Silbeck hotel PMS to Nekt.
Silbeck is a Brazilian Property Management System (PMS) for hotels, providing comprehensive management of reservations, occupancy, guest registration, billing, and operations. With over 30 years in the hospitality market, Silbeck offers a REST API for integration with external systems.
## Configuring Silbeck as a Source
In the [Sources](https://app.nekt.ai/sources) tab, click on the "Add source" button located on the top right of your screen. Then, select the Silbeck option from the list of connectors.
Click **Next** and you'll be prompted to add your access.
### 1. Add account access
You'll need the JWT credentials provided by Silbeck to connect your hotel's PMS data. The following configurations are required:
* **Client ID**: The JWT Client ID provided by Silbeck for API authentication.
* **Client Secret**: The JWT Client Secret provided by Silbeck for API authentication.
* **API URL**: The base URL for your Silbeck API instance (e.g., `http://cloud.silbeck.com.br:30503/datasnap/rest`). This URL is specific to your hotel's deployment.
* **Start Date**: The earliest date from which records will be synced for date-range based streams (reservations, stays, occupancy, etc.).
Once you're done, click **Next**.
### 2. Select streams
Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Select the streams and click **Next**.
### 3. Configure data streams
Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table and the type of sync.
* **Layer**: choose between the existing layers on your catalog.
* **Folder**: a folder can be created inside the selected layer to group all tables.
* **Table name**: we suggest a name, but feel free to customize it.
* **Sync Type**: choose between INCREMENTAL and FULL\_TABLE.
Once you are done configuring, click **Next**.
### 4. Configure data source
Describe your data source for easy identification within your organization, not exceeding 140 characters.
To define your [Trigger](https://docs.nekt.com/runs/scheduling-and-triggers), consider how often you want data to be extracted from this source.
Once you are ready, click **Next** to finalize the setup.
### 5. Check your new source
You can view your new source on the [Sources](https://app.nekt.ai/sources) page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your [Catalog](https://app.nekt.ai/catalog), you need at least one successful source run.
# Streams and Fields
Below you'll find all available data streams from Silbeck and their corresponding fields:
Registry of all rooms/apartments in the hotel.
**Fields:**
* `id` - Unique identifier for the room
* `codigo` - Room code/number
* `codigoTipoApartamento` - Room type code
Room type categories with capacity information.
**Fields:**
* `id` - Unique identifier for the room type
* `codigo` - Room type code
* `nome` - Room type name
* `quantidade` - Number of rooms of this type
* `maximoOcupantes` - Maximum occupancy
Products available in the hotel (minibar, services, etc.).
**Fields:**
* `id` - Unique identifier
* `codigo` - Product code
* `nome` - Product name
Supplies and inputs used by the hotel.
**Fields:**
* `id` - Unique identifier
* `codigo` - Supply code
* `nome` - Supply name
Hotel departments/sectors.
**Fields:**
* `id` - Unique identifier
* `codigo` - Department code
* `nome` - Department name
Available meal plan types (e.g., all-inclusive, half-board).
**Fields:**
* `id` - Unique identifier
* `codigo` - Meal plan code
* `nome` - Meal plan name
Guest categories (adult paying, adult complimentary, child paying, child complimentary).
**Fields:**
* `id` - Unique identifier
* `nome` - Category name
* `tipo` - Category type (1=Adult Paying, 2=Adult Complimentary, 3=Child Paying, 4=Child Complimentary)
Cities registry.
**Fields:**
* `id` - Unique identifier
* `nome` - City name
* `estado` - State/province code
Professions/occupations registry.
**Fields:**
* `id` - Unique identifier
* `nome` - Profession name
Corporate accounts and companies. Paginated at 250 records per page.
**Fields:**
* `id` - Unique identifier
* `codigo` - Company code
* `nome` - Company name
* `dataNascimento` - Registration date
* `telefone` - Phone number
* `celular` - Mobile phone
* `email` - Email address
* `cidade` - City
* `cep` - Postal code
* `bairro` - Neighborhood
* `estado` - State
* `pais` - Country
* `sexo` - Gender
* `documento` - Document number
* `tipoPessoa` - Person type
Supplier records. Paginated at 250 records per page.
**Fields:**
* `id` - Unique identifier
* `codigo` - Supplier code
* `nome` - Supplier name
* `dataNascimento` - Registration date
* `telefone` - Phone number
* `celular` - Mobile phone
* `email` - Email address
* `cidade` - City
* `cep` - Postal code
* `bairro` - Neighborhood
* `estado` - State
* `pais` - Country
* `sexo` - Gender
* `documento` - Document number
* `tipoPessoa` - Person type
Guest records. Paginated at 250 records per page.
**Fields:**
* `id` - Unique identifier
* `codigo` - Guest code
* `nome` - Guest name
* `dataNascimento` - Date of birth
* `telefone` - Phone number
* `celular` - Mobile phone
* `email` - Email address
* `cidade` - City
* `cep` - Postal code
* `bairro` - Neighborhood
* `estado` - State
* `pais` - Country
* `sexo` - Gender
* `documento` - Document number
* `tipoPessoa` - Person type
Hotel occupancy data by date, including guest count (PAX) and room (APTO) metrics with average daily rate.
**Fields:**
* `data` - Date
* `pax_diaAnterior` - PAX from previous day
* `pax_saida` - PAX departures
* `pax_entrada` - PAX arrivals
* `pax_total` - Total PAX
* `pax_percentual` - PAX occupancy percentage
* `pax_diariaMedia` - PAX average daily rate
* `apto_diaAnterior` - Rooms from previous day
* `apto_saida` - Room departures
* `apto_entrada` - Room arrivals
* `apto_total` - Total rooms occupied
* `apto_percentual` - Room occupancy percentage
* `apto_diariaMedia` - Room average daily rate
* `totalDiaria` - Total daily revenue
* `revPar` - Revenue per available room
Room availability by apartment type and date. Shows available, occupied, and maintenance counts per room type per day.
**Fields:**
* `tipo_apto_id` - Room type ID
* `tipo_apto_codigo` - Room type code
* `tipo_apto_nome` - Room type name
* `tipo_apto_qtdeMapa` - Total rooms mapped for this type
* `data` - Date
* `qtdeDisponivel` - Available rooms
* `qtdeOcupado` - Occupied rooms
* `qtdeManutencao` - Rooms under maintenance
Detailed stay/lodging records including guest lists and daily rate breakdowns.
**Key Fields:**
* `id` - Stay ID
* `apartamento` - Room code
* `fechado` - Whether the stay is closed (checked out)
* `dataEntrada` - Check-in date
* `dataSaida` - Check-out date
* `faturamento` - Billing type
* `empresa` - Associated company
* `idReserva` - Related reservation ID
* `nomePortal` - Booking portal name
* `nomeTipoPensao` - Meal plan name
**Nested Arrays:**
* `listaHospede` - List of guests with name, category, contact info, and demographics
* `listaData` - Daily rate breakdown with predicted and actual values
Reservation records with detailed item breakdowns, guest lists, daily rates, totals, advance payments, and extras.
**Key Fields:**
* `id` - Reservation ID
* `dataHora` - Reservation date/time
* `titular` - Primary guest name
* `nomePortal` - Booking portal
* `faturamento` - Billing type
* `empresa` - Associated company
* `email` - Contact email
* `telefone` - Contact phone
* `voucher` - Voucher code
**Nested Arrays:**
* `listaReservaItem` - Reservation items with room details, dates, guests, daily rates, totals, advance payments, and extras
Charges and transactions posted to guest accounts within a date range.
**Fields:**
* `id` - Transaction ID
* `dataHora` - Transaction date/time
* `idProduto` - Product ID
* `codigoProduto` - Product code
* `nomeProduto` - Product name
* `idSetor` - Department ID
* `codigoSetor` - Department code
* `nomeSetor` - Department name
* `quantidade` - Quantity
* `valorUnitario` - Unit price
* `ativo` - Whether the charge is active (not reversed)
* `dataHoraEstorno` - Reversal date/time (if reversed)
Current status of all rooms, including occupancy, maintenance, and cleaning status.
**Fields:**
* `id` - Room ID
* `codigo` - Room code
* `codigoTipoApartamento` - Room type code
* `situacao` - Current status
* `limpeza` - Cleaning status (0=not clean, 1=clean)
* `estadia` - Current stay details (if occupied)
* `manutencao` - Maintenance details (if under maintenance)
Detailed account statement for each occupied room, showing charges by department with individual line items.
**Fields:**
* `apartamento_codigo` - Room code
* `setor_id` - Department ID
* `setor_nome` - Department name
* `setor_idMoeda` - Currency ID
* `setor_simboloMoeda` - Currency symbol
* `setor_valorTotal` - Total for this department
* `lancamento_id` - Charge ID
* `lancamento_idProduto` - Product ID
* `lancamento_codigoProduto` - Product code
* `lancamento_nomeProduto` - Product name
* `lancamento_dataHora` - Charge date/time
* `lancamento_quantidade` - Quantity
* `lancamento_valorUnitario` - Unit price
* `lancamento_valorTotal` - Total amount
* `lancamento_ativo` - Whether the charge is active
* `lancamento_faturado` - Whether the charge is invoiced