id_site_coinapi
id_site_coinapi - definition
id_site_coinapi is a UUID that identifies the CoinAPI ingestion site (Point of Presence/PoP) where a market-data update was first received and timestamped.
Every quote, trade, or order book update delivered through CoinAPI - whether via REST, WebSocket, FIX, or Flat Files - includes this field. It provides verifiable data lineage, allowing developers and traders to understand where an update entered the CoinAPI infrastructure.
What does id_site_coinapi represent?
It is the immutable UUID of the PoP (data center) that first ingested the update from an exchange.
A PoP is a geographically distributed edge location where CoinAPI maintains:
- direct WebSocket or FIX connections to exchanges
- ultra-low-latency ingest pipelines
- synchronized timestamping
- redundancy and regional failover
Examples of common PoP locations include:
- Equinix NY4 (New York / Secaucus)
- Equinix LD4 (London / Slough)
- Equinix TY8 (Tokyo) …and additional regional ingest sites across North America, Europe, and APAC.
Each PoP has its own UUID, which does not change over time.
Why id_site_coinapi matters
This field allows you to:
1. Measure ingestion latency
By comparing time_exchange (exchange timestamp) and time_coinapi (timestamp at the PoP), you can estimate:
- exchange → PoP network latency
- PoP → client delivery latency
- jitter and route variance over time
2. Reconstruct microstructure accurately
When replaying historical tick data, the PoP origin helps you rebuild:
- queue position
- tick sequencing
- matching-engine behavior analyzed from a specific regional vantage point
3. Perform compliance & audit analysis
Regulated entities often need to demonstrate:
- when data arrived
- where it arrived
- that timestamps reflect authentic market conditions
4. Understand routing behavior
Across global markets, different PoPs may receive updates faster depending on:
- exchange geography
- network paths
- load balancing or failover conditions
id_site_coinapi gives you visibility into that routing.
Can you get the human-readable PoP name?
Yes, but only on request.
For security reasons, CoinAPI does not publish PoP mappings publicly.
However, when required for:
- HFT latency studies
- microstructure research
- regulatory work
- deterministic replay
- audit requirements
CoinAPI can export the mapping:
id_site_coinapi → PoP datacenter name
This can be requested for:
- a specific exchange
- a specific symbol_id
- a defined UTC time window
How id_site_coinapi works in practice
For each event:
- Exchange emits an update
- A PoP receives and timestamps it (time_coinapi)
- id_site_coinapi = UUID of that PoP
- Event is normalized and delivered to you
It is a stable and deterministic identifier — same PoP = same UUID.
How developers use id_site_coinapi
- HFT simulation: model time-sensitive behavior as if the client were physically colocated at NY4/LD4/TY8.
- Latency analytics: compute arrival deltas per PoP and compare across regions.
- Redundancy analysis: detect failovers or path changes (e.g., switching from LD4 to NY4).
- Microstructure replay: ensure order-book reconstruction mimics real exchange behavior.
Things to remember
- id_site_coinapi identifies where CoinAPI first ingested the data.
- It is a UUID, not a human-readable location.
- The UUID → PoP mapping is available on request.
- Each PoP is stable and does not change over time.
- Essential for latency studies, compliance, and HFT-grade microstructure analysis.