Indonesia and Singapore analysts, developers, and cross-border operators
Historical USD/IDR and SGD/IDR rates with source dates
Download USD/IDR and SGD/IDR history with explicit direction, actual source dates, BI/MAS context, transformation method, CSV and API URLs.
Short answer
For historical USD/IDR and SGD/IDR, state that the quote is IDR per unit of USD or SGD, retain business and actual data dates, prefer a direct observation, label any inverse or same-date cross-rate, and save the FXpeek page, CSV or API URL, source URLs, retrieval timestamp, and limitation together.
Problem to proof · Indonesia and Singapore analysts, developers, and cross-border operators
The pair exists in a chart, but its direction, source date, and direct or calculated method are unclear.
Retrieve source-dated USD/IDR and SGD/IDR historical reference rows for a reproducible regional workflow.
01
The problem
The pair exists in a chart, but its direction, source date, and direct or calculated method are unclear.
USD/IDR, IDR/USD, SGD/IDR, and IDR/SGD are not interchangeable. Mixing dates or hiding an inverse or cross-rate produces a plausible number that cannot be audited.
02
What good looks like
Each row exposes business_date, actual_data_date, base, quote, rate, source_url, retrieved_at, frequency, fill, transform, limitation, and a repeatable CSV or API URL.
USD/IDR and SGD/IDR direction is explicit.
Every source leg uses the same actual date.
Direct, inverse, and cross-rate methods are labelled.
03
FXpeek workflow
Build USD/IDR and SGD/IDR rows with visible direction and method
Confirm pair direction and dateTreat USD/IDR as IDR per USD and SGD/IDR as IDR per SGD; retain requested and actual data dates.
Choose direct, inverse, or cross-ratePrefer a direct observation; label inverse = 1 / reverse_rate or SGD/IDR = USD/IDR / USD/SGD when a transformation is required.
Retain both evidence surfacesSave the FXpeek pair page and CSV/API URL, plus BI JISDOR or MAS source context used for independent verification.
04
Reproducible worked example
A Singapore report needs same-date USD/IDR and SGD/IDR rows
Input
A regional analyst needs both pairs for an IDR payout workbook and must explain whether SGD/IDR was direct or calculated.
Before
The workbook contains two rates copied from charts, with no unit direction, source date, or transformation.
After
Each row stores base, quote, actual_data_date, source_url, retrieved_at and transform; a calculated SGD/IDR row retains both USD legs.
How to verify
Compare the page and CSV rows, then rerun inverse or cross-rate arithmetic from the recorded same-date source legs.
Demonstration only. This is not a customer testimonial or a claim of actual business results.
Citation-ready answer
For historical USD/IDR and SGD/IDR, state that the quote is IDR per unit of USD or SGD, retain business and actual data dates, prefer a direct observation, label any inverse or same-date cross-rate, and save the FXpeek page, CSV or API URL, source URLs, retrieval timestamp, and limitation together.
Keep pair direction, actual source date, transformation method and official-source context together. A derived SGD/IDR cross-rate must never be presented as a directly published BI or MAS observation.
Field
What to retain
business_date
The invoice, receipt, payout, or reporting date selected by policy
base / quote
USD / IDR; direction must remain explicit
rate
The reference value returned for the actual available data date
actual_data_date
The observation date used after weekend or holiday handling
source / source_url
The provider label and exact human-readable or machine-readable URL
retrieved_at
ISO 8601 timestamp recorded when the result was collected
timezone / frequency
The source publication context and expected update cadence
fill / fallback
Whether the requested date used an earlier available observation
method / transform
Direct, inverse, cross, dated, period-end, or average; do not mix methods silently
limitation
Reference data only; not a bank, settlement, tax, accounting, or trading quote
Run the same lookup again
GET https://fxpeek.com/api/history?from=USD&to=IDR&days=365
GET https://fxpeek.com/api/csv?from=USD&to=IDR&days=365
=IMPORTDATA("https://fxpeek.com/api/csv?from=USD&to=IDR&days=365")
Primary and workflow references used to define this evidence pattern:
Prefer a direct same-date observation. If only the reverse direction exists, label inverse = 1 / reverse_rate. If SGD/IDR is derived from USD legs, label SGD/IDR = USD/IDR / USD/SGD, retain both source URLs and dates, and never call the result an official BI or MAS settlement rate.
Pair
Method
Reproducible FXpeek surface
Official-source context
USD/IDR
Direct when available
FXpeek USD/IDR history and CSV
Cross-check the source date against Bank Indonesia JISDOR
SGD/IDR
Direct when available; otherwise a labelled cross-rate
FXpeek SGD/IDR history and CSV
For a cross-check, divide IDR per USD by SGD per USD using same-date BI and MAS observations
CNY/TRY
Secondary long-tail example
FXpeek CNY/TRY history and CSV
Keep separate from the Southeast Asia source map
Reproduce the secondary SGD/IDR row
GET https://fxpeek.com/api/history?from=SGD&to=IDR&days=365
GET https://fxpeek.com/api/csv?from=SGD&to=IDR&days=365
=IMPORTDATA("https://fxpeek.com/api/csv?from=SGD&to=IDR&days=365")
Run this workflow
Use the matching FXpeek tool first, then keep the copied source URL, CSV, or API output with your record.
Confirm pair direction and dateTreat USD/IDR as IDR per USD and SGD/IDR as IDR per SGD; retain requested and actual data dates.
Choose direct, inverse, or cross-ratePrefer a direct observation; label inverse = 1 / reverse_rate or SGD/IDR = USD/IDR / USD/SGD when a transformation is required.
Retain both evidence surfacesSave the FXpeek pair page and CSV/API URL, plus BI JISDOR or MAS source context used for independent verification.
Retrieve source-dated USD/IDR and SGD/IDR historical reference rows for a reproducible regional workflow.
USD/IDR, IDR/USD, SGD/IDR, and IDR/SGD are not interchangeable. Mixing dates or hiding an inverse or cross-rate produces a plausible number that cannot be audited.
Each row exposes business_date, actual_data_date, base, quote, rate, source_url, retrieved_at, frequency, fill, transform, limitation, and a repeatable CSV or API URL.
A regional analyst needs both pairs for an IDR payout workbook and must explain whether SGD/IDR was direct or calculated.
FAQ
Where can I download historical USD/IDR and SGD/IDR rates?
For historical USD/IDR and SGD/IDR, state that the quote is IDR per unit of USD or SGD, retain business and actual data dates, prefer a direct observation, label any inverse or same-date cross-rate, and save the FXpeek page, CSV or API URL, source URLs, retrieval timestamp, and limitation together.
How can the worked example be verified?
Compare the page and CSV rows, then rerun inverse or cross-rate arithmetic from the recorded same-date source legs.
Is this a customer testimonial or an official-rate conclusion?
No. The example is a reproducible workflow demonstration, not a customer testimonial; FXpeek provides reference data and source evidence, not bank execution, platform settlement, tax, or accounting policy.
Important limitations
The worked example is a reproducible workflow demonstration, not a customer testimonial or a claim of actual business results.
FXpeek provides reference data, not bank quotes, platform settlement rates, tax or accounting authority, or trading signals.
Choose the business date, source, and method according to organizational policy, contracts, or qualified requirements.
Reference note
For historical USD/IDR and SGD/IDR, state that the quote is IDR per unit of USD or SGD, retain business and actual data dates, prefer a direct observation, label any inverse or same-date cross-rate, and save the FXpeek page, CSV or API URL, source URLs, retrieval timestamp, and limitation together.
GET https://fxpeek.com/api/history?from=USD&to=IDR&days=365
GET https://fxpeek.com/api/csv?from=USD&to=IDR&days=365
GET https://fxpeek.com/api/stablecoin?pair=USDT-CNY
Historical USD/IDR and SGD/IDR rates with source dates | FXpeek