Hello Harri, hope you are well!
Here’s the reference to Path Variable in the AppGyver docs: path variables
And attached is a screenshot of my current config.
I am trying to set up the Woocommerce Connector we discussed previously that I can eventually share on the marketplace, so of course I’d like the users’ URL to be able to be dynamically set… also as shown the Woocommerce API version might be nice. When adding the URL placeholders, I tied both adding the curly brackets and without but didn’t work either way.
On a related note, I couldn’t get the HTTP Header authorization to work. According the the most recent Woocommerce API docs Woocommerce AP Authorization
“You may use [HTTP Basic Auth] by providing the REST API Consumer Key as the username and the REST API Consumer Secret as the password.”
Again, the idea is to have this be a dynamic value provided by the end user. I’m using Postman right next to AppGyver and it works there, but I wasn’t having any luck (all the above strings were hardcoded of course). But the Woocommerce Docs did mention that the keys could be send as Query parameters, and I did get this work but its not as elegant as I’d like.
Finally, just so I understand how AppGyver wants REST APIs set-up, is the idea to have a separate resource created for each API, or could this be also set as a URL placeholder (products, coupons, orders etc)? Probably not, as then the resource schemas would be very messy.