The WooCommerce API has a simple authentication model using pre-generated secrets: Consumer Key (user) and Consumer Secret (password) on WooCommerce API calls.
There is currently no planned driver, but the data can easily be accessed using Invantive SQL as described for the Twinfield proxy of BI-ON-FOCUS on Replicate Twinfield through a Proxy :
( url => 'https://example.com/wp-json/wc/v3/orders?per_page=1000'
, contentType => 'application/json'
, headers => 'Authorization=Basic%20'
|| urlencode(base64_encode(ascii_to_blob('CONSUMERKEY' || ':' || 'CONSUMERSECRET')))
columns id int path 'id'
The code is untested since there is no access to an environment, but serve as a starting point.
The data can be replicated with Data Replicator using for instance:
create or replace table data_from_woo_commerce@InMemoryStorage
select /*+ ods(true, interval '0 seconds') */
This simple variant does not include paging. That would require some Invantive PSQL to feed back the data into the next call to
It is not clear in what way errors on WooCommerce are transported by the API to the client.