4 Ways to Monetize Your Website With Datafeedr

Since 2008, Datafeedr has helped thousands of affiliate marketers worldwide monetize their websites. Having the biggest affiliate product database worldwide and a powerful search engine to search across different affiliate networks and excellent tech support Datafeedr has become the number 1 affiliate datafeed integration service for affiliates worldwide. If you’re new to Datafeedr here’s a quick overview how you can monetize your website with affiliate content.

1: Create a WooCommerce Affiliate Store

The Datafeedr WooCommerce Importer Plugin allows you to search, select and import affiliate products from Datafeedr’s huge database (at the time of this writing 600+ million products) into your WordPress website and display those products using one of the most popular eCommerce platforms, WooCommerce.

To get an idea about the store building process just watch this video in which Eric shows you how easy it is to import affiliate products into your WordPress WooCommerce store.

Each product has its own landing page. The Buy Now button (affiliate link) redirects to the corresponding product page on the merchant’s site. Want to bypass the single product pages on your website entirely? No problem. It’s possible to make all of the product links on your product category pages go directly to the merchant’s website.

2: Supplement Your WooCommerce Product Detail Pages by Adding Price Comparison Sets

By default, a WooCommerce theme uses a generic page to show basic product information like product name, description, image and price for example. To make your product pages more unique you can use the Datafeedr Comparison Sets Plugin to supplement that product information with a price comparison set.

When the WooCommerce Integration option in the plugin is activated, a price comparison set will be automatically created for each product in your WooCommerce store – ie. if any product matches are found in the product feeds from your selected merchants.

3: Embed Price Comparison Sets into Blog Posts and Pages or any Other Area Where WordPress Shortcodes are Allowed

If you prefer not to create an affiliate store… no worries… you can still use Datafeedr to monetize your site content. Our Comparison Sets Plugin also allows you to embed Price Comparison Sets in blog posts, pages or in any other area where WordPress shortcodes are allowed. Ideal for affiliates with product review websites.

4: Create Your Own Custom Solution by Using the Datafeedr API

Are you a developer and want to create your own custom solution? Our API provides a powerful interface that enables you to programmatically find and filter product and coupon data from the affiliate networks and merchants we support giving you the keys to build something awesome! The API does not handle anything other than allowing you to query our product database and returning products. The rest is up to you or your developer(s) :). Click here to access our API documentation.

Alternatives to Amazon Associates Program

You may or may not have heard that on April 21, 2020 Amazon will drastically reduce its commissions in several of their product categories in the US market.

  1. Furniture, Home, Home Improvement, Lawn & Garden, Pets Products, Pantry 8.00% 3.00%
  2. Headphones, Beauty, Musical Instruments, Business & Industrial Supplies 6.00% 3.00%
  3. Outdoors, Tools 5.50% 3.00%
  4. Grocery 5.00% 1.00%
  5. Sports 4.50% 3.00%
  6. Baby Products 4.50% 3.00%
  7. Health & Personal Care 4.50% 1.00%
  8. Amazon Fresh 3.00% 1.00%

Below you see a table of the current fee rates and a table with the upcoming changes.

As you can see commission rates for popular categories such as home improvement, furniture, lawn and garden, and pet products will see a commission rate of 8 percent per sale drop down to just 3 percent! For headphones, beauty products, and musical instruments, commission rates will go from 6 percent down to 3 percent. Some other categories even drop down to a measly 1 percent. You can always check out Amazon’s latest fees here.

If you are currently promoting products from the affected categories you will notice a decline in your commissions. If Amazon is your most important source of internet income, now is the time to evaluate and diversify your income stream for your website or blog. Don’t make Amazon the ONLY way that you earn from your site. Find and test other affiliate programs in your niche. Experiment with display advertising on your affiliate pages.

Alternatives to the Amazon USA Associates Program

Amazon’s announcement seems to only apply to their USA program. As far as we know, these changes do not affect other locales and each locale has its own commission structure. If you are promoting products in the US market and your niche is affected by these new commission structures, the following affiliate networks might be worth looking into as alternatives:

