Legacy REST API Question

  • Resolved Frank B.

    (@frankbiganski)


    1 year ago

    Hi,

    Not truly knowing what REST API is, I know how to set up my plugins and add Stripe Publish and Secret API keys, and the Webhook too.

    But after seeing your recent “disclaimer” stating Legacy REST API was going to be removed in ver. 9.0, I disabled/unchecked Legacy REST API but customers began receiving an error when trying to check out.

    I enabled WooCommerce and Stripe test modes and the information is passing through to Stripe, but the customer and my tests were getting an error: Error processing your order. Please try again later.

    So I re-enabled Legacy REST API but I’m wondering how I can learn how to correct this. You mention an extension will be available, but I prefer to try and make it right.

    I use LearnPress and they have a WooCommerce Payments plugin, so I asked them if this is their issue or something I can correct/set up with your plugin.

    I see where I can add REST API and I give it a friendly nae and set the permissions to Read, Write, or Read & Write, but this is where I get lost.

    If you can point me in the best direction or some good reads, maybe I can figure out out to set this up correctly within the Legacy thing?

    Cheers!

    Frank B.
    thedronecoach.io

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @frankbiganski

    I appreciate your effort in trying to understand and implement the REST API. It’s not the simplest of tech, but with a little guidance, you’ll be able to navigate through it.

    The REST API is a set of functions through which developers can perform requests and receive responses via HTTP protocols such as GET and POST. It’s used to connect your WooCommerce store to other services and platforms.

    The error you’re experiencing might be due to some incompatibility issues between the new version of WooCommerce and your plugins. When you disabled the Legacy REST API, it might have disrupted the connection between your store and the payment gateway, hence the checkout error.

    Before moving forward, please ensure that all your plugins, especially WooCommerce and Stripe, are updated to their latest versions. This can often solve many issues.

    Next, regarding the setup of the REST API, I would recommend starting with our detailed documentation on REST API here: https://woocommerce.github.io/woocommerce-rest-api-docs/#introduction. It provides a comprehensive guide on how to set it up correctly.

    For more specific guidance related to your plugins, I recommend contacting the LearnPress team and asking them for assistance. They might be able to provide you with a more precise direction since they are familiar with their plugin’s compatibility with WooCommerce.

    Remember, transitioning from the Legacy REST API to the new REST API might require some time and testing. Also, as we explained on our blog, we will release an additional plugin to keep using Legacy API: https://developer.woo.com/2023/10/03/the-legacy-rest-api-will-move-to-a-dedicated-extension-in-woocommerce-9-0/

    I hope this clarifies your concern. If you have any other questions, feel free to ask.

    Thread Starter Frank B.

    (@frankbiganski)

    I so very much appreciate your detailed reply and web links Shameem. The documentation will help in me getting a better grasp on REST API.

    I found some older posts from 2018 and 2019 stating REST API between Woo and Stripe only passed customer information but not the credit card information. I realise that could be outdated but either way, when I have a few hours to spare, I’ll try generating new API keys via Woo and pasting those into my Stripe account and trying some testing. I have to get up really early to do this though when most of the U.S. is sleeping. ??

    I didn’t see in the docs though… are REST API’s typically set to READ only?

    I guess it will be a slow work-in-progress over the coming months into next year, but at least we have your extension to fall back on and that’s a huge relief.

    BTW, I already contacted LearnPress before contacting you and they stated “We have checked and found this issue seems to originate from Woocommerce”. Here’s a buck! ??

    Thanks again!

    Frank

    Plugin Support Beauty of Code (woo-hc)

    (@beautyofcode)

    Hey Frank,

    I’m really glad that @shameemreza was able to provide the clarity you needed!

    I didn’t see in the docs though… are REST API’s typically set to READ only?

    Yes, REST API’s are set to READ only.

    Since this has been resolved, feel free to create a new topic if you need any further help. ??

    Also, if you have a minute, we’d love it if you could leave us a review:

    https://www.ads-software.com/support/plugin/woocommerce/reviews/

    Cheers!

    Thread Starter Frank B.

    (@frankbiganski)

    Yes, resolved and I discovered it was my fault, no surprise, eh? ??

    The long, short version: Over the past many years, I was using LearnPress with a ThimPress theme and a LearnPress/Stripe plugin. I was not using Woo at the time.

    I recently switched to Total WordPress theme and installed WooCommerce. I also had to buy a LearnPress WooCommerce integration plugin.

    I did not know I should have uninstalled the original/old LearnPress/Stripe plugin. I also realized there were two unused ThimPress plugins that only pertained to the previous ThimPress theme. I thought they maybe were connected to the LearnPress plugin, but they were not.

    So I deleted the old/original LearnPress Stripe plugin, deleted the two unused ThimPress plugins, and then I was able to uncheck the Legacy REST API, and I no longer have any issues. I’m amazed my site was working at all.

    Anyway, no Legacy REST API issue to worry about for me and I sincerely appreciate ya’lls time.

    Frank

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Legacy REST API Question’ is closed to new replies.