Factuarea APIDevelopers

Test a WooCommerce store connection

Test the connection with one connected WooCommerce store and return the diagnosis.

  • The check reads the WooCommerce system status resource with the stored credential and writes nothing, neither in the shop nor in Factuarea.
  • It answers 200 with reachable, credential_accepted, the WooCommerce and WordPress versions the shop reports (WooCommerce publishes no REST API version of its own; the one this connector speaks is fixed on our side), the instant of the check and, when something went wrong, a failure_codewoocommerce_store_unreachable (the shop did not answer), woocommerce_credentials_rejected (the shop answered and refused the key) or woocommerce_rest_route_missing (the shop answered and does not publish its REST API).
  • Those three are outcomes of a check that ran, not failures of the API, which is why they travel inside a 200 instead of as an error status.
  • The endpoint is a POST because it makes an outbound call to an address you chose, so it consumes third-party resources and requires an Idempotency-Key header.
  • A missing store or one from another company returns 404 store_not_found.
POST
/woocommerce/stores/{store}/connection-test
AuthorizationBearer <token>

In: header

Path Parameters

store*string

Headers

Idempotency-Key*string

Client-generated opaque key (up to 255 characters; UUID v7 recommended) that makes retries safe: the first response is cached and replayed for repeats without re-executing the mutation. Reusing a key with a different body returns 409 idempotency_key_reused. See the Idempotency guide. Required on this operation: repeating it delivers an effect that cannot be taken back (an email sent, a file generated, a third-party call, a charge), so a request without this header is rejected with 422 idempotency_key_required before any business logic runs.

Length1 <= length <= 255
Factuarea-Version?string

Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.

Formatdate
X-Active-Profile?string

Operate on behalf of a child company (gestoría master key): pass its public id (UUID v7) and the request runs against that child's data without changing the key's scope, tier or environment (omit to use the key's own company). Invalid UUID → 400 parameter_invalid_uuid; unknown or non-owned id → 404 profile_not_found. See the Acting on behalf guide.

Formatuuid

Response Body

application/json

application/json

application/json

application/json

application/json

application/json

application/json

application/json