How to Import Cryptocurrency Prices into WordPress with Ingestics

A step-by-step guide to turning a live crypto price API into automatically updating WordPress content.

Crypto price trackers, “coin of the day” posts, and portfolio-style content pages are some of the most reliable traffic drivers in the finance niche — but only if the numbers stay current. Manually updating a Bitcoin or Ethereum price post every hour isn’t realistic. This guide walks through connecting a live cryptocurrency price API to WordPress using Ingestics, so new price data flows into your site automatically, with the source correctly attributed.

What You’ll Need

• A WordPress site with Ingestics installed and activated
• The URL of a crypto price API endpoint that returns JSON (many, including CoinGecko’s public markets endpoint, work without an API key; others like CoinMarketCap require a free API key sent as a header)
• A custom post type or your default Posts, depending on whether you want prices mixed with regular content or kept separate

Install and Run the Setup Wizard

After activating Ingestics, open the plugin from the WordPress admin menu. On first launch, the guided Setup Wizard will walk you through enabling API fetching, choosing a starting fetch frequency, and setting your default publish mode. For this use case, set the publish mode to Draft initially — that way you can review the first few imported price posts before trusting the pipeline to publish live automatically.

Add Your Crypto API as a Provider

From the Ingestics dashboard, go to the Providers tab and click Add API Provider. Give it a clear name like “Crypto Prices — Top 10,” paste in your API endpoint URL, and set the HTTP method to GET. If your chosen API requires a key (most crypto APIs offer a free tier with a key), select the appropriate authentication type — API Key or Bearer — and enter it in the Request & Authentication section. Ingestics stores this key encrypted, and masks it in every preview and log entry, so it’s never exposed on screen or in your database in plain text.

Map the Price Fields

Open the JSON mapping section and use the point-and-click JSON Path Selector: run a test call, then click directly on the coin name in the sample response to map it to the post Title, click the price field to map it to your content or a custom field, and click the coin’s logo image URL to map it to the Featured Image. Since most crypto APIs return an array of coins in one response, make sure your “items” mapping points at that array so each coin becomes its own post.

If you want the price itself to be easy to update in place rather than creating a new post every fetch, this is a good moment to think about your publishing strategy — see the “Going Further” section below on live-updating custom post types.

Configure Publishing

In the Publishing Mapping section, choose your post type (a custom “crypto_price” post type is cleaner than mixing prices into your main blog, though the default Post type works fine to start), assign a category like “Cryptocurrency,” and add relevant tags. Ingestics’ free-tier source attribution block will automatically append a “Source: [Your Provider Name] | Read Original” line to each post, which is good practice for financial data transparency.

Preview Before You Fetch

Before running a live fetch, use the Preview tab to load the Planned Call — this shows exactly what request Ingestics will send (with your API key masked) without actually calling the API. This lets you catch a typo in your endpoint URL or a missing header before it causes an error in your Activity Log.

Run Your First Fetch

Click Fetch Now on your crypto provider. Ingestics will call the API, parse the response using your field mapping, check for duplicates (so re-running the same fetch doesn’t create ten identical Bitcoin posts), and create WordPress posts in your chosen status. Check the Activity Log tab afterward — it will show exactly how many items were fetched, created, filtered, or flagged as duplicates, so you can verify everything worked as expected before moving to automation.

Automate the Updates (Lite Plan)

Crypto prices move by the minute, so manual fetching won’t cut it for a real tracker. On the Free plan, fetching is manual only. Upgrading to Lite unlocks scheduled fetching at 1-hour, 2-hour, 4-hour, 6-hour, or 24-hour intervals — hourly is a sensible default for a price tracker without hammering your API rate limits. Pro adds custom frequencies down to 15-minute intervals if you need closer to real-time updates.

Display Prices on Your Site (Lite Plan)

Once Lite is active, use the [aapi_feed] shortcode or the Ingestics Gutenberg block to display your latest crypto prices in a grid layout anywhere on your site — a dedicated “Crypto Prices” page, a homepage widget, or a sidebar. Set the post_type attribute to match your crypto custom post type and orderby="date" to always show the freshest data first.

