Quentin Goin 2 Posted September 11, 2019 Share Posted September 11, 2019 Ive created a Swagger file for WooCommerce to setup as a scribe connector and need to pass 2 parameters in the query to Authorize my user. I have a Consumer_Key and Consumer_Secret. I am able to see data in Postman when I use OAuth1.0, however, Scribe Online does not seem to support OAuth1.0. As shown in the screen shot below, this OAuth1.0 DOES have response of data with the Add authorization data to: Request Body/Request URL selected. (The screen shots show inaccurate key/secret and domain to protect the customer.) In Postman, using BasicAuth does NOT give data response as shown in second screen shot. (Again, the keys and domain have been changed to protect the customer.) Ive tried to get an end result of the followingURL with no success in Scribe Online connector. https://www.example.com/wp-json/wc/v3/ordersconsumer_key=123&consumer_s... This is per https://woocommerce.github.io/woocommerce-rest-api-docs/shell#rest-api-keys Any ideas or suggestions would be appreciated on how to get Scribe Online to Authenticate to WooCommerce API as I can do in Postman. Link to comment Share on other sites More sharing options...
Quentin Goin 2 Posted September 13, 2019 Author Share Posted September 13, 2019 After further investigation and options, a workaround for Query (GET) only was determined... If consumer_key and consumer_secret are used in the Swagger as GET parameters, they show up on the filters tab in Scribe Online. Then using those as filters, populate with the api keys. It works for query blocks which is what I need it for. Updating (Put) or creating (post) will not work this way due to Scribe blocks not having filters. I did have to put a generic URI in the TEST URI for the connector. Example: https://staging.domain.com/wp-json/wc/v3 (did not end with "customers" for example) Link to comment Share on other sites More sharing options...
Recommended Posts