To import stock market data into WordPress, connect a stock quote API as a provider in Ingestics, map the symbol, price, and change fields to post fields, and schedule refreshes around market hours. The connection and mapping work on the Free tier; automatic updates start at Lite.

This is the data-feed workflow — a watchlist or quotes dashboard that maintains itself. Here is the full setup.

Which stock data API should you use?

Alpha Vantage, Finnhub, Twelve Data, and Financial Modeling Prep all offer free JSON endpoints with an API key. Two things to check before choosing:

1. Rate limits. Free plans are tight (Alpha Vantage allows 25 requests/day; Finnhub 60/minute). Your fetch schedule must fit the quota.
2. Redistribution terms. Most free plans permit personal or internal dashboards; publishing quotes commercially may need a paid plan. Read the terms for the plan you are on.

Also note the data is typically delayed 15 minutes on free plans — fine for a daily-movers page, not for trading. A quotes page is site content, not investment advice; label it accordingly.

How do you connect the stock API to WordPress?

In Ingestics → Providers, add an API provider. Paste the quote endpoint with your symbols in the query string, choose GET, and set API-key authentication (most stock APIs take the key as a query parameter or header — either works, and Ingestics stores it encrypted).

Open the call preview and confirm the JSON: symbol, current price, change, percent change, previous close. A 401/403 means the key is wrong; an empty response usually means the symbol format is off (some APIs want AAPL, others NASDAQ:AAPL).

How do you map quote fields to WordPress?

Typical mapping for a Finnhub-style response:

• symbol → post title (or part of it: “AAPL Quote”)
• c (current price), d (change), dp (percent change) → content
• Timestamp → content, so readers see how fresh the number is

On Free, JSON-path mapping composes the post directly. Lite’s Post Template Builder formats it into a readable line — “AAPL: $189.40 (+1.2%) as of 16:00 ET” — with placeholders instead of raw values.

Should quotes create new posts or update existing ones?

For a watchlist page you almost always want one post per ticker, updated in place. That is Pro’s Advanced Sync Engine: it matches the existing post by external ID or title and updates it on each fetch, skipping unchanged items. Without it (Free/Lite), each fetch creates new posts — which suits a “daily market close” archive, where duplicate detection prevents same-day re-posts.

How do you fetch multiple tickers efficiently?

Two patterns:

• Batch endpoints. Some APIs return many symbols in one call — one provider, one request, whole watchlist. Cheapest on quota.
• Paginated endpoints. For long lists, Lite’s page/offset pagination walks the result set; Pro adds cursor pagination for APIs that use continuation tokens.

If the API only allows one symbol per request, create one provider per ticker and let Lite’s shared rotation spread the calls across the schedule instead of firing them all at once.

How often should stock data refresh?

Match the schedule to the market, not the clock. A 15–30 minute interval during trading hours covers a watchlist; overnight and weekend fetches are wasted quota. Lite’s cron intervals handle a steady cadence; Pro’s custom scheduling lets you concentrate fetches into market hours.

How do you display the stock dashboard?

Lite unlocks the [auto_api_feed] shortcode, Gutenberg block, and grid layout — a grid of ticker cards works well. Business adds a ticker layout, the classic scrolling strip for a finance site header. Shortcode options are in the documentation.

Which Ingestics tier does this workflow need?

• Free — connect the API, map quotes, manual fetch. Proves the pipeline on 3 providers.
• Lite — scheduled refreshes, pagination, template builder, grid display. The working minimum for a live watchlist.
• Pro — sync-in-place ticker posts, cursor pagination, market-hours custom scheduling.
• Business — ticker layout, rate-limit budget queue for tight API quotas.

The same pattern powers cryptocurrency prices — a 24/7 market with looser data licensing — and the general mechanics are in the REST API import guide. More automated publishing workflows are on the use cases hub.