Does Google have a currency exchange rate REST API?

Google documents GOOGLEFINANCE as a Google Sheets function. It does not document the Search currency converter or GOOGLEFINANCE as a general production REST API for application backends.

Can Apps Script retrieve historical GOOGLEFINANCE data?

Google states that historical GOOGLEFINANCE data cannot be accessed through the Sheets API or Apps Script. Use a dedicated historical endpoint when code needs a date range.

Should I replace GOOGLEFINANCE in an existing spreadsheet?

Not automatically. Keep it when the workflow stays in Sheets and its limitations are acceptable. Switch when you need backend JSON, documented quotas, history, or explicit source metadata.

Google Currency Exchange Rate API Alternative

Compare GOOGLEFINANCE with a documented exchange-rate API for backend JSON, quotas, history, source data, and observation times.

exchangerate.devSep 20, 20266 min read

Use GOOGLEFINANCE when the answer belongs in a spreadsheet cell. Use a dedicated exchange-rate API when your application needs JSON, documented quotas, historical ranges, or source and observation fields.

Key points

Google documents GOOGLEFINANCE as a Google Sheets function, not a backend REST API.

Search converter results are a consumer interface, not a supported application contract.

A dedicated API gives your backend JSON, authentication, quotas, errors, and observation metadata.

Keep GOOGLEFINANCE for spreadsheet-native workflows where its documented limits are acceptable.

What Google offers for currency conversion

Google Search can display a currency converter, and Google Sheets provides the documented GOOGLEFINANCE function. The Sheets function is convenient for a person working in a spreadsheet, but Google notes that quotes may be delayed and that historical GOOGLEFINANCE data cannot be downloaded through the Sheets API or Apps Script.

google sheets · currency formula

=GOOGLEFINANCE("CURRENCY:USDEUR")

Why an application backend needs a different contract

A production backend needs a documented URL, response schema, authentication method, request limits, error behavior, and a stable way to determine when the underlying rate was observed. A search result or spreadsheet formula does not provide that server contract.

NeedGOOGLEFINANCEExchange-rate API

Spreadsheet cellGood fitPossible but unnecessary

Backend JSON responseNot documented as a REST APINative JSON contract

Historical date rangeRestricted outside the sheetRange endpoint

Source and freshness fieldsLimited quote metadatasource, market_session, data_updated_at

Use a JSON exchange-rate endpoint instead

The first request can be made without a key. The server receives a documented JSON response rather than scraping a search page or trying to automate a spreadsheet.

curl · latest USD to EUR rate

curl "https://api.exchangerate.dev/v1/latest/USD?symbols=EUR"

For a past date, start with the historical exchange-rate lookup. It is a quicker way to check the result and see the API request you can use in your backend.

When GOOGLEFINANCE is still the right choice

Keep using GOOGLEFINANCE when the workflow is intentionally spreadsheet-native, a person can inspect the result, and the documented quote delay and historical restrictions are acceptable. A dedicated API is useful when the value must leave the sheet, drive application behavior, or carry audit-friendly source metadata.

Do not scrape the Search converter

A visible result in Google Search is not permission or a stable interface for automated retrieval. Use a documented function or API instead.

exchangerate.dev

Practical integration guides for developers working with currency data.

What Google offers for currency conversion

Why an application backend needs a different contract

Use a JSON exchange-rate endpoint instead

When GOOGLEFINANCE is still the right choice

Keep reading