Datafeedr does support all these affiliate networks (and many others). You can browse a full list of all of the 17,000+ merchants we support.

Many large retailers often run their own in-house affiliate program, too. These are programs where you create a direct relationship with the merchant/retailer instead of going through an affiliate network.

If you think a specific retailer would be a good alternative to the Amazon Associates Program, just Google the retailer’s name along with the phrase “Affiliate Program”.

While it might take some time to replace your Amazon affiliate links with other competing offers, it could pay off… especially if you are in some of those product categories taking the biggest hit.

What do you think of Amazon’s new changes? Let us know in the comments below.

Are Your Product Pages Missing the Mark? Here’s How You Can Fix It

All too many affiliate product pages are thin in content and boring. Learn how to up your product description (re)writing game and avoid common mistakes with this guide.

Have you worked hard building your affiliate store but still aren’t seeing the conversion rates you had hoped for? It’s possible that your product pages are completely missing the mark.

If you’re using a merchant’s product feed to create your product pages this is more likely to be true. Here are a couple of issues you will face when importing the manufacturers’ product descriptions straight into your website.


The product descriptions merchants provide in their datafeeds are most of the time only a few dozen words or even worse… sometimes a merchant does not provide product descriptions at all. As a result, you end up with product pages thin in content.

Here’s an example of a thin product page only listing a product image, the product name and description, the price, buy now link and links to the other product categories on the site.

As you can see in the image below (click on it to enlarge the image) the product information comes straight from the merchant’s datafeed. The description hardly counts 36 words! With so less information potential customers will have to know exactly what your product is all about from the start or guess based on the picture.

If you’re going to sell your visitors on the products you’re promoting, try to provide plenty of details. They should never have questions about what a product is or how it works. The more information you can provide, the more confident they’ll feel and the less likely it will be they will search for more information elsewhere.

If you explain what the product is, how the product works, what makes this product special and why your visitors need it in their lives you’ll make it clear for any potential customer who comes across your site, increasing the chance that they’ll click the Buy Now button.

When we look at this SEO-wise… by having too many of such thin, low quality content pages on your site you will be dragging down the overall “quality score” of your site. And you run the risk that your site gets devalued by Google’s core algorithm.

But even if your site isn’t negatively affected by Google’s core algorithm, it can still be hit by a manual Google penalty. If a human reviewer at Google finds that your site is not following Google’s webmaster quality guidelines, a manual action may be applied to your site (partial or site-wide). As long as your site has a manual action against it, some or all of your pages will be devalued in Google’s search results until you fix the issue(s). When it involves a thin content penalty the manual action may look like this in your Google Search Console.


Another issue you will face when using a merchant’s datafeed is that you’re not the only affiliate who is using the datafeed. It’s likely other affiliates are using the same datafeed on their sites too. That means the same product descriptions will end up on multiple websites. Let’s take a look at another thin product page example.

Also in this example the product information comes straight from the merchant’s datafeed – click on the image below to enlarge it.

When copying and pasting the first 2 sentences of the product description into Google you’ll see that about 20 sites are all using the same product description.

As you know, the key to running a successful affiliate business is to make your site stand out against the competition. If your product descriptions are identical to your competitors’, potential customers will have no reason to choose you over them. In addition when potential customers realize they’ve read the same content elsewhere, that experience can reduce their trust in your site and likeliness that they’ll visit your site again in the future.

When we look at this SEO-wise… to avoid a bad user experience search engines don’t want their users to land on the same content over and over again. If there are multiple pages with the same content across different domains, Google will simply decide which page they want to show to their users for a given search query and which ones to ignore.

Simply put: if your site has the same copy as dozens or hundreds of other affiliate sites, there’s no reason why Google would choose your page over all the other pages with the same copy for a given search query. But when you go the extra mile by writing unique, rich and full product descriptions, you don’t force Google and other search engines to choose between multiple pages with the same content.


