Manual Reservation Entry
The Manual Reservation Entry endpoint allows merchants to manually register a reservation and schedule a future payment through the Autocore API.
Endpoint
POST https://[base_url]/v2/bookings/manual-entry
Request Body
The request body is composed of two main objects:
order: Reservation and payment scheduling information.card_item: Encrypted card information.
Order Object
| PARAMETER | TYPE | REQ. | DESCRIPTION |
|---|---|---|---|
| reservation_id | String | No | Merchant reservation identifier. If omitted, one will be generated automatically. |
| hotel_id | Integer | Yes | Hotel identifier where the reservation belongs. |
| first_name | String | Yes | Guest first name. |
| last_name | String | Yes | Guest last name. |
| total_amount | Number | Yes | Total reservation amount to be charged. |
| no_show_amount | Number | No | Amount to charge in case of no-show. |
| tax_percent | Float | No | Tax percentage expressed as a decimal value between 0 and 1. Default: 0. |
| service_percent | Float | No | Service fee percentage expressed as a decimal value between 0 and 1. Default: 0. |
| currency_code | String | No | ISO 4217 currency code. Default: COP. |
| country | String | No | Guest country. |
| installments | Integer | No | Number of installments. Default: 1. |
| charge_date | String | Yes | Scheduled payment date (YYYY-MM-DD). |
| checkin | String | No | Reservation check-in date (YYYY-MM-DD). |
| checkout | String | No | Reservation check-out date (YYYY-MM-DD). |
| String | No | Guest email address. | |
| phone_number | String | No | Guest phone number. |
| notes | String | No | Internal notes associated with the reservation. |
| manual_payment_required | Boolean | No | Indicates that payment will be collected manually instead of automatically. Default: false. |
| requires_checkin_before_payment | Boolean | No | Indicates that payment should only be attempted after guest check-in. Default: false. |
Card Item Object
| PARAMETER | TYPE | REQ. | DESCRIPTION |
|---|---|---|---|
| cc_holder | String | Yes* | Encrypted cardholder name. |
| cc_number | String | Yes* | Encrypted card number. |
| cc_expire_month | String | Yes* | Encrypted expiration month (MM). |
| cc_expire_year | String | Yes* | Encrypted expiration year (YYYY). |
| cc_code | String | Yes* | Encrypted card verification code (CVV). |
For details about the encryption process, refer to the Security on Sensitive Data documentation.
Request Example
{
"order": {
"reservation_id": "RES-10001",
"hotel_id": 17,
"first_name": "Juan",
"last_name": "Perez",
"total_amount": 350000,
"no_show_amount": 100000,
"tax_percent": 0.19,
"service_percent": 0.10,
"currency_code": "COP",
"country": "CO",
"installments": 1,
"charge_date": "2026-07-15",
"checkin": "2026-07-20",
"checkout": "2026-07-22",
"email": "[email protected]",
"phone_number": "+573001112233",
"notes": "Manual reservation created by front desk.",
"manual_payment_required": false,
"requires_checkin_before_payment": true
},
"card_item": {
"cc_holder": "<encrypted_value>",
"cc_number": "<encrypted_value>",
"cc_expire_month": "<encrypted_value>",
"cc_expire_year": "<encrypted_value>",
"cc_code": "<encrypted_value>"
}
}
Response Examples
Reservation Scheduled Successfully
{
"msg": "Proceso concluido satisfactoriamente",
"data": {
"id": 14316,
"reservation_id": "j0cdro952q68",
"crs_id": "MANUAL-j0cdro952q68",
"hotel_id": 17,
"payment_status": "Pendiente",
"apply_charge_at": "2026-07-15",
"total": 350000.0,
"currency_code": "COP",
"created_manually": true
}
}
Validation Error
{
"code": 0,
"message": "Error http: 400",
"detail": "Se requieren los datos de pago para continuar con la programación de la reserva.",
"extra_info": {
"details": {
"error": "Tokenización rechazada, error no especificado."
}
}
}
Common Error Responses
In addition to the validation errors shown above, this endpoint may also return the standard Autocore API error responses (401, 403, 404, 409, 422, 429 and 500) as documented in the General Error Responses section.
Notes
charge_datedetermines when the automatic payment process will attempt to collect the payment.- When
requires_checkin_before_paymentis enabled, the scheduled payment will only be attempted after the guest has checked in.