日本語 / English
CFTC positioning refers to Tuesday. It is published Friday at 15:30 ET. Index a backtest by observation date and the strategy tester reads Friday's number on Tuesday. The result will look good. It is not true.
This feed is ordered by publisher_release_at — the moment the market could first know a number. A source that only keeps observation dates cannot offer this.
| Field | Value |
|---|---|
| Observation date | 2026-08-18 |
| Published | 2026-08-21T15:30:00-04:00 |
| Gap | 3 days |
| Value | -52893 |
Source included, CC BY 4.0. Both versions behave identically.
| File | Platform | Requires | Size |
|---|---|---|---|
| YendollerPanel.mq4 | MT4(MQL4) | Terminal build 600 or later (uses WebRequest, StringSplit, input) | 11,828B |
| YendollerPanel.mq5 | MT5(MQL5) | No constraint | 10,991B |
Flat formats readable with StringSplit alone. MQL has no JSON parser, and asking every user to write one is a bug source.
| File | Contents |
|---|---|
| latest.txt | Current values, KEY=VALUE |
| events.txt | Upcoming scheduled releases (9 entries) |
| cftc.legacy.jpy.noncomm_net.csv | Historical, ordered by release time — 400 rows (value) |
| cftc.tff.jpy.lev_money_net.csv | Historical, ordered by release time — 400 rows (value) |
| drv.gap.jp_us.csv | Historical, ordered by release time — 233 rows (gap2y) |
| drv.hedge_cost.jpy.rate_component.csv | Historical, ordered by release time — 1262 rows (value) |
| drv.theoretical_swap.csv | Historical, ordered by release time — 500 rows (usdjpy) |
| drv.usdjpy.decomposition.csv | Historical, ordered by release time — 120 rows (usdjpy) |
| drv.usdjpy.rv.csv | Historical, ordered by release time — 260 rows (rv20) |
| obs.usdjpy.close.daily.csv | Historical, ordered by release time — 260 rows (value) |
| rate.us.ust.10y.csv | Historical, ordered by release time — 249 rows (value) |
| rate.us.ust.2y.csv | Historical, ordered by release time — 249 rows (value) |
Historical CSVs carry release_epoch, release_utc, value, observation_date, status and record_id. Rows are ordered by release time, not observation date.
Free. No registration, no authentication. Article 38 of our charter commits us to keeping the basic data and API free; a paid tier, if it ever launches, would cover support and uptime guarantees, not the data.
Bug reports: report form (Japanese) or info@yendoller.com. A contact address is optional — you may report without expecting a reply.