Finally manufacturers’ product descriptions in datafeeds are most of the time boring boilerplate copy rather than engaging, useful copy designed to connect with potential customers.

Your product copy should be rich and interesting. Visitors to your website have a very short attention span, and your job is to make sure they stay focused on your product for long enough so they click the buy now button. To do this, you need to capture their emotions, not just their logic.

The goal is to draw visitors in and make them feel like they’ll have a happy, simple life if only they buy this product. You can’t make false claims, of course, but don’t be afraid to get colorful.

Good product descriptions should use lots of adjectives and attention-grabbing words. If you’re describing a cooking pot, saying it’s a stainless steel pot with heat-resistant handles won’t convince anyone to part with their money over it. But describing in loving detail how this pot distributes heat evenly over a surface so that you can get a perfect saute every time will catch the attention of kitchen enthusiasts.


In the Webmaster Guidelines for Affiliate Sites Google explains exactly how the above issues may negatively affect your rankings. The guidelines clearly state that thin and duplicate affiliate pages

  • can suffer in Google’s search rankings
  • are highly unlikely to perform well in Google search results
  • may be negatively perceived by search engines

The good news, however, is that Google also tells you exactly what to do to make your site stand out to distinguish you from other affiliates who are promoting the same products. The guidelines clearly state to

  • create websites with original content that adds value for users
  • make sure you add substantial value beyond simply republishing content from the original merchant
  • keep your content updated, relevant, fesh and on-topic

If you want to avoid the above issues and comply with Google’s guidelines here’s how to up your product pages for both potential customers and search engines.


When (re)writing your product pages add some keywords (and variations) that you know your customers are searching for. Some simple keyword research can help you get lots of ideas for keywords to use in your product page. Keyword research can also help you get ideas for features you may want to include in your content.

Let’s say, for instance, that you’re wanting to sell light bulbs. You may discover that people are searching for “incandescent light bulbs”, “energy-efficient bulbs” and “recyclable bulbs”. Include in your product description that your light bulbs meet both those requirements, increasing your product’s appeal.

Be careful not to stuff too many keywords into your product page to try to get a higher search ranking. Search engine algorithms may knock you down for that. Always write for your visitors not for search engines.


The first step to creating engaging, useful product descriptions is to write a good hook. You want to capture your potential customers’ attention right away, so start with something that will get them excited. There’s a big difference between “Buy a new Buick today,” and “Are you ready to start the engine on your next adventure?”

You should also try to connect with the customer as much as possible. People like hearing about themselves, and they’re more likely to buy your product if they can see themselves using it.

So talk about your customers’ experience using your product, not just what makes your company great. Paint a picture of how they will feel using your product and how it will improve their life. If you’d like a good example of this kind of appeal, take a look at car commercials; they focus almost to a fault on the experience of driving the car rather than the concrete details.

You also want to make sure you stick the landing. Anyone who works in sales will know the first and last sentences of your pitch are what will sell your product. Sum up what your customers stand to gain by buying your product, and give them a specific call to action to follow.


While you’re writing these engaging descriptions, you want to make sure you don’t turn off your customers with the appearance of your page. Large walls of text are intimidating, and no one wants to dive into them. Think about how much easier it is to tackle reading a Twitter feed than it is a New York Times article.

Keep your paragraphs short and well-spaced on your description page. Try to limit paragraphs to three sentences or less, with a nice mix of one- and two-sentence paragraphs in there. This will make it easier for your customers to keep reading through your copy and make it to the pitch at the end.

You should also try to keep your content as readable as possible. On average, you want to aim for a ninth-grade reading level so you don’t overwhelm your audience with a lot of technical jargon. Sticking to simple, clear descriptions will keep potential customers from getting frustrated and leaving your page.

Some Examples

Let’s take the product description from our first example again. We upgraded the decription from 36 words to about 300+ words trying to solve problem 1: thin content, problem 2: duplicate content and problem 3: boring boilerplate copy.

