Skip to main content
GET
/
openapi
/
v1
/
fx
/
em-stress
Emerging-market FX stress
curl --request GET \
  --url https://api.hayinsights.com/openapi/v1/fx/em-stress \
  --header 'X-API-Key: <api-key>'
{
  "success": true,
  "statusCode": 200,
  "data": {
    "asOf": "2026-05-14",
    "pairs": [
      {
        "pair": "USD/CNY",
        "latestPrice": 6.79,
        "vol30d": 1.42,
        "vol90dMean": 2.39,
        "vol90dSd": 0.63,
        "zScore": -1.52,
        "priceZScore": -2,
        "level": "WARNING",
        "sampleN": 90
      },
      {
        "pair": "USD/IDR",
        "latestPrice": 17500.9,
        "vol30d": 3.95,
        "vol90dMean": 3.56,
        "vol90dSd": 0.37,
        "zScore": 1.02,
        "priceZScore": 2.49,
        "level": "WARNING",
        "sampleN": 90
      }
    ]
  },
  "meta": {
    "timestamp": "2026-06-19T08:50:42.383Z"
  }
}

Authorizations

​
X-API-Key
string
header
required

Your HayInsights API key (prefixed apk_). Create and manage keys in the HayInsights dashboard (Account → API keys).

Send it in the X-API-Key header on every request to /openapi/v1/*. Which data domains you may access and your request quota are both governed by the subscription plan attached to the key — see the Plans & features and Rate limits guides.

Response

Emerging-market FX stress readings.

Standard success envelope shared by every endpoint. Each operation's response wrapper extends this (via allOf) and adds a typed data property.

​
success
boolean
required

Always true for a successful response.

Example:

true

​
statusCode
integer
required

Mirrors the HTTP status code.

Example:

200

​
data
object
required

Emerging-market FX stress monitor — one entry per tracked currency pair.

​
meta
object

Response metadata. Always present; timestamp is the server time the response was generated.