I’m working on an app that will connect sellers to buyers. Thus, there will be an e-commerce component with a need to split payment 3 ways - seller, platform (me), and a 3rd party. (Actually, I guess it’s 4-way considering the payment processor’s cut.)
Since I have a bit of experience with the WooCommerce REST API, I’ve been considering the possibility of using it to process payments instead of “reinventing the wheel” by building the payment functionality in Bubble. (Not sure if actually storing the products in WooCommerce makes sense though.)
I’d like to keep as much functionality in Bubble as possible - mostly for scalability and maintainability. I’ve net yet built a complete app in Bubble, let alone integrated split payments, so I’m not entirely sure what I’m up against.
Has anyone done anything like this? Might it be better in the long run to build the split payment functionality using Bubble?
Hello Steve, nice to meet you! I just want to see if you had any luck using WooCommerce REST API in Bubble since your post? Both are new concepts to me but seem very promising.
I want to build a new interface/app to create and edit orders manually, but I also want to keep running WooCommerce. Is this possible by using the REST API?
Absolutely, it’s totally possible. I’ve done it. While I didn’t use WooCommerce for the Bubble project referenced in this post, it might make sense if you already run a WC store and/or wish to create a custom UI and/or integrations for WC. The WC API is pretty well documented, so it’s just a matter of creating a Bubble plug-in (or using the API connector) to interface with Bubble.
Are you sure the keys are correct and that the associated user on the WP side has the appropriate permissions?
Looks like you’re trying to list WC orders, but if the user associated with those keys doesn’t have permission to view orders, you’ll get a 401 I believe.
The only other thing that comes to mind at the moment is that the docs do state that some servers don’t parse the auth header correctly…
Occasionally some servers may not parse the Authorization header correctly (if you see a “Consumer key is missing” error when authenticating over SSL, you have a server issue). In this case, you may provide the consumer key/secret as query string parameters instead.
…so maybe try sending the keys as qs params to see if that’s the issue.
EDIT: FWIW, I believe I had to do this for a couple WP sites.
(You could also test using postman or similar before implementing in Bubble.)
If the working installation is on a different host (or perhaps just a different plan with the same most), that suggests that simply adding the credentials to the URL (as query string parameters) will work for the original installation.
Hello I am just starting a new project : I already have a Woocomemrce Webstore and I want to build an App using Bubble and BDK Native APP. I have made some test but right now I am nor happy with the API Rest peformance. It take more than 3 minutes to display data from the rest Api connector. The API Response time is correct but Bubble take times to display the data. Did you have the same issue ?
As a troubleshooting step, have you tried hitting the endpoint with Postman or similar? That might give some indication whether the performance issue is with Bubble or your site.
Ah, ok. Sorry, I didn’t realize that’s what you meant in your previous post. In that case, I’m not sure what to suggest. The performance issue might have something to do with your workflow logic and/or it might be a Bubble platform issue - perhaps just a temporary one.
What data are you retrieving, and how are you displaying it in Bubble?