Going Further: Keeping One Live Price Post Instead of Creating New Ones

Many crypto trackers want a single “Bitcoin Price Today” post that updates in place rather than a new post every hour. Ingestics’ core duplicate-detection logic is built to prevent republishing rather than update existing posts, so the cleanest pattern for a “live ticker” style page is: fetch into a dedicated custom post type on a schedule, then use the shortcode with count="1" and orderby="date" to always surface just the latest price post on your live page, while older price posts remain as a historical archive underneath — useful for showing price-history content over time, which also happens to be good for SEO.

On Pro, the content filter engine can automatically reject fetch items with no price/content, and on Business, AI rewrite can turn a bare price update into a short narrative summary (“Bitcoin is up 3% today, trading at…”) before publishing.

Troubleshooting Tips

No posts are being created: Check the Activity Log’s Message column — it will tell you if items were fetched but filtered, or if zero items were fetched (usually a mapping or auth issue). Use the Planned Call preview to double check the request being sent.

Duplicate coin posts every fetch: Make sure duplicate detection is checking on Title (coin name) or Source URL, and that your coin identifier is stable between fetches.

Rate limit errors: Most free-tier crypto APIs cap requests per minute. If you’re fetching too frequently, add spacing between provider schedules or check if your API plan needs an upgrade upstream.

Frequently Asked Questions

Do I need a paid crypto API to do this?
No — several crypto price APIs offer generous free tiers with no key required for basic market data. Check your chosen provider’s current terms and rate limits.

Can I track multiple coins at once?
Yes. If your API returns an array of coins in one response, Ingestics will map each coin in that array to its own WordPress post in a single fetch.

Will this work for other financial data too?
Yes — the same approach applies to stock prices, forex rates, or any other numeric API data. See our companion guide on importing stock market data for a dedicated walkthrough.

Real-World Example: A Top-10 Coin Tracker

Picture a simple finance blog that wants a “Top 10 Cryptocurrencies” page updated hourly. The provider is configured against an endpoint returning the top 10 coins by market cap in one JSON array call. Each fetch run creates or updates ten posts — Bitcoin, Ethereum, and so on — each with its current price, 24-hour change percentage, and coin logo mapped from the response. Because duplicate detection matches on title, “Bitcoin” from hour one and “Bitcoin” from hour two are treated as the same ongoing entry rather than ten new posts per day; the practical pattern most sites use is combining this with the “one live post, sorted by date” display trick described above, so the page always shows the freshest ten entries at the top, while historical price-point posts quietly accumulate underneath for anyone interested in browsing price history over time.

Common Mistakes to Avoid

• Mapping the wrong price field. Many crypto APIs return several price-related fields (current price, high/low, market cap, price change) — double check you’ve mapped “current price,” not a different numeric field, during your first preview.
• Fetching too frequently on a free API tier. Free-tier crypto APIs often cap requests per minute; scheduling every 15 minutes across several coins can exhaust a free quota faster than expected.
• Forgetting source attribution matters for financial data. Readers reasonably want to know where a price came from and when it was last updated — keep the source attribution block enabled rather than disabling it for a cleaner look.
• Not testing the image mapping. Coin logo URLs occasionally 404 or redirect; check your Activity Log’s image-sideload diagnostics after the first few fetches rather than assuming every logo attached correctly.

More Frequently Asked Questions

Can I show price change with an up/down colored indicator?
Map the percentage-change field into a custom field, then use your theme’s template or a small snippet to conditionally style it green or red based on the sign of the value — this styling logic lives in your theme, not in Ingestics’ field mapping itself.

What happens if the crypto API goes down temporarily?
Ingestics’ basic retry (free tier) attempts the request again automatically; Pro’s exponential backoff retry handles longer outages more gracefully, and your existing published posts remain visible and unaffected in the meantime.