HTTP POST Auth Keys

This setting displays the currently defined keys used to authenticate HTTP POSTs.

For security reasons, HTTP POST auth keys are separate from autologin auth keys, since autologin auth keys are visible in links.

For best security practices you should not reuse, or tie your HTTP POST auth keys to your Infusionsoft API key, or to your autologin auth keys.

You can define multiple HTTP POST auth keys by separating each one with a comma. This makes it easy to transition from one key to another by having multiple active keys at once. HTTP POST auth keys are defined in your i2SDK plugin.

  • Was this Helpful?
  • YesNo
9 ways to add more value to your membership site

Table of Contents

Keep Reading

Force Cache Flush

WordPress uses a caching system to map SEO / human readable page links into WordPress’s native links. This process is called URL rewriting, and the cache is referred to as the URL Rewrite Cache. When using some plugins, this URL conversion cache can be come corrupted. The symptom of this is random 404 page errors for pages that actually exist.

Read More »

Want to get some fresh ideas on how you can improve your membership site or course?

Download our free ebook!

Book a Call

Welcome to Memberium!

We are very excited for you to be part of our family. 

We would love to answer any questions that you have!

Please choose the best time for you to get in a call with us. 

For Technical Support, you can contact us at https://keap.memberium.com/support/ or Email us at support@memberium.com.