Factuarea APIDevelopers
Support
Open app

Delete a charge treatment rule

Delete a charge treatment rule.

  • Charges already excluded by it keep their record in the non-invoiced charges list.
  • Responds 204 with no body.
  • Returns 404 charge_rule_not_found if the rule does not exist in that account and company.
DELETE
/connected-accounts/{account}/charge-rules/{rule}

Authorization

AuthorizationBearer <token>

In: header

Path Parameters

account*string
rule*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.

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

Previous/v1/connected-accounts/{account}/charge-rules
POST

Create a charge treatment rule

Create a charge treatment rule at the end of the account's list. A rule matches a charge by condition and either invoices it (optionally with a concept and a vat_rate) or excludes it from invoicing with a non_invoice_reason (indemnity_not_subject, multipurpose_voucher or invoiced_elsewhere). Responds 201 with the rule. Fails with charge_rule_invalid when a field breaks the contract and with charge_rule_limit_reached when the account already has the maximum number of rules.

Next/v1/connected-accounts/{account}/charge-rules/{rule}
PUT

Update a charge treatment rule

Replace a charge treatment rule: condition, outcome, concept, vat_rate and non_invoice_reason are all sent again; its position does not change (use the reorder operation). Returns 404 charge_rule_not_found if the rule does not exist in that account and company, and 422 charge_rule_invalid when a field breaks the contract.