Let’s take the product description from our second example now. We upgraded the decription from 178 words to about 350+ words trying to solve problem 1: thin content, problem 2: duplicate content, problem 3: boring boilerplate copy and problem 4: unreadable massive block of text.

In both examples visitors have a better idea now what the products are all about, why the products are special and why they need it. Search engines will no longer see thin and duplicate content on the product pages in question. And by adding additional product pics and/or product videos the product pages in question can be made even more unique and rich in content.

How Datafeedr Can Help

Honing your product description writing skills can increase your traffic and sales conversions. It will put you ahead of the majority of affiliates who are promoting the same products as you. Keep in mind that you won’t become an expert overnight. Learning to write great product descriptions that connect with your specific customer base will take time and practice.

You can do it all yourself or you can let us do all the hard work for you. There’s no shame in bringing in a pro. We’ve teamed up with some excellent writers who can definitely help to create engaging product descriptions for the products you’re promoting on your site. We would love to help you create a world-class affiliate store optimized for SEO today. If you’re interested in this service don’t hesitate to contact us today to learn more.

Building a WooCommerce Store Using Affiliate Feeds

A couple of weeks ago I spoke with BobWP on his WP eCommerce Show. You can find that talk here https://wpecommerceshow.com/building-a-woocommerce-store-using-affiliate-feeds-with-eric-busch/

Here are a few of the topics we discussed:

  1. What is Datafeedr and how did it come to be?
  2. Is it viable to start up an online store with just affiliate products?
  3. For new site owners, how do you get accepted by these affiliate networks with nothing selling on your site?
  4. Are there ever instances where store owners will mix affiliate products in with their own products?
  5. Is there such as thing as having too many affiliate products in your store?

Add filter to WooCommerce category metabox on Product Set “edit” page

If you have a lot of categories (like I have on geargrabber.net) you may find that scrolling and finding the category you are looking for is time-consuming. Here’s what the default WooCommerce category metabox looks like on a Product Set “edit” page:

You can use the Post Category Filter plugin to add a filter to your WooCommerce category box to make it easy to filter your long list of WooCommerce categories to something more manageable.

Here’s what the end result looks like:

Simple as that!

GDPR, WordPress & You – A Webinar

This morning SiteGround did a 1-hour webinar about GDPR. In the webinar their senior legal advisor Maya Stoyanova talked about the procedures you need to follow in order to run a GDPR-compliant business and the changes you may need to undertake to comply with the new regulations.

If you are running a WordPress website (which you probably are), there were many relevant questions regarding GDPR and WordPress and what steps you need to take to get compliant.

The webinar was NOT SiteGround-specific so even if you are not hosted with SiteGround, it doesn’t matter. It’s all very relevant.

Check it out: https://www.crowdcast.io/e/what-is-gdpr

I would also keep an eye on SiteGround’s Blog for a summary and transcripts of the webinar in the next few days.

Here is the related blog post.

3 Custom WooCommerce Buy Buttons

There are lots of fun things you can do to WooCommerce [Buy Now] and [Add to Cart] buttons.

Here I’ll show you a few ways you can customize WooCommerce buttons which appear in The Loop (Shop Frontpage, Shop Category pages, etc…). You can add the code snippets below to a Custom Plugin.

First, let’s see how buttons look like be default. Here is a screenshot of 3 products on a category page. All 3 of these products are External (or Affiliate) products so they display a greyed out [Buy Now] button.

Default Button Display in WooCommerce Loop

Add Highlighting to Buttons for Products On Sale

This one will format the WooCommerce buttons by highlighting the buttons for products which are on sale.

Here’s what that would look like:

The custom code for that looks like this:

