← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · CALENDAR EVENTS TIMING

Crypto Calendar Event Data: Event Time vs Retrieval Time

Calendar events have a scheduled time, an actual release time and the time you retrieved the data. Revisions add another clock.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

An economic or crypto event has a scheduled time (which can change), an actual release time (sometimes seconds or minutes off), values that may be revised later, and your retrieval time. For studies of market reaction, use the actual release time from the primary source in UTC; store scheduled time separately and record when values were retrieved and whether they were later revised.

Which times the data carries

TimePresent?Meaning
Scheduled timeCalendarCan change
Actual releasePrimary sourceReaction start
Revision timeLaterValues change
Retrieval timeNoRecord it

Review Crypto Calendar Event Data with bar replay before using it live.

Open ChartsPod replay

What to record yourself

Field to storeWhy
scheduled (UTC)Plan
released (UTC)Event
retrieved_atData version
revised?Flag
sourcePrimary/secondary
Calendar Events: a stored recordCalendar Events: a stored record: scheduled (UTC) — Plan; released (UTC) — Event; retrieved_at — Data version; revised? — Flag; source — Primary/secondary.scheduled (UTC)Planreleased (UTC)Eventretrieved_atData versionrevised?FlagsourcePrimary/secondary
Every calendar events row carries its own clock. Original ChartsPod editorial graphic.

Example

Calendar Events: event vs retrieval (illustrative)Calendar Events: event vs retrieval (illustrative): SCHEDULED: 12:30:00 UTC; ACTUAL: 12:30:04; RETRIEVED: 12:31:10; REVISED: Next month.SCHEDULED12:30:00 UTCACTUAL12:30:04RETRIEVED12:31:10REVISEDNext month
Two clocks, one record. Original ChartsPod editorial graphic.

Illustrative: a reaction study aligned price to scheduled times; one event was delayed 15 minutes, placing the 'reaction' window entirely before the release.

Related: Crypto Calendar Event Data: Null vs Zero - Handle Missing Fields Correctly, Order Flow Around CPI Releases in Crypto: What Price Response Adds to the Reading.

An economic or crypto event has a scheduled time (which can change), an actual release time (sometimes seconds or minutes off), values that may be revised later, and your retrieval time. For studies of market reaction, use the actual release time from the primary source in UTC; store scheduled time separately and record when values were retrieved and whether they were later revised.

Put Crypto Calendar Event Data next to price, flow and positioning in one workspace.

Open a ChartsPod workspace

Questions readers ask

Which time should event studies use?

Actual release time, UTC.

Can scheduled times change?

Yes; store both.

Why track revisions?

Values change after release.

Sources and methodology

Field definitions come from DEX Screener's API reference and CoinGecko's onchain API documentation, read 17 October 2026. Where a schema doesn't document a timestamp, this guide says so and recommends recording retrieval time yourself.

  1. ChartsPod: product overview, pricing and FAQ — free terminal, venues, modules, no order placement; checked 17 Oct 2026.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.