Green fees and currencies
Green fees are represented using a numeric amount and an ISO 4217 currency code.
{
"period": "weekend_holiday",
"amount": 500,
"currency": "DKK",
"value": "500 DKK"
}
Price fields
| Field | Description |
|---|---|
period | Canonical code describing when the price applies |
amount | Numeric amount in the stated currency |
currency | Three-letter ISO currency code |
value | Displayable representation without exchange-rate estimates |
The original currency takes precedence over a converted amount that may have appeared in the source material.
For example, a source value such as DKK 500 (67 EUR) is normalized as:
{
"amount": 500,
"currency": "DKK",
"value": "500 DKK"
}
The EUR equivalence is excluded because currency exchange rates change.
Do not compare different currencies directly
These prices are not directly comparable:
[
{"amount": 65, "currency": "GBP"},
{"amount": 500, "currency": "DKK"},
{"amount": 70, "currency": "EUR"}
]
Applications that need cross-currency comparisons must convert amounts using an exchange-rate provider and clearly state the rate date. The API's original amount and currency should remain available.
Format amounts
Use a locale-aware number formatter:
const label = new Intl.NumberFormat('en-GB', {
style: 'currency',
currency: fee.currency
}).format(fee.amount);
Conditions and periods
A price may depend on weekday, weekend, holiday, time, course, number of holes or player category. Do not select a price using amount alone. Evaluate its associated conditions and canonical period.
Green fees can change. Applications should present them as guidance and encourage users to confirm the current price during booking.