<?php /** * Add highlighting to an add to cart button for WooCommerce products which are on sale. * * @param string $html * @param WC_Product $product * @param array $args * * @return string */ function mycode_display_highlighted_add_to_cart_button_for_products_on_sale( $html, $product, $args ) { if ( ! $product->is_on_sale() ) { return $html; } $extra_class = ' alt'; $extra_text = ' SALE'; $url = $product->add_to_cart_url(); $quantity = isset( $args['quantity'] ) ? $args['quantity'] : 1; $class = isset( $args['class'] ) ? $args['class'] . $extra_class : 'button' . $extra_class; $attributes = isset( $args['attributes'] ) ? wc_implode_html_attributes( $args['attributes'] ) : ''; $text = $product->add_to_cart_text() . $extra_text; $format = '<a href="%1$s" data-quantity="%2$s" class="%3$s" %4$s>%5$s</a>'; return sprintf( $format, esc_url( $url ), esc_attr( $quantity ), esc_attr( $class ), $attributes, esc_html( $text ) ); } add_filter( 'woocommerce_loop_add_to_cart_link', 'mycode_display_highlighted_add_to_cart_button_for_products_on_sale', 20, 3 );

Remove Buy/Add Buttons

In some cases you may want to remove the buttons altogether. This might be useful for the next few code snippets.

Here’s how to remove the Buy/Add buttons from your WooCommerce Loops.

<?php /** * Remove the action which adds [Add to Cart] & [Buy Now] buttons * to the WooCommerce Product Loop */ function mycode_remove_add_to_cart_from_loop() { remove_action( 'woocommerce_after_shop_loop_item', 'woocommerce_template_loop_add_to_cart' ); } add_action( 'init', 'mycode_remove_add_to_cart_from_loop' );

Add [More Details] Button Linking to Single Product Page

Now that the Buy/Add button is gone, we can add some other buttons to The Loop.

Here we will add a [More Details] button which links to the single product page.

While it’s not that exciting, we will build on this in the following examples. But if you like this, here’s the code:

<?php /** * Adds an action to the loop to display a [More Details] button * to the WooCommerce Product Loop which links to the Single Product Page. */ function mycode_add_more_details_button_to_single() { add_action( 'woocommerce_after_shop_loop_item', 'mycode_display_more_details_button_to_single' ); } add_action( 'init', 'mycode_add_more_details_button_to_single' ); /** * Display [More Details] button HTML with a link to the Single Product Page. * * @global WC_Product $product */ function mycode_display_more_details_button_to_single() { global $product; $url = $product->get_permalink(); $text = __( 'More Details', 'mycode' ); $title = sprintf( __( 'View more details about %s', 'mycode' ), $product->get_name() ); $class = sprintf( 'button add_to_cart_button product_type_%s', $product->get_type() ); $format = '<a href="%1$s" title="%2$s" class="%3$s">%4$s</a>'; printf( $format, esc_url( $url ), esc_attr( $title ), esc_attr( $class ), esc_html( $text ) ); }

Link Directly to External/Affiliate Site from [More Details] Button

The one is strictly for External/Affiliate products. This adds a new [More Details] button which links directly to the external/affiliate website instead of your single product page.

This looks very similar to the default functionality of WooCommerce.

And here’s the custom code:

<?php /** * Adds an action to the loop to display a [More Details] button * to the WooCommerce Product Loop which links to an External/Affiliate product. */ function mycode_add_more_details_button_to_external() { add_action( 'woocommerce_after_shop_loop_item', 'mycode_display_more_details_button_to_external' ); } add_action( 'init', 'mycode_add_more_details_button_to_external' ); /** * Display [More Details] button HTML with a link to an External/Affiliate product. * * @global WC_Product_External $product */ function mycode_display_more_details_button_to_external() { /** * @var WC_Product_External $product */ global $product; if ( 'external' != $product->get_type() ) { return; } $url = $product->get_product_url(); $text = __( 'Buy Now', 'mycode' ); $title = sprintf( __( 'View more details about %s', 'mycode' ), $product->get_name() ); $class = sprintf( 'button add_to_cart_button product_type_%s', $product->get_type() ); $format = '<a href="%1$s" title="%2$s" class="%3$s" target="_blank">%4$s</a>'; printf( $format, esc_url( $url ), esc_attr( $title ), esc_attr( $class ), esc_html( $text ) ); }

