5.2 - Return Structure¶
{
"StatusCode": 200,
"Status": "ESUCC or EFAIL",
"Message": "Request OK. ",
"Debug": null,
"Result": {}
}
Example¶
{
"StatusCode": 200,
"Status": "ESUCC",
"Message": "Request OK. Request OK. {0}",
"Debug": null,
"Result": {
"start_date": "2022-12-31",
"end_date": "2022-12-31",
"data": [
{
"country_code": "AUT",
"country_name": "Austria",
"indicator_name": "Real interest rate (%)",
"date": "2022-12-31 00:00:00",
"period": "Annual",
"value": 0.0
},
{
"country_code": "AUT",
"country_name": "Austria",
"indicator_name": "Population, total",
"date": "2022-12-31 00:00:00",
"period": "Annual",
"value": 9042530.0
}
]
}
}
On Failure¶
{
"StatusCode": 401,
"Status": "EFAIL",
"Message": "Invalid Timestamp or Request too old.",
"Debug": null,
"Result": null
}
Note (checked against the API on 2026-11-11)¶
Today this operation is served at https://api.infotrie.com/api/idata/get_macro_economic_indicators, with your InfoTrie API key in the X-API-Key header; the legacy AppKey header is refused with a 401. The same data, without the envelope, is at https://api.infotrie.com/api/market_data/get_macro_economic_indicators.
On success the envelope is StatusCode 200, Status ESUCC, Message always Request OK. Request OK. {0}, Debug null, and Result the data. An error raised by the operation (a missing, unknown or malformed parameter: 400) comes in the same envelope, with Status EFAIL, Message Request Failed. followed by the reason, and Result null. A request refused before it reaches the operation (no or an invalid API key: 401; a key without the operation's scope: 403; over the rate limit: 429) gets {"status": "error", "message": "..."} instead of the envelope. There is no timestamp check: the 401 under On Failure is no longer sent.
start_date is the start actually used: coverage begins on 2018-01-01, and a window reaching further back starts there. Observations come in no set order.