Macro Indicators
Live/v1/market/macro-dailyCountry-level macro time series packaged for benchmark and monitoring workflows.
Primary key
geo_object_id
Boundary
Current strongest package is centered on COUNTRY_US.
// API
The public API is designed for integration teams that need stable request contracts, bounded surface definitions, and reference material that stays aligned with the live delivery surface. Teams with a concrete need can apply for a test API key through the contact form, with reviewed scope tied to the documented surface.
Access posture
Managed
Scope model
Package-based
Reference path
Docs-linked
Reference request
Request
GET /v1/market/macro-daily?geo_object_id=COUNTRY_USResponse shape
{
"geo_object_id": "COUNTRY_US",
"series_id": "CPIAUCSL",
"macro_topic": "inflation",
"metric_date": "2026-02-01",
"avg_metric_value": 327.46
}// Access Model
The public API is positioned as a reviewed integration surface. Teams validate product fit, apply for a test API key through the contact form, and build against the published contract rather than undocumented source behavior.
Every public surface is paired with a published contract covering key fields, request shape, and current boundary.
Test API keys are issued through reviewed contact requests so the granted scope matches the intended evaluation workflow.
Teams are expected to integrate against the public reference set rather than infer behavior from undocumented assumptions.
01
Start with Data and Docs to verify the surface, contract key, and current delivery boundary.
02
Teams with a concrete evaluation need can apply through the contact form for reviewed test access.
03
Build against documented fields, request shape, and freshness semantics instead of inferred source behavior.
Access posture
Reviewed test access
Application path
Contact form request
Primary contract key
geo_object_id for region-facing surfaces
Reference path
Data → Docs → Contact form
Best fit
Integration teams, design partners, and customer evaluation workflows that need stable, documented data delivery rather than exploratory raw feeds.
What teams receive
A reviewed test key scope, public reference docs, endpoint families, and delivery boundaries that match the current live surface.
What this is not
This is not instant self-serve signup or an unrestricted bulk source export. It is a documented evaluation surface with reviewed test access.
Authentication
Approved evaluations receive a test API key scoped to the reviewed use case. Authentication details are issued as part of onboarding rather than exposed as anonymous self-serve credentials.
Versioning
Current public paths are versioned under stable endpoint families. Material contract changes are documented in public Docs and release notes before teams are expected to adopt them.
Errors
Integrations should expect standard HTTP request outcomes and treat contract mismatches, missing scope, and boundary assumptions as explicit errors rather than hidden data gaps.
Support path
Access questions, scope review, and early integration support are handled through the contact workflow during evaluation. Teams are expected to review Data and Docs before requesting deeper support.
Program notes
Who should request access
Teams evaluating a real integration, data workflow, or product pilot that depends on stable request contracts and documented delivery boundaries.
What is not available
There is no anonymous signup, unrestricted bulk export, or open raw-feed endpoint. Access is reviewed, scoped, and aligned to the current public delivery surface.
// Endpoint Families
Each endpoint family maps to a public product surface. The endpoint path, contract key, and current boundary are published together so teams can evaluate fit before requesting access.
Authentication is provided through an issued test API key after access review. Header conventions and scope details are supplied during onboarding.
Public endpoints expose documented delivery surfaces rather than unrestricted source archives or bulk historical dumps.
The public reference set is the canonical place to verify field semantics, freshness notes, version expectations, and scope rules before integration.
/v1/market/macro-dailyCountry-level macro time series packaged for benchmark and monitoring workflows.
Primary key
geo_object_id
Boundary
Current strongest package is centered on COUNTRY_US.
/v1/geo/region-facilitiesFacility and point-of-interest outputs normalized to standard geo objects.
Primary key
geo_object_id
Boundary
Strongest on administrative regional lookup and map-ready facility coverage.
/v1/news/regionCurrent regional news feed with explicit freshness and coverage boundaries.
Primary key
geo_object_id
Boundary
Read as a bounded current news surface, not unrestricted global coverage.
/v1/events/region-aggregateRecent event aggregates derived from current regional news updates.
Primary key
geo_object_id
Boundary
Read as a current event surface, not a complete global event archive.
/v1/geo/region-profileSynthesized regional context delivered as a profile surface.
Primary key
geo_object_id
Boundary
Read as contextual output rather than a single-source feed.
// Request Contract
Public access is anchored in the published contract: request key, request shape, field semantics, and current live boundary. Teams should integrate against that reference layer rather than infer behavior from undocumented source assumptions.
For region-facing products, geo_object_id is the primary public contract key. The correct next step is to review the matching docs page before requesting package access.