Integration error codes
Every public API error code emitted by Integration, with its HTTP status, its type and a page per code.
Error codes emitted by Integration. Each code links to its own page with the cause and the action to take.
| Code | Type | HTTP | Description |
|---|---|---|---|
charge_rule_invalid | invalid_request_error | 422 | The rule is inconsistent: the condition, the outcome, the not-invoiced reason, the concept or the VAT rate do not fit together or are not valid. The conflicting field is reported in param. |
charge_rule_limit_reached | invalid_request_error | 422 | The Stripe account already has the maximum number of charge treatment rules. |
charge_rule_not_found | not_found_error | 404 | The charge treatment rule does not exist on the given Stripe account or does not belong to your company. |
connect_return_domain_already_exists | conflict_error | 409 | The host you are trying to add is already one of the return domains of your account. It is compared normalized (lower case, no port or path), so App.Example.com and app.example.com are the same domain. |
connect_return_domain_limit_reached | invalid_request_error | 422 | Your account already has the maximum number of return domains it allows, and the new one was not saved. The cap is per account and counts every registered domain. |
connect_return_domain_not_found | not_found_error | 404 | The return domain named in the path does not exist in your account, or belongs to another one: both answers are identical on purpose so the domains of other accounts are never revealed. |
connect_return_url_not_allowed | invalid_request_error | 422 | The host of the return_url is not among the return domains of the account of the key you use to start the Stripe connection. Only https addresses whose exact host (no wildcards) is registered on that account are accepted, so nobody can send the person to a site you do not control. |
invalid_connection_method | invalid_request_error | 422 | The connection method does not exist for this provider. |
platform_account_subscriptions_owned_by_billing | invalid_request_error | 422 | The connected Stripe account is the platform's own account: Factuarea's subscription fees are invoiced by Billing directly, so that account does not support subscription autoinvoicing (subscription_autoinvoicing_enabled). |
shopify_api_version_expired | api_error | 500 | The Admin API version this connector speaks to the shop with is no longer supported. Shopify does not return an error when that happens: it serves the oldest stable version with a 200, so the breakage shows up as fields quietly missing from the response. |
shopify_credentials_rejected | invalid_request_error | 422 | The shop answered and rejected the access token, or there was none to use. In Shopify the token comes from authorising the app, and the merchant can revoke that authorisation from their admin at any time, so a token that worked yesterday may not work today without anyone changing a setting. |
shopify_store_unreachable | api_error | 502 | The shop did not answer: the request timed out, the transport failed, Shopify returned an error of its own, or the Admin API query cost budget was exhausted. What is failing sits upstream, not in the credential. |
store_already_connected | invalid_request_error | 422 | That shop is already connected to your company under the same provider. The pair provider plus remote shop is unique per company, so connecting it twice would leave two stores ingesting the same orders and invoicing them twice. |
store_external_id_mismatch | invalid_request_error | 422 | The remote identifier you are sending does not match any shop your company has authorised for that integration. With providers that sign their notifications using the application secret — Shopify — that identifier decides which company each sale is invoiced to, so only a shop that went through the authorisation flow is accepted. |
store_not_found | not_found_error | 404 | The identifier does not resolve to any connected store of the authenticated company. A store belonging to another company answers exactly the same way, so the response never reveals whether it exists elsewhere. |
store_url_not_allowed | invalid_request_error | 422 | The base address of the shop is not an authorised outbound destination for your company. Reading orders back from the shop would open a connection to a host nobody approved. |
stripe_account_linked_elsewhere | conflict_error | 409 | That Stripe account is already linked and active in another Factuarea company. An active Stripe account can only belong to one company. |
stripe_oauth_exchange_failed | invalid_request_error | 422 | Stripe did not confirm the account authorization: the authorization code expired, was already used or was denied. |
woocommerce_credentials_rejected | invalid_request_error | 422 | The shop answered and rejected the credential, or the credential could not be used at all: the key is missing, the secret is missing, or the base address is not https. Authentication travels in the header over HTTPS, so a shop published in clear text would hand over both pieces on the first hop, which is why it is rejected before anything leaves. |
woocommerce_rest_route_missing | invalid_request_error | 422 | The shop answered, but its REST API is not published: WordPress replied that the route does not exist. The usual cause is permalinks left on the plain setting, so /wp-json/ is not served. The credential may be perfectly valid. |
woocommerce_store_unreachable | api_error | 502 | The shop did not answer: the request timed out, the transport failed, or its hosting returned an error of its own. What is failing sits upstream, in the merchant's installation, not in the platform and not in the credential. |
Related
Error codes by category
Find an error by the category that emits it.
Full reference table
All codes, HTTP statuses, types and descriptions in one reference.
Error model
Interpret the error envelope and handle errors by code.