PlugIndex

Directory / plugin

Aura Historia Partner Connect

v0.3.2 · by aurahistoria

Connects WooCommerce to Aura Historia by creating and maintaining the product webhooks your store needs.

View on WordPress.org

About this plugin

Aura Historia Partner Connect connects a WooCommerce store to Aura Historia.

After you connect the store through Aura Historia OAuth, the plugin automatically:

  • creates and maintains exactly three WooCommerce product webhooks:
    • product.created
    • product.updated
    • product.deleted
  • keeps those managed webhooks in sync without creating duplicates
  • repairs plugin-owned webhooks after manual edits or deletion
  • generates and stores the WooCommerce webhook signing secret automatically
  • sends webhook deliveries to Aura Historia using the built-in endpoint pattern
  • pauses plugin-owned webhooks on deactivation
  • removes plugin-owned webhooks and plugin options on uninstall
  • queues the first published-product CREATE backfill once per ListingSource after successful configuration; failed setup/queueing leaves that first run pending for later retry, while ordinary repairs never start a fresh run
  • imports supported local shipping configuration and scoped item class/variation inputs through separate typed APIs after connection, local changes, periodic reconciliation and the Import shipping repair action

The plugin keeps the settings surface intentionally small. Merchants do not manually enter Aura Historia credentials in wp-admin. The OAuth flow sets and stores:

  • ListingSource ID (ls_ TypeID)
  • Aura Historia access token

Merchants do not enter:

  • a webhook delivery URL
  • a webhook secret

This plugin is intended for merchants who already use Aura Historia. Once OAuth completes, the plugin sends product data to Aura Historia so the connected catalog can stay in sync.

External services

This plugin connects to Aura Historia, a hosted service required for the plugin to work.

It sends data after a merchant connects the store through Aura Historia OAuth, and later when WooCommerce sends managed webhook events or the plugin runs a product backfill or shipping import. These background jobs run without an open admin page.

The service is used to:

  • register the generated WooCommerce webhook secret and current store locale details
  • receive ongoing product webhook deliveries
  • receive background product backfill batches
  • store typed shipping profiles, source defaults, listing selections and class/variation inputs acquired locally by the plugin

Data sent to the service may include:

  • when connecting, to the Aura Historia OAuth broker: the OAuth client ID, requested permissions, this store’s settings page URL, a random state value and a completion challenge, and later the transaction ID, the one-time completion code and the matching completion secret
  • ListingSource ID (ls_ TypeID)
  • Aura Historia access token in the bearer Authorization header for backend API calls
  • Aura Historia access token in a bearer Authorization header on managed live webhook deliveries
  • generated WooCommerce webhook secret
  • store language and currency
  • unchanged signed WooCommerce webhook payloads for product.created, product.updated, and product.deleted, including any WooCommerce descriptions
  • published products during backfill: WooCommerce product ID as sourceListingId, canonical URL, image URL array, optional localized title, optional tagged monetary price (exact integer currency minor units; non-representable prices omitted), and optional availability. Backfill does not send description/body yet (follow-up #93).
  • shipping import: supported geographic shipping rules and ordered zones, enabled service identifiers, exact/conditional rates and currency, pickup availability without addresses, source-scoped class/variation codes, WooCommerce product IDs, producer operation keys/order and actual acquisition time. Shipping requests do not contain credentials in their bodies, whole settings/metadata, customers, orders, addresses or full product descriptions.

Service endpoints:

  • POST https://aura-historia.com/api/oauth/client/redirect-broker/woocommerce/transactions (from the store’s server)
  • GET https://aura-historia.com/{language}/oauth/authorize (in the merchant’s browser)
  • POST https://aura-historia.com/api/oauth/client/redirect-broker/woocommerce/transactions/complete (from the store’s server)
  • PUT https://api.aura-historia.com/v1/listing-sources/{listingSourceId}/ingestion-configurations/woocommerce
  • POST https://api.aura-historia.com/v1/webhooks/woocommerce/{listingSourceId}
  • POST https://api.aura-historia.com/v1/listing-sources/{listingSourceId}/product-listings/async
  • GET/POST https://api.aura-historia.com/v1/listing-sources/{listingSourceId}/shipping-profiles
  • GET/PUT/DELETE https://api.aura-historia.com/v1/listing-sources/{listingSourceId}/shipping-profiles/{shippingProfileId} and POST .../{shippingProfileId}/restore
  • GET/PUT/DELETE https://api.aura-historia.com/v1/listing-sources/{listingSourceId}/shipping-default
  • GET/PATCH https://api.aura-historia.com/v1/listing-sources/{listingSourceId}/product-listings/by-source-id/{sourceListingId}/delivery

Service provider and policies:

Plugin tags