Developer API terms and licence.
Edition 22 October 2026. Effective for orders accepting this version from publication. Version fuel-api-terms-2026-10-22.
1. Provider and agreement
FuelWatch Developer API is provided by Alex Santos, trading as FuelWatch.ie, with service address Lodge Road, Westport, Co. Mayo, Ireland. Contact hello@fuelwatch.ie for support, complaints or privacy requests. The service is for a business, profession or public body; by ordering you confirm authority to act for your organization. Mandatory consumer and data-protection rights remain unaffected.
This version applies to orders accepting it from publication. It expressly permits the integration described below, including public applications, despite the general consumer terms’ restrictions on automated access or competing applications. It does not change an existing report purchase or its accepted licence.
2. Included data and permitted use
During a confirmed paid API period, your organization receives a non-exclusive licence to request the eligible Republic of Ireland petrol and diesel observations through the documented endpoint and display them in its own websites, apps and internal tools. Your staff and contractors may process the data for you under your control. Your users may view the displayed prices; they do not receive a licence to operate their own raw data feed.
The endpoint supplies the latest eligible reported price per station and fuel, the report’s Dublin calendar date, permitted station names/counties and qualified coordinates where available. Exact report times are not supplied. Northern Ireland, LPG, heating oil, green diesel, EV charging, historical exports and write access are excluded. A station may have no recent price or eligible coordinates. The current coverage and returned fields define the available feed; it is not a complete Irish forecourt directory.
3. Attribution, open licences and caching
Show “FuelWatch” with a link to fuelwatch.ie and show each price’s report date. Preserve source notices returned by the API. OpenStreetMap-derived station information remains available under ODbL 1.0; credit © OpenStreetMap contributors and retain the licence link. Applicable attribution and share-alike obligations continue to apply. Ask us for the source component or alteration information needed to exercise those rights; we will supply what the applicable open licence requires.
For the FuelWatch-controlled feed, cache responses on your backend for no more than 60 minutes, recalculate report age when displaying cached results, and do not build a historical archive, resell or sublicense a raw feed. Browser/mobile interfaces may receive the individual records needed for your display, but must not expose your API key or become a general data-download service. These restrictions apply only to rights FuelWatch controls and never remove independent rights or impose additional restrictions under an upstream open licence.
When your paid access ends, or affected FuelWatch-controlled data is withdrawn, stop displaying that feed and remove its cached copies within 24 hours, or sooner where a specific rights/security notice requires it. Independently held open-licence rights remain intact.
4. Plans and metering
Starter is €15 per month for 5,000 requests, Growth €29 for 10,000, and Scale €49 for 25,000. Their minute limits are respectively 60, 120 and 240 requests, shared across all your organization’s keys. Fees are in EUR. FuelWatch is not VAT-registered and does not add VAT to these fees. The tax basis of observed fuel prices is a separate response field.
Each admitted station-results page uses one request, including empty pages and repeat requests. Validation, access or source failures before the usage debit do not count; a connection lost after a generated page is debited can still count. Unused units do not roll over. There are no automatic overage charges: requests stop when your allowance is exhausted. Each confirmed paid monthly interval has its own allowance. The limit is 100 stations per page. v1 has no self-service plan changes; contact us to arrange a different plan.
5. Payment and cancellation
Payment starts the monthly subscription and access is granted after server verification. Subscriptions renew monthly until cancelled. A checkout return page is not proof of payment. Cancel in the API billing portal before the next renewal to stop that charge; cancellation takes effect at the paid period’s end. A failed renewal grants no new interval. Keep a current organization owner able to manage billing. If the final owner is removed, API access is restricted and FuelWatch arranges period-end cancellation of future renewal.
A business customer cancelling partway through a correctly supplied period does not ordinarily receive a refund for that elapsed service. This does not affect the remedies below or mandatory cancellation/refund rights. Refunds and payment disputes can restrict the related API period during reconciliation; we review the payment and remedy before restoring applicable access. Unrelated purchases are unaffected.
6. Coverage, freshness and service care
We supply the API with reasonable skill and care using the published scope and checks. Prices are community reports and may have changed at the pump. A snapshot is normally compiled hourly from available reports and expires after two hours; this is not a promise of new reports at every station each hour. meta.snapshot_at records compilation time. reported_date and age_days describe the original observation at day precision. Show these limits clearly and handle unavailable results in your application.
There is no guaranteed station count, coordinate coverage, continuous availability or uptime service level. These limits do not excuse a failure to supply the service as described. A station name describes the captured business listing, not verified historical branding. No station or brand endorses your application merely because its prices appear.
7. Corrections, support and remedies
Report access failures, material errors or a rights concern to hello@fuelwatch.ie, with the affected public station reference or request details, without sending API secrets. We aim to acknowledge complaints within two working days and correct a service failure within ten working days after receiving enough information to investigate. Working days exclude weekends and Irish public holidays; these targets do not extend a shorter legal deadline.
If we cannot supply a usable service matching the agreed scope within that period, you may agree a later correction or receive a refund for the part of the paid service not supplied as agreed. If none of a paid period’s service was supplied, that period is refunded in full. A material or repeated failure allows you to end the affected subscription immediately. A serious uncorrectable issue does not require waiting. Refunds due are issued within 14 calendar days, without a refund fee, ordinarily to the original payment method; credits require your agreement.
We may immediately restrict an affected key, source or interval for abuse, compromised credentials, payment restrictions or a rights/security concern, explain the material restriction and provide the appropriate remedy. Apply notified corrections and removals promptly. We do not retrospectively change your accepted terms or remove independent open-licence rights.
8. Security and privacy
Keep API keys on your backend, share them only with authorized operators and revoke exposed keys promptly. Do not circumvent quotas, use other organizations’ credentials or attempt to identify contributors, reconstruct individual activity or combine the feed for that purpose. The API excludes contributor account details, photos, device positions and exact submission times. This reduces linkage risk; it is not a guarantee that every observation is anonymous.
The privacy policy describes source linkage, API account/key/usage records and rights handling. Required order, invoice and tax records are ordinarily retained for six years, or longer for a specific obligation or unresolved claim. Access/security records are kept only while needed to operate the account, investigate abuse or resolve a case; they are reviewed at least annually. API snapshots are short-lived working copies, not a promised customer archive. We do not store full card details.
9. Responsibility
For business purchases, FuelWatch is responsible for reasonably foreseeable direct loss caused by its breach or failure to exercise reasonable care. Total liability for a claim or connected claims is limited to the greater of €1,000 or the fees paid for the affected product in the preceding 12 months. Indirect or consequential loss is excluded. These limits do not reduce refunds due, or exclude fraud, fraudulent misrepresentation, death/personal injury caused by negligence, or liability that cannot lawfully be limited. Mandatory consumer and data-protection rights remain unaffected.
10. Changes and disputes
The accepted version applies to your order. Material changes for future renewals will be notified at least 30 days before taking effect, with the option to cancel before the first affected charge. Contact us first so we can investigate a complaint. Irish law and the Irish courts apply, subject to mandatory rights to use another court. If a provision is unenforceable, the remaining terms continue so far as the law allows.