Operational time and sessions
Latin America spans multiple countries, currencies and time zones. Name the actual deployment cities and avoid assuming that São Paulo and Mexico City share one local trading or support schedule.
Market data · deployment planning
Market Data for Brokers in Latin America
Plan a market-data deployment for Latin America around the actual source, hosting route, instrument calendars and consumer requirements.
Regional acceptance checks
Use separate calendars for each selected instrument and validate the handling of local-currency labels. Test incident handover and archive date boundaries across the chosen locations; region-wide latency or coverage is not implied.
Requirements to confirm
- Deployment city and hosting environment
- IANA zones: America/Sao_Paulo and America/Mexico_City
- Per-instrument holiday calendars
- Measured route and incident ownership
Bring the proposed instrument list, source documentation and consumer workflow to a technical discussion. The agreed integration specification defines coverage, fields, usage permissions and acceptance tests.
Integration brief
A practical deployment brief for Latin America
| Operating location | Identify the actual hosting city and consumer location before selecting the delivery route. |
|---|---|
| Time zones | America/Sao_Paulo and America/Mexico_City. Preserve source and archive timestamps in UTC. |
| Instrument calendar | Confirm the source calendar per instrument, including holidays and session breaks. |
| Acceptance evidence | Record the route, test window, clock synchronization and responsibilities for each layer. |
Separate location from instrument policy
Latin America includes many jurisdictions, local clocks and market calendars. Define the countries and cities actually served rather than applying one regional timezone.
What to test
- Test quote timestamps, language-independent symbol identifiers and source session boundaries for each deployment. Source rights and commercial scope must be checked for the intended consumers, not inferred from the region name.
- Check that incident ownership covers the sessions your consumers use.
- Compare source event time with receive time rather than reporting an unexplained latency number.