Booking page configuration: rules, categories, online services, payment mode, approval threshold, required fields, current texts, payability, theme, arrival info, units (Cache-Control public, max-age=60)
curl --request GET \ --url https://example.com/api/public/v1/example/booking/configParameters
Sezione intitolata “Parameters”Path Parameters
Sezione intitolata “Path Parameters”Responses
Sezione intitolata “Responses”OK
object
Marinas.booking_enabled; when false every other field is a default
An online provider with checkout is enabled (or allow_without_provider is set: bookings then go to approval) and the terms and privacy texts are published (without them details are refused with booking_rules consents texts_unpublished)
object
Local time HH:MM in the marina timezone
Local time HH:MM in the marina timezone
Weekdays without arrivals, 0 = Sunday
object
Price_class (M2 berth category), or standard
object
Length in integer centimetres
Length in integer centimetres
object
object
Optional translated text (both languages may be empty)
object
Indicative price per unit (the quote is binding)
Quantity in thousandths (1.5 = 1500)
Percentage in integer basis points (1 % = 100)
Refund of the paid amount when cancelling at least min_days_before days before arrival
object
object
Required documents may be uploaded after payment
Current published version of each text kind
object
Long localised text (booking texts, arrival information); it is the source language
object
object
object
Berthing-master phone (marina contact
Long localised text (booking texts, arrival information); it is the source language
object
Example
{ "services": [ { "unit": "night" } ], "payment_mode": "deposit", "required_fields": { "documents": [ "boating_licence" ] }, "texts": [ { "kind": "terms" } ]}Not found (or not visible to the principal)
object
object
Map validation issues (map_invalid)
object
ValidateMap rule (m1-plan §2.3), e.g. berth_overlap
Numbers only (cm, counts)
object
Price list validation issues (price_list_invalid)
object
Pricing.Validate issue code (m2-plan §4.8), e.g. period_overlap
object
Id of the row, or the client key of an unsaved one
Codes and integers as strings; never personal data
object
Machine-readable details: no_price {item_id, contract_type, night, unit, category, band, reason}; price_list_overlap {conflicts: [{id, code, valid_from, valid_to}]}; in_use {references}; resource_taken ConflictDetail; fit_blocked FitResult; placement_invalid {reason, allocation_id?}; invalid_transition {from, action}; closure_active {closure_id, from_date, to_date}; release_invalid {reason}; allocation_changed {current_resource_id, current_resource_code} (null when the allocation is gone); remote_pin_mismatch {expected_fingerprint, presented_fingerprint}; scenario_conflicts {conflicts: [StorageScenarioConflict]}; maintenance_conflicts {conflicts: [MaintenanceConflict]}; storage_no_space {area_id, from, to}. Ids, codes, dates and integers only.
object
Example
{ "type": "bad_request", "issues": [ { "severity": "error" } ], "price_list_issues": [ { "severity": "error", "ref": { "kind": "list" } } ]}Rate limited (see Retry-After)
object
object
Map validation issues (map_invalid)
object
ValidateMap rule (m1-plan §2.3), e.g. berth_overlap
Numbers only (cm, counts)
object
Price list validation issues (price_list_invalid)
object
Pricing.Validate issue code (m2-plan §4.8), e.g. period_overlap
object
Id of the row, or the client key of an unsaved one
Codes and integers as strings; never personal data
object
Machine-readable details: no_price {item_id, contract_type, night, unit, category, band, reason}; price_list_overlap {conflicts: [{id, code, valid_from, valid_to}]}; in_use {references}; resource_taken ConflictDetail; fit_blocked FitResult; placement_invalid {reason, allocation_id?}; invalid_transition {from, action}; closure_active {closure_id, from_date, to_date}; release_invalid {reason}; allocation_changed {current_resource_id, current_resource_code} (null when the allocation is gone); remote_pin_mismatch {expected_fingerprint, presented_fingerprint}; scenario_conflicts {conflicts: [StorageScenarioConflict]}; maintenance_conflicts {conflicts: [MaintenanceConflict]}; storage_no_space {area_id, from, to}. Ids, codes, dates and integers only.
object
Example
{ "type": "bad_request", "issues": [ { "severity": "error" } ], "price_list_issues": [ { "severity": "error", "ref": { "kind": "list" } } ]}Headers
Sezione intitolata “Headers”Porto è sviluppato da Coste360 SRL. Codice sorgente disponibile con licenza BSL 1.1; il marchio Porto è escluso dalla licenza.