Add Price to Button

Here we will add the product’s price (regular or sale price) to the button. This helps prices stand out a bit more.

Here’s the custom code for that:

<?php /** * Adds an action to the loop to display a [Buy $199.99] button containing the price * to the WooCommerce Product Loop which links to an External/Affiliate product. */ function mycode_add_more_details_button_to_external_with_price() { add_action( 'woocommerce_after_shop_loop_item', 'mycode_display_more_details_button_to_external_with_price' ); } add_action( 'init', 'mycode_add_more_details_button_to_external_with_price' ); /** * Display [Buy $199.99] button HTML containing the price with a link to an External/Affiliate product. * * @global WC_Product_External $product */ function mycode_display_more_details_button_to_external_with_price() { /** * @var WC_Product_External $product */ global $product; if ( 'external' != $product->get_type() ) { return; } $url = $product->get_product_url(); $price = wc_price( $product->get_price() ); $text = sprintf( __( 'Buy %s', 'mycode' ), $price ); $title = sprintf( __( 'Buy %s', 'mycode' ), $product->get_name() ); $class = sprintf( 'button add_to_cart_button product_type_%s', $product->get_type() ); $format = '<a href="%1$s" title="%2$s" class="%3$s" target="_blank">%4$s</a>'; printf( $format, esc_url( $url ), esc_attr( $title ), esc_attr( $class ), $text ); }

Add Merchant’s Name to Button

Here’s another one that works well for External/Affiliate products. We can also add the merchant’s name to the button.

And here’s the code:

<?php /** * Adds an action to the loop to display a [Buy at Acme] button containing the merchant's name * to the WooCommerce Product Loop which links to an External/Affiliate product. */ function mycode_add_more_details_button_to_external_with_merchant_name() { add_action( 'woocommerce_after_shop_loop_item', 'mycode_display_more_details_button_to_external_with_merchant_name' ); } add_action( 'init', 'mycode_add_more_details_button_to_external_with_merchant_name' ); /** * Display [Buy at Acme] button containing the merchant's name in the * WooCommerce Product Loop which links to an External/Affiliate product. * * @global WC_Product_External $product */ function mycode_display_more_details_button_to_external_with_merchant_name() { /** * @var WC_Product_External $product */ global $product; if ( 'external' != $product->get_type() ) { return; } $url = $product->get_product_url(); $merchant = $product->get_attribute( 'pa_merchant' ); $text = $merchant ? sprintf( __( 'Buy at %s', 'mycode' ), $merchant ) : __( 'Buy Now', 'mycode' ); $title = sprintf( __( 'View more details about %s', 'mycode' ), $product->get_name() ); $class = sprintf( 'button add_to_cart_button product_type_%s', $product->get_type() ); $format = '<a href="%1$s" title="%2$s" class="%3$s" target="_blank">%4$s</a>'; printf( $format, esc_url( $url ), esc_attr( $title ), esc_attr( $class ), esc_html( $text ) ); }

Those are all for the WooCommerce Loop but if you want to make similar customizations on the Single Product Page, you would want to use the woocommerce_after_single_product_summary hook.

Using OAuth 1.0 with the WordPress API & Custom Endpoints

This very long article covers setting up OAuth 1.0 to work with the core version of the WordPress API.

We will be generating client keys, oauth tokens, a custom endpoint and allowing access to our API only from those whom we have manually authenticated via OAuth.

Before we begin, I have 2 local installs of WordPress:


This is our main API website that our client will make requests to.


This is our client website that will make requests to the API website.

I have listed quite a few resources that I used to put together this tutorial at the bottom of the article. In some cases, I’ve just copied the code or steps. If you get stuck or want more info, I highly encourage you to read those resources. They will definitely be worth your time!

Get some coffee and let’s begin!

Test to make sure you can connect to the API.

Add the following code to your plugin on your client site.

Change the $url value to match the URL of the API site’s URL. So it will be something like http://example.com/wp-json

Mine is installed on my local machine that’s why the URL is http://wp-api-main/wp-json

Then create a new page and add this shortcode to the page [test_api_connection]

Open the page and you should see content like this:

    [name] => WP-API Main
    [description] => Just another WordPress site
    [url] => http://wp-api-main
    [home] => http://wp-api-main
    [namespaces] => Array
            [0] => oembed/1.0
            [1] => wp/v2

    [authentication] => Array

    [routes] => Array
            [/] => Array
                    [namespace] => 
                    [methods] => Array
                            [0] => GET

                    [endpoints] => Array
                            [0] => Array
                                    [methods] => Array
                                            [0] => GET
// ...

Here’s what mine looks like:

The thing to notice is that the [authentication] is an empty array. Let’s change that part.

Now go to your main API site and install and activate the “WordPress REST API – OAuth 1.0a Server” plugin.

Once installed and activated, go to Users > Applications and click the [Add New] button.

On the “Add Application” page you will fill in some values. “Consumer Name” and “Description” can be whatever you wish. Just put something that makes sense.

I’m not sure what the Callback does at this time so I just inserted something like “http://wp-api-main/auth/success”.

After you have filled in all 3 fields, click the [Add Consumer] button.

Now you will see that the Client has a Client Key and Client Secret under the “OAuth Credentials” section.

Copy those for later.

Client Key (consumer_key):


Client Secret (consumer_secret):


Now if you go back to the new page you created on your Client site which has the shortcode, the [authentication] array should have some values in it.

Now we need to hook up these keys with our client so that our client can then make subsequent authenticated API requests to our API site.

The details behind this process are complicated and covered in detail in some of the resource links I share at the bottom of this article especially on nobil.cc.

The method I found the easiest to use the above keys is with an app like Postman or Paw. Postman is free and also has a Chrome extension if you aren’t on a Mac. I’ll use Postman in this tutorial because it’s free.

For these next steps, I relied heavily on nobil.cc. It contains more background on this process. Definitely worth the read!

If you have questions about these next few steps, check that article, too.

Open the Postman app.

In the “Get” request URL field enter the URL of the main API website’s /oauth1/request path. I have entered


Under Authorization Type, choose OAuth 1.0

Enter the Consumer Key (ie. the Client Key) and Consumer Secret (ie. the Client Secret).

Click the [Update Request] button. This will automatically fill in the timestamp field and the Nonce field.

Your request URL will have been update to something like this:


Then click the [Send] button.

Scroll down to see the response. You should see something like this:


Save that string somewhere. We will need these 2 initial OAuth tokens:





Next, we will use the “oauth_token” value we just got and construct a URL like this (on our Main API site):


Load the URL in your browser.

You will get a login-type screen which has a message like “Howdy eric,
“Client API Connection” would like to connect to WP-API Main.”

Click the [Authorize] button.

The next screen will have a message like this: “Your verification token is PvHs1j8ol5FqVd4QPv0eGt9t

verification token


Copy that token down… we’ll need that later, too!

The last step is to get our access token.

So in Postman, enter this URL into the request URL field:


This time you will need to fill in your:

  • Consumer Key
  • Consumer Secret
  • Token
  • Token Secret

Clicking the [Update Request] button will fill in the nonce and timestamp and your request URL will be transformed into something like this:


Next click the [Params] button to the right of the request URL.

Add 1 new row to the params. Set the key to “oauth_verifier” and the value to “PvHs1j8ol5FqVd4QPv0eGt9t” (which is the value we got in the previous step.

Then click the [Send] button. Note that you may need to click the [Update Request] again and then click [Send].

After you scroll down you will see your new tokens.






You can now disregard your old oauth_token and oauth_token_secret tokens. You won’t need the old ones anymore. You only need these new ones. Additionally, you can disregard your oauth_verifier code as well. You shouldn’t need that code any more.

OK, we are done with Postman and we now have the necessary OAuth tokens we need in order to make an authenticated API request.

The only thing is, our main API site does not require authentication yet. So let’s force it to require authentication.

On your main API site, install the Disable Rest API plugin.

So now we have 2 plugins installed on our main API site:

  • WP REST API – OAuth 1.0a Server
  • Disable REST API

Let’s make sure our API now requires authentication. Go to the test page you created on your client site and load the page again.

You should now see a 401 “rest_cannot_access” message like this.

Excellent! I bet you’ve never been so happy to see a 401 message. 🙂

So, now that we have the keys to get around that restriction and authenticate, let’s do so.

But we’re not out of the woods yet… unfortunately, not even close.

The next bit of code mostly comes from this Sitepoint article. Please refer to that for more details. In our case, we will make a class that handles sending the proper headers to an API that requires authentication. Time to get more coffee… I’ll be here when you get back.

We are going to create a new shortcode so that we can add it to our page with the other shortcode.

Let’s first go to our page and modify our page so it looks like this:



Then we need to add a new shortcode to our plugin so we can start testing our OAuth connection.

Here’s our new shortcode:

A few things to take note of…

We added a $method variable and set it to ‘GET‘. That matches our wp_remote_get() call.

We added the various keys that we created to a $keys array.

Then we passed the $keys, $url and $method variables as parameters to our new OAuth_Authorization_Header() class. More on that in a second.

We get the $header value from the get_header() method and then added our authorization header array to a new $args array.

Lastly, we modified our call to wp_remote_get() by adding the $args array as the second parameter to the function.

The rest of the shortcode code is the same as our first one.

OK, so what about the new OAuth_Authorization_Header class?

Well, it’s a modified and simplified version of the class in the Sitepoint article which is itself a modified and simplified version of the code from a Twitter WordPress HTTP client. Love me some open source!

Here’s the basic OAuth_Authorization_Header class without documentation or checks to ensure all the required data is present… it’s a starting point. Be sure to validate the incoming arguments.

So now when you load the page with your shortcodes on your client site, you should have one ‘access denied’ message and one with a successful response.

The last thing I want to do is set up a custom endpoint on my API site and make that custom endpoint protected. Currently, all of our endpoints are private because we installed the Disable REST API plugin. But what if you just want a single custom endpoint to be private, not all endpoints?

Here’s how we can do that.

First, disable the Disable REST API plugin on your main API site.

After you do that, now both your shortcodes on your client site should load a successful response like this:

Next, create a custom plugin on your main API site and add the following code to your plugin:

Basically, this creates a new endpoint and returns an array if successfully called.

Let’s tweak our URLs in our client plugin:

In the client plugins we have this:

$url = 'http://wp-api-main/wp-json';

Let’s change that to this to make a request to a specific endpoint:

$url = 'http://wp-api-main/wp-json/myapiplugin/v2/greeting';

Be sure to change the $url variable in BOTH shortcodes.

Then refresh the page on your client site with the shortcodes. You should now see 2 successful responses.

Perfect! Now, let’s make that new endpoint private so only authenticated clients can access it.

Change the Main API plugin to this:

You see we have added a new item to array in the third parameter of the call to register_rest_route(). We have added:

'permission_callback' => 'myapiplugin_permission_callback',

Then we added a new function to our plugin that returns ‘true‘ if the current user can update core WordPress or false if the user can not. Who is this user that “current_user_can” is referring to? That user is our client who we have granted permissions to through the OAuth key exchange (back in the Postman section of this article).

So now that we have added this new authentication code to our plugin, let’s go back to our client shortcode page and reload that page.

Now you should see 1 access denied message and one success message.

And now you have successfully set up OAuth1 with your WordPress API so that a client that you have explicitly granted access to can call a private endpoint that you have set up.


Here are some of the articles I referenced when putting my article together. They were a huge help so if you are looking for more information about some of these steps, do check these out:

1 2 3 4