Investing APIinvesting.com ↗
Access Investing.com's economic calendar events and government bond yields across 70+ countries. Filter by date, importance, country, and expiry.
What is the Investing API?
This API exposes three endpoints covering two core datasets from Investing.com: upcoming economic calendar events and government bond yield instruments spanning roughly 730 instruments across about 70 countries. The get_economic_events endpoint returns scheduled macro events with importance ratings, forecast, actual, and previous values. The bond endpoints expose both the current yield snapshot and daily historical series across all expiries per country.
curl -X GET 'https://api.parse.bot/scraper/94e4f0a4-20b9-4cde-8307-8fc5cfe90588/get_economic_events?end_date=2026-10-17&start_date=2026-10-14' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns a list of upcoming economic events from the Investing.com economic calendar. Each event includes the scheduled date/time (UTC), country, currency, event name, importance level, and actual/forecast/previous values when available. Events are returned in chronological order. By default returns events for the next 7 days starting from today. The API fetches up to 200 events per internal request and paginates automatically. When the importance filter is set, it fetches multiple pages to find matching events. The limit parameter caps the total number of returned events (max 500).
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of events to return. Clamped to range 1-500. |
| end_date | string | End date in ISO format YYYY-MM-DD (e.g. 2026-09-07). When omitted, defaults to 7 days after start_date. |
| importance | string | Filter events by importance level. When omitted, events of all importance levels are returned. |
| start_date | string | Start date in ISO format YYYY-MM-DD (e.g. 2026-09-01). When omitted, defaults to today (UTC). |
| country_ids | string | Comma-separated list of numeric country IDs to filter by (e.g. 5,4,17 for US, UK, Germany). When omitted, events for all countries are returned. |
{
"type": "object",
"fields": {
"total": "number of events returned in this response",
"events": "array of economic event objects, each containing occurrence_id, event_id, date_time, country, currency, event_name, importance, actual, forecast, previous, preliminary, reference_period, unit, category, and source",
"has_more": "boolean indicating whether more events exist beyond this response"
},
"sample": {
"data": {
"total": 2,
"events": [
{
"unit": "%",
"actual": null,
"source": "Eurostat",
"country": "Euro Zone",
"category": "inflation",
"currency": "EUR",
"event_id": 68,
"forecast": 3.3,
"previous": 2.9,
"date_time": "2026-09-01T09:00:00Z",
"event_name": "CPI (YoY)",
"importance": "high",
"preliminary": true,
"occurrence_id": 555262,
"reference_period": "Aug"
},
{
"unit": null,
"actual": null,
"source": "Institute for Supply Management",
"country": "United States",
"category": "economic_activity",
"currency": "USD",
"event_id": 173,
"forecast": 55.2,
"previous": 55.6,
"date_time": "2026-09-01T14:00:00Z",
"event_name": "ISM Manufacturing PMI",
"importance": "high",
"preliminary": false,
"occurrence_id": 555288,
"reference_period": "Aug"
}
],
"has_more": true
},
"status": "success"
}
}About the Investing API
Economic Calendar Events
The get_economic_events endpoint returns upcoming events from Investing.com's economic calendar in chronological order. Each event object includes occurrence_id, event_id, date_time (UTC), country, currency, event_name, importance, and the actual, forecast, and previous values when they are available. You can filter results with start_date and end_date (ISO YYYY-MM-DD), importance level, and a comma-separated country_ids list (e.g. 5,4,17 for US, UK, Germany). The limit parameter caps results at 500 per call; the has_more boolean in the response tells you whether additional events exist beyond the current window.
Bond Instruments Snapshot
The list_bond_instruments endpoint lists every government bond yield instrument Investing.com publishes on its World Government Bonds page — approximately 730 instruments across around 70 countries. Each record includes bond_id, country, name, expiry (normalized codes such as 1M, 2Y, 10Y, 30Y, or null), last_yield, previous close, day high/low, change, and the UTC timestamp of the last quote. You can filter by country (case-insensitive). The response also returns a sorted countries array for reference when constructing calls to the history endpoint.
Bond Yield History
The get_bond_yield_history endpoint accepts a required country string (matched against list_bond_instruments.countries) and fans out across all of that country's listed expiries to return a daily historical yield series. The United States currently has 13 instruments ranging from 1-month to 30-year; Switzerland has around 20 including overnight. You can restrict to specific maturities using the expiries parameter (e.g. 2Y,10Y,30Y). Date range is controlled by start_date and end_date; when omitted the window defaults to the 30 days ending today. The response includes a coverage object showing how many instruments were requested, succeeded, and failed, plus a failures array with bond_id, name, status_code, and snippet for any instruments that could not be retrieved. Each element of instruments contains bond_id, name, expiry, row_count, and a rows array of {date, yield} objects.
The Investing API is a managed, monitored endpoint for investing.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when investing.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official investing.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a macro event calendar that highlights high-importance events filtered by
country_idsandimportancefor a specific trading session. - Backtest fixed-income strategies using daily historical yield series from
get_bond_yield_historyfor specific expiries like2Yand10Y. - Monitor yield curve shape by pulling all expiries for a country from
list_bond_instrumentsand comparinglast_yieldacross maturities. - Alert on scheduled central-bank-related events by filtering
get_economic_eventsforimportance= high and specificcountry_ids. - Compare government bond spreads across countries using
list_bond_instrumentsfiltered to a consistent expiry such as10Y. - Track forecast vs. actual divergence for economic releases by storing
forecastandactualfields fromget_economic_eventsover time. - Reconstruct historical yield curves for academic or risk modeling by requesting multi-expiry history via
get_bond_yield_historywith a wide date range.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Investing.com have an official developer API?+
How does the `get_economic_events` endpoint handle events where actual values are not yet published?+
actual field is included in the event object but will be null or absent until Investing.com publishes the result. The forecast and previous fields follow the same pattern — they appear when the source carries them and are absent otherwise. You can poll the endpoint after a release time to pick up the updated actual value.What is the coverage of `get_bond_yield_history`, and how far back does history go?+
coverage object in the response reports exactly how many instruments succeeded or failed for a given request.Does the API return intraday bond yield data or tick-level economic event updates?+
get_bond_yield_history is daily-grain (rows contain one entry per date). The list_bond_instruments snapshot reflects the latest quoted yield at the time of the call but is not a streaming or tick feed. You can fork this API on Parse and revise it to add intraday or tick-level endpoints if the source exposes that data.