Complete Reservation
This API allows your application to complete a specific reservation. By providing the reservation's unique ID and a note for the completing reservation.
Endpoint
POST https://demo-api.frontpayment.no/api/v1/connect/reservations/complete/{{RESERVATION_UUID}}
Authorization
To access this endpoint, includeInclude a Bearer Token
in the Authorization
header of your request.header. You can obtain this token from Frontpayment.Front Payment.
ExampleExample:
Authorization: Bearer YOUR_FRONTPAID_BEARER_TOKENYOUR_FRONTPAYMENT_BEARER_TOKEN
Request Payload
Send the following parameters as a JSON object in the request body:
{
"note": "Test Complete Note"
}
Validation Rules
Make sure your request meets the following requirements:
Field | Type | Description |
---|---|---|
note |
string |
Required Reservation completing note. |
Response
A successful request will return a 202
status with the following JSON payload:
{
"status_code": 202,
"status_message": "OK",
"message": "reservationCompletedSuccessfully",
"is_data": false,
"data": null
}
API returns a 404
error, it means requested order with RESERVATION_UUID
could not be found in our system.
{
"status_code": 404,
"status_message": "Not Found",
"message": "reservationNotFound",
"is_data": false,
"data": null
}
API returns a 417
error, it means requested payload is not valid.
{
"status_code": 417,
"status_message": "Client Error",
"message": "payloadValidationErrors",
"is_error": true,
"errors": "Array"
}
API return a 400
error, it means your requested reservation status is in SENT
, RESERVED NOT PAID
or EXPIRED
.
{
"status_code": 400,
"status_message": "Conflict of Business Logic",
"message": "prerequisiteFailedToCompleteReservation",
"is_data": false,
"data": null
}
API returns a 510
error, it means something failed on the server side
{
"status_code": 510,
"status_message": "Execution Exception Occurred",
"message": "Something Went Wrong",
"is_error": true,
"errors": "Array"
}