Resolve a catalog price
Resolve the effective catalog price for a complete catalog selection — product, optional variant, optional presentation, optional commercial combination (configuration_id), its canonical selection_signature and the chosen option_value_ids — under an optional price list.
- The combination and its signature are NOT mutually exclusive here: a real selection carries both, because the signature is derived from the combination.
- What is rejected is repeating the cross the combination already identifies (
variant_id/presentation_id). - No amount is ever accepted in the payload: every own price and every option adjustment comes from the catalog, so a caller cannot price its own line.
- The response carries the breakdown (
unit_semantics,source_amount,option_adjustment_total,option_adjustments_absorbed) so a double charge is detectable from the preview —sourcealone cannot tell a price-list entry that ABSORBS the option adjustments from a legacy one that ADDS them, and both sayprice_list.
In: header
Headers
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.
dateOperate 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.
uuidRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json