factpulse 4.1.2 → 4.4.0

data/lib/factpulse/api/flux6_invoice_lifecycle_cdar_api.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 
@@ -145,14 +145,16 @@ module FactPulse
     end
 
     # [Simplified] Get lifecycle events for invoices
-    # Returns lifecycle events (CDAR) grouped by invoice reference.  **How it works (AFNOR XP Z12-013 compliant):** 1. Searches lifecycle flows on the PDP by flowType + flowDirection + date range 2. Downloads and parses each CDAR XML to extract the invoice reference 3. Groups events by invoice, sorted chronologically  **Parameters:** - `days`: Number of days to look back (default: 7) - `invoiceId`: Optional filter on a specific invoice reference  **Authentication:** JWT Bearer (recommended) or PDP credentials as query parameters.
+    # Returns lifecycle events (CDAR) grouped by invoice reference.  **How it works (AFNOR XP Z12-013 compliant):** 1. Searches lifecycle flows on the PDP by flowType + flowDirection + date range 2. Downloads and parses each CDAR XML to extract the invoice reference 3. Groups events by invoice, sorted chronologically  **Parameters:** - `days`: Number of days to look back (default: 7) - `invoiceId`: Optional filter on a specific invoice reference - `flowDirection`: `All` (default), `In` (statuses received from the counterparty)   or `Out` (statuses issued by you or your PA, e.g. 202/203)  **Authentication:** JWT Bearer (recommended) or PDP credentials as query parameters.
     # @param [Hash] opts the optional parameters
     # @option opts [Integer] :days Number of days to look back (default to 7)
     # @option opts [String] :invoice_id Filter by invoice reference
+    # @option opts [String] :flow_direction All (default), In (received statuses) or Out (issued statuses) (default to 'All')
     # @option opts [String] :pdp_flow_service_url PDP Flow Service URL
     # @option opts [String] :pdp_token_url PDP OAuth token URL
     # @option opts [String] :pdp_client_id PDP Client ID
     # @option opts [String] :pdp_client_secret PDP Client Secret
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [LifecycleResponse]
     def get_lifecycle_api_v1_cdar_lifecycle_get(opts = {})
       data, _status_code, _headers = get_lifecycle_api_v1_cdar_lifecycle_get_with_http_info(opts)
@@ -160,14 +162,16 @@ module FactPulse
     end
 
     # [Simplified] Get lifecycle events for invoices
-    # Returns lifecycle events (CDAR) grouped by invoice reference.  **How it works (AFNOR XP Z12-013 compliant):** 1. Searches lifecycle flows on the PDP by flowType + flowDirection + date range 2. Downloads and parses each CDAR XML to extract the invoice reference 3. Groups events by invoice, sorted chronologically  **Parameters:** - `days`: Number of days to look back (default: 7) - `invoiceId`: Optional filter on a specific invoice reference  **Authentication:** JWT Bearer (recommended) or PDP credentials as query parameters.
+    # Returns lifecycle events (CDAR) grouped by invoice reference.  **How it works (AFNOR XP Z12-013 compliant):** 1. Searches lifecycle flows on the PDP by flowType + flowDirection + date range 2. Downloads and parses each CDAR XML to extract the invoice reference 3. Groups events by invoice, sorted chronologically  **Parameters:** - `days`: Number of days to look back (default: 7) - `invoiceId`: Optional filter on a specific invoice reference - `flowDirection`: `All` (default), `In` (statuses received from the counterparty)   or `Out` (statuses issued by you or your PA, e.g. 202/203)  **Authentication:** JWT Bearer (recommended) or PDP credentials as query parameters.
     # @param [Hash] opts the optional parameters
     # @option opts [Integer] :days Number of days to look back (default to 7)
     # @option opts [String] :invoice_id Filter by invoice reference
+    # @option opts [String] :flow_direction All (default), In (received statuses) or Out (issued statuses) (default to 'All')
     # @option opts [String] :pdp_flow_service_url PDP Flow Service URL
     # @option opts [String] :pdp_token_url PDP OAuth token URL
     # @option opts [String] :pdp_client_id PDP Client ID
     # @option opts [String] :pdp_client_secret PDP Client Secret
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [Array<(LifecycleResponse, Integer, Hash)>] LifecycleResponse data, response status code and response headers
     def get_lifecycle_api_v1_cdar_lifecycle_get_with_http_info(opts = {})
       if @api_client.config.debugging
@@ -181,6 +185,10 @@ module FactPulse
         fail ArgumentError, 'invalid value for "opts[:"days"]" when calling Flux6InvoiceLifecycleCDARApi.get_lifecycle_api_v1_cdar_lifecycle_get, must be greater than or equal to 1.'
       end
 
+      allowable_values = ["In", "Out", "All"]
+      if @api_client.config.client_side_validation && opts[:'flow_direction'] && !allowable_values.include?(opts[:'flow_direction'])
+        fail ArgumentError, "invalid value for \"flow_direction\", must be one of #{allowable_values}"
+      end
       # resource path
       local_var_path = '/api/v1/cdar/lifecycle'
 
@@ -188,6 +196,7 @@ module FactPulse
       query_params = opts[:query_params] || {}
       query_params[:'days'] = opts[:'days'] if !opts[:'days'].nil?
       query_params[:'invoiceId'] = opts[:'invoice_id'] if !opts[:'invoice_id'].nil?
+      query_params[:'flowDirection'] = opts[:'flow_direction'] if !opts[:'flow_direction'].nil?
       query_params[:'pdpFlowServiceUrl'] = opts[:'pdp_flow_service_url'] if !opts[:'pdp_flow_service_url'].nil?
       query_params[:'pdpTokenUrl'] = opts[:'pdp_token_url'] if !opts[:'pdp_token_url'].nil?
       query_params[:'pdpClientId'] = opts[:'pdp_client_id'] if !opts[:'pdp_client_id'].nil?
@@ -197,6 +206,7 @@ module FactPulse
       header_params = opts[:header_params] || {}
       # HTTP header 'Accept' (if needed)
       header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
+      header_params[:'Organization-Id'] = opts[:'organization_id'] if !opts[:'organization_id'].nil?
 
       # form parameters
       form_params = opts[:form_params] || {}
@@ -345,6 +355,7 @@ module FactPulse
     # Generate a CDAR message and submit it to the PA/PDP platform.  **Authentication strategies:** 1. **JWT with client_uid** (recommended): PDP credentials retrieved from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in the request  **Flow types (flowType):** - `CustomerInvoiceLC`: Client-side lifecycle (buyer) - `SupplierInvoiceLC`: Supplier-side lifecycle (seller)
     # @param submit_cdar_request [SubmitCDARRequest] 
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [SubmitCDARResponse]
     def submit_cdar_api_v1_cdar_submit_post(submit_cdar_request, opts = {})
       data, _status_code, _headers = submit_cdar_api_v1_cdar_submit_post_with_http_info(submit_cdar_request, opts)
@@ -355,6 +366,7 @@ module FactPulse
     # Generate a CDAR message and submit it to the PA/PDP platform.  **Authentication strategies:** 1. **JWT with client_uid** (recommended): PDP credentials retrieved from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in the request  **Flow types (flowType):** - &#x60;CustomerInvoiceLC&#x60;: Client-side lifecycle (buyer) - &#x60;SupplierInvoiceLC&#x60;: Supplier-side lifecycle (seller)
     # @param submit_cdar_request [SubmitCDARRequest] 
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [Array<(SubmitCDARResponse, Integer, Hash)>] SubmitCDARResponse data, response status code and response headers
     def submit_cdar_api_v1_cdar_submit_post_with_http_info(submit_cdar_request, opts = {})
       if @api_client.config.debugging
@@ -379,6 +391,7 @@ module FactPulse
       if !content_type.nil?
           header_params['Content-Type'] = content_type
       end
+      header_params[:'Organization-Id'] = opts[:'organization_id'] if !opts[:'organization_id'].nil?
 
       # form parameters
       form_params = opts[:form_params] || {}
@@ -413,6 +426,7 @@ module FactPulse
     # Submit a pre-generated CDAR XML message to the PA/PDP platform.  Useful for submitting XML generated by other systems.  **Validation:** The XML is validated against XSD and Schematron BR-FR-CDV rules BEFORE submission. Invalid XML will be rejected with detailed error messages.  **Authentication strategies:** 1. **JWT with client_uid** (recommended): PDP credentials retrieved from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in the request
     # @param submit_cdarxml_request [SubmitCDARXMLRequest] 
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [SubmitCDARResponse]
     def submit_cdar_xml_api_v1_cdar_submit_xml_post(submit_cdarxml_request, opts = {})
       data, _status_code, _headers = submit_cdar_xml_api_v1_cdar_submit_xml_post_with_http_info(submit_cdarxml_request, opts)
@@ -423,6 +437,7 @@ module FactPulse
     # Submit a pre-generated CDAR XML message to the PA/PDP platform.  Useful for submitting XML generated by other systems.  **Validation:** The XML is validated against XSD and Schematron BR-FR-CDV rules BEFORE submission. Invalid XML will be rejected with detailed error messages.  **Authentication strategies:** 1. **JWT with client_uid** (recommended): PDP credentials retrieved from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in the request
     # @param submit_cdarxml_request [SubmitCDARXMLRequest] 
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [Array<(SubmitCDARResponse, Integer, Hash)>] SubmitCDARResponse data, response status code and response headers
     def submit_cdar_xml_api_v1_cdar_submit_xml_post_with_http_info(submit_cdarxml_request, opts = {})
       if @api_client.config.debugging
@@ -447,6 +462,7 @@ module FactPulse
       if !content_type.nil?
           header_params['Content-Type'] = content_type
       end
+      header_params[:'Organization-Id'] = opts[:'organization_id'] if !opts[:'organization_id'].nil?
 
       # form parameters
       form_params = opts[:form_params] || {}
@@ -481,6 +497,7 @@ module FactPulse
     # **Simplified endpoint for OD** - Submit a PAID status (212) for an **ISSUED** invoice.  This status is **mandatory for PPF** (BR-FR-CDV-14 requires the paid amount).  **Use case:** The **seller** confirms payment receipt for an invoice they issued.  **Who issues this status?** - **Issuer (IssuerTradeParty):** The seller (SE = Seller) who received payment - **Recipient (RecipientTradeParty):** The buyer (BY = Buyer) who paid  **Reference:** XP Z12-014 Annex B, example UC1_F202500003_07-CDV-212_Encaissee.xml  **Authentication:** JWT Bearer (recommended) or PDP credentials in request.
     # @param encaissee_request [EncaisseeRequest] 
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [SimplifiedCDARResponse]
     def submit_encaissee_api_v1_cdar_encaissee_post(encaissee_request, opts = {})
       data, _status_code, _headers = submit_encaissee_api_v1_cdar_encaissee_post_with_http_info(encaissee_request, opts)
@@ -491,6 +508,7 @@ module FactPulse
     # **Simplified endpoint for OD** - Submit a PAID status (212) for an **ISSUED** invoice.  This status is **mandatory for PPF** (BR-FR-CDV-14 requires the paid amount).  **Use case:** The **seller** confirms payment receipt for an invoice they issued.  **Who issues this status?** - **Issuer (IssuerTradeParty):** The seller (SE &#x3D; Seller) who received payment - **Recipient (RecipientTradeParty):** The buyer (BY &#x3D; Buyer) who paid  **Reference:** XP Z12-014 Annex B, example UC1_F202500003_07-CDV-212_Encaissee.xml  **Authentication:** JWT Bearer (recommended) or PDP credentials in request.
     # @param encaissee_request [EncaisseeRequest] 
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [Array<(SimplifiedCDARResponse, Integer, Hash)>] SimplifiedCDARResponse data, response status code and response headers
     def submit_encaissee_api_v1_cdar_encaissee_post_with_http_info(encaissee_request, opts = {})
       if @api_client.config.debugging
@@ -515,6 +533,7 @@ module FactPulse
       if !content_type.nil?
           header_params['Content-Type'] = content_type
       end
+      header_params[:'Organization-Id'] = opts[:'organization_id'] if !opts[:'organization_id'].nil?
 
       # form parameters
       form_params = opts[:form_params] || {}
@@ -549,6 +568,7 @@ module FactPulse
     # **Simplified endpoint for OD** - Submit a REFUSED status (210) for a **RECEIVED** invoice.  This status is **mandatory for PPF** (BR-FR-CDV-15 requires a reason code).  **Use case:** The **buyer** refuses an invoice they received.  **Who issues this status?** - **Issuer (IssuerTradeParty):** The buyer (BY = Buyer) refusing the invoice - **Recipient (RecipientTradeParty):** The seller (SE = Seller) who issued the invoice  **Reference:** XP Z12-014 Annex B, example UC3_F202500005_04-CDV-210_Refusee.xml  **Allowed reason codes (BR-FR-CDV-CL-09):** - `TX_TVA_ERR`: Incorrect VAT rate - `MONTANTTOTAL_ERR`: Incorrect total amount - `CALCUL_ERR`: Calculation error - `NON_CONFORME`: Non-compliant - `DOUBLON`: Duplicate - `DEST_ERR`: Wrong recipient - `TRANSAC_INC`: Incomplete transaction - `EMMET_INC`: Unknown issuer - `CONTRAT_TERM`: Contract terminated - `DOUBLE_FACT`: Double billing - `CMD_ERR`: Order error - `ADR_ERR`: Address error - `REF_CT_ABSENT`: Missing contract reference  **Authentication:** JWT Bearer (recommended) or PDP credentials in request.
     # @param refusee_request [RefuseeRequest] 
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [SimplifiedCDARResponse]
     def submit_refusee_api_v1_cdar_refusee_post(refusee_request, opts = {})
       data, _status_code, _headers = submit_refusee_api_v1_cdar_refusee_post_with_http_info(refusee_request, opts)
@@ -559,6 +579,7 @@ module FactPulse
     # **Simplified endpoint for OD** - Submit a REFUSED status (210) for a **RECEIVED** invoice.  This status is **mandatory for PPF** (BR-FR-CDV-15 requires a reason code).  **Use case:** The **buyer** refuses an invoice they received.  **Who issues this status?** - **Issuer (IssuerTradeParty):** The buyer (BY &#x3D; Buyer) refusing the invoice - **Recipient (RecipientTradeParty):** The seller (SE &#x3D; Seller) who issued the invoice  **Reference:** XP Z12-014 Annex B, example UC3_F202500005_04-CDV-210_Refusee.xml  **Allowed reason codes (BR-FR-CDV-CL-09):** - &#x60;TX_TVA_ERR&#x60;: Incorrect VAT rate - &#x60;MONTANTTOTAL_ERR&#x60;: Incorrect total amount - &#x60;CALCUL_ERR&#x60;: Calculation error - &#x60;NON_CONFORME&#x60;: Non-compliant - &#x60;DOUBLON&#x60;: Duplicate - &#x60;DEST_ERR&#x60;: Wrong recipient - &#x60;TRANSAC_INC&#x60;: Incomplete transaction - &#x60;EMMET_INC&#x60;: Unknown issuer - &#x60;CONTRAT_TERM&#x60;: Contract terminated - &#x60;DOUBLE_FACT&#x60;: Double billing - &#x60;CMD_ERR&#x60;: Order error - &#x60;ADR_ERR&#x60;: Address error - &#x60;REF_CT_ABSENT&#x60;: Missing contract reference  **Authentication:** JWT Bearer (recommended) or PDP credentials in request.
     # @param refusee_request [RefuseeRequest] 
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [Array<(SimplifiedCDARResponse, Integer, Hash)>] SimplifiedCDARResponse data, response status code and response headers
     def submit_refusee_api_v1_cdar_refusee_post_with_http_info(refusee_request, opts = {})
       if @api_client.config.debugging
@@ -583,6 +604,7 @@ module FactPulse
       if !content_type.nil?
           header_params['Content-Type'] = content_type
       end
+      header_params[:'Organization-Id'] = opts[:'organization_id'] if !opts[:'organization_id'].nil?
 
       # form parameters
       form_params = opts[:form_params] || {}

data/lib/factpulse/api/health_api.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/api/invoice_generation_api.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 
@@ -110,9 +110,10 @@ module FactPulse
     end
 
     # Submit a complete invoice (generation + signature + submission)
-    # Unified endpoint to submit a complete invoice to different destinations.     **Facture prête pour Flux 2** - Génère une facture Factur-X complète avec signature optionnelle et soumission vers Chorus Pro ou PDP AFNOR.      **Automated workflow:**     1. **Auto-enrichment** (optional): retrieves data via public APIs and Chorus Pro/AFNOR     2. **Factur-X PDF generation**: creates a PDF/A-3 with embedded XML     3. **Electronic signature** (optional): signs the PDF with a certificate     4. **Submission**: sends to the chosen destination (Chorus Pro or AFNOR PDP)      **Supported destinations:**     - **Chorus Pro**: French B2G platform (invoices to public sector)     - **AFNOR PDP**: Partner Dematerialization Platforms      **Destination credentials - 2 modes available:**      **Mode 1 - Retrieval via JWT (recommended):**     - Credentials are retrieved automatically via the JWT `client_uid`     - Do not provide the `credentials` field in `destination`     - Zero-trust architecture: no secrets in the payload     - Example: `\"destination\": {\"type\": \"chorus_pro\"}`      **Mode 2 - Credentials in the payload:**     - Provide credentials directly in the payload     - Useful for tests or third-party integrations     - Example: `\"destination\": {\"type\": \"chorus_pro\", \"credentials\": {...}}`       **Electronic signature (optional) - 2 modes available:**      **Mode 1 - Stored certificate (recommended):**     - Certificate is retrieved automatically via the JWT `client_uid`     - No key to provide in the payload     - PAdES-B-LT signature with timestamp (eIDAS compliant)     - Example: `\"signature\": {\"reason\": \"Factur-X compliance\"}`      **Mode 2 - Keys in the payload (for tests):**     - Provide `key_pem` and `cert_pem` directly     - PEM format accepted: raw or base64     - Useful for tests or special cases without stored certificate     - Example: `\"signature\": {\"key_pem\": \"-----BEGIN...\", \"cert_pem\": \"-----BEGIN...\"}`      If `key_pem` and `cert_pem` are provided → Mode 2     Otherwise → Mode 1 (certificate retrieved via `client_uid`)
+    # Unified endpoint to submit a complete invoice to different destinations.     **Facture prête pour Flux 2** - Génère une facture Factur-X complète avec signature optionnelle et soumission vers Chorus Pro ou PDP AFNOR.      **Automated workflow:**     1. **Auto-enrichment** (optional): retrieves data via public APIs and Chorus Pro/AFNOR     2. **Factur-X PDF generation**: creates a PDF/A-3 with embedded XML     3. **Electronic signature** (optional): signs the PDF with a certificate     4. **Submission**: sends to the chosen destination (Chorus Pro or AFNOR PDP)      **Two accepted `invoiceData` formats, detected automatically** (same rule as     `/generate-invoice`):     - **Simplified format** (`number` + `lines`): totals, VAT and dates are computed.       Any field of the complete model may be added on top (`deliveryDate` BT-72,       `deliveryParty` BG-15, `paymentReference` BT-83, `supplier.bic` BT-86, ...).     - **Complete format** (`invoiceLines` present): full `FacturXInvoice` structure,       used as provided.      A non-compliant invoice is **not submitted**: the Schematron errors are returned     as a 400 `SCHEMATRON_VALIDATION_FAILED`, rather than a 200 followed by an     asynchronous rejection by the PA. This includes the empty-element rule     (PEPPOL-EN16931-R008), which the PAs apply as blocking.      **Supported destinations:**     - **Chorus Pro**: French B2G platform (invoices to public sector)     - **AFNOR PDP**: Partner Dematerialization Platforms      **Destination credentials - 2 modes available:**      **Mode 1 - Retrieval via JWT (recommended):**     - Credentials are retrieved automatically via the JWT `client_uid`     - Do not provide the `credentials` field in `destination`     - Zero-trust architecture: no secrets in the payload     - Example: `\"destination\": {\"type\": \"chorus_pro\"}`      **Mode 2 - Credentials in the payload:**     - Provide credentials directly in the payload     - Useful for tests or third-party integrations     - Example: `\"destination\": {\"type\": \"chorus_pro\", \"credentials\": {...}}`       **Electronic signature (optional) - 2 modes available:**      **Mode 1 - Stored certificate (recommended):**     - Certificate is retrieved automatically via the JWT `client_uid`     - No key to provide in the payload     - PAdES-B-LT signature with timestamp (eIDAS compliant)     - Example: `\"signature\": {\"reason\": \"Factur-X compliance\"}`      **Mode 2 - Keys in the payload (for tests):**     - Provide `key_pem` and `cert_pem` directly     - PEM format accepted: raw or base64     - Useful for tests or special cases without stored certificate     - Example: `\"signature\": {\"key_pem\": \"-----BEGIN...\", \"cert_pem\": \"-----BEGIN...\"}`      If `key_pem` and `cert_pem` are provided → Mode 2     Otherwise → Mode 1 (certificate retrieved via `client_uid`)
     # @param submit_complete_invoice_request [SubmitCompleteInvoiceRequest] 
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [SubmitCompleteInvoiceResponse]
     def submit_complete_invoice_api_v1_processing_invoices_submit_complete_post(submit_complete_invoice_request, opts = {})
       data, _status_code, _headers = submit_complete_invoice_api_v1_processing_invoices_submit_complete_post_with_http_info(submit_complete_invoice_request, opts)
@@ -120,9 +121,10 @@ module FactPulse
     end
 
     # Submit a complete invoice (generation + signature + submission)
-    # Unified endpoint to submit a complete invoice to different destinations.     **Facture prête pour Flux 2** - Génère une facture Factur-X complète avec signature optionnelle et soumission vers Chorus Pro ou PDP AFNOR.      **Automated workflow:**     1. **Auto-enrichment** (optional): retrieves data via public APIs and Chorus Pro/AFNOR     2. **Factur-X PDF generation**: creates a PDF/A-3 with embedded XML     3. **Electronic signature** (optional): signs the PDF with a certificate     4. **Submission**: sends to the chosen destination (Chorus Pro or AFNOR PDP)      **Supported destinations:**     - **Chorus Pro**: French B2G platform (invoices to public sector)     - **AFNOR PDP**: Partner Dematerialization Platforms      **Destination credentials - 2 modes available:**      **Mode 1 - Retrieval via JWT (recommended):**     - Credentials are retrieved automatically via the JWT `client_uid`     - Do not provide the `credentials` field in `destination`     - Zero-trust architecture: no secrets in the payload     - Example: `\"destination\": {\"type\": \"chorus_pro\"}`      **Mode 2 - Credentials in the payload:**     - Provide credentials directly in the payload     - Useful for tests or third-party integrations     - Example: `\"destination\": {\"type\": \"chorus_pro\", \"credentials\": {...}}`       **Electronic signature (optional) - 2 modes available:**      **Mode 1 - Stored certificate (recommended):**     - Certificate is retrieved automatically via the JWT `client_uid`     - No key to provide in the payload     - PAdES-B-LT signature with timestamp (eIDAS compliant)     - Example: `\"signature\": {\"reason\": \"Factur-X compliance\"}`      **Mode 2 - Keys in the payload (for tests):**     - Provide `key_pem` and `cert_pem` directly     - PEM format accepted: raw or base64     - Useful for tests or special cases without stored certificate     - Example: `\"signature\": {\"key_pem\": \"-----BEGIN...\", \"cert_pem\": \"-----BEGIN...\"}`      If `key_pem` and `cert_pem` are provided → Mode 2     Otherwise → Mode 1 (certificate retrieved via `client_uid`)
+    # Unified endpoint to submit a complete invoice to different destinations.     **Facture prête pour Flux 2** - Génère une facture Factur-X complète avec signature optionnelle et soumission vers Chorus Pro ou PDP AFNOR.      **Automated workflow:**     1. **Auto-enrichment** (optional): retrieves data via public APIs and Chorus Pro/AFNOR     2. **Factur-X PDF generation**: creates a PDF/A-3 with embedded XML     3. **Electronic signature** (optional): signs the PDF with a certificate     4. **Submission**: sends to the chosen destination (Chorus Pro or AFNOR PDP)      **Two accepted `invoiceData` formats, detected automatically** (same rule as     `/generate-invoice`):     - **Simplified format** (`number` + `lines`): totals, VAT and dates are computed.       Any field of the complete model may be added on top (`deliveryDate` BT-72,       `deliveryParty` BG-15, `paymentReference` BT-83, `supplier.bic` BT-86, ...).     - **Complete format** (`invoiceLines` present): full `FacturXInvoice` structure,       used as provided.      A non-compliant invoice is **not submitted**: the Schematron errors are returned     as a 400 `SCHEMATRON_VALIDATION_FAILED`, rather than a 200 followed by an     asynchronous rejection by the PA. This includes the empty-element rule     (PEPPOL-EN16931-R008), which the PAs apply as blocking.      **Supported destinations:**     - **Chorus Pro**: French B2G platform (invoices to public sector)     - **AFNOR PDP**: Partner Dematerialization Platforms      **Destination credentials - 2 modes available:**      **Mode 1 - Retrieval via JWT (recommended):**     - Credentials are retrieved automatically via the JWT `client_uid`     - Do not provide the `credentials` field in `destination`     - Zero-trust architecture: no secrets in the payload     - Example: `\"destination\": {\"type\": \"chorus_pro\"}`      **Mode 2 - Credentials in the payload:**     - Provide credentials directly in the payload     - Useful for tests or third-party integrations     - Example: `\"destination\": {\"type\": \"chorus_pro\", \"credentials\": {...}}`       **Electronic signature (optional) - 2 modes available:**      **Mode 1 - Stored certificate (recommended):**     - Certificate is retrieved automatically via the JWT `client_uid`     - No key to provide in the payload     - PAdES-B-LT signature with timestamp (eIDAS compliant)     - Example: `\"signature\": {\"reason\": \"Factur-X compliance\"}`      **Mode 2 - Keys in the payload (for tests):**     - Provide `key_pem` and `cert_pem` directly     - PEM format accepted: raw or base64     - Useful for tests or special cases without stored certificate     - Example: `\"signature\": {\"key_pem\": \"-----BEGIN...\", \"cert_pem\": \"-----BEGIN...\"}`      If `key_pem` and `cert_pem` are provided → Mode 2     Otherwise → Mode 1 (certificate retrieved via `client_uid`)
     # @param submit_complete_invoice_request [SubmitCompleteInvoiceRequest] 
     # @param [Hash] opts the optional parameters
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [Array<(SubmitCompleteInvoiceResponse, Integer, Hash)>] SubmitCompleteInvoiceResponse data, response status code and response headers
     def submit_complete_invoice_api_v1_processing_invoices_submit_complete_post_with_http_info(submit_complete_invoice_request, opts = {})
       if @api_client.config.debugging
@@ -147,6 +149,7 @@ module FactPulse
       if !content_type.nil?
           header_params['Content-Type'] = content_type
       end
+      header_params[:'Organization-Id'] = opts[:'organization_id'] if !opts[:'organization_id'].nil?
 
       # form parameters
       form_params = opts[:form_params] || {}
@@ -183,6 +186,7 @@ module FactPulse
     # @param [Hash] opts the optional parameters
     # @option opts [String] :callback_url Webhook URL for async notification when submission completes.
     # @option opts [String] :webhook_mode Webhook content delivery: &#39;inline&#39; (base64 in payload) or &#39;download_url&#39; (temporary URL, 1h TTL) (default to 'inline')
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [TaskResponse]
     def submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post(submit_complete_invoice_request, opts = {})
       data, _status_code, _headers = submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post_with_http_info(submit_complete_invoice_request, opts)
@@ -195,6 +199,7 @@ module FactPulse
     # @param [Hash] opts the optional parameters
     # @option opts [String] :callback_url Webhook URL for async notification when submission completes.
     # @option opts [String] :webhook_mode Webhook content delivery: &#39;inline&#39; (base64 in payload) or &#39;download_url&#39; (temporary URL, 1h TTL) (default to 'inline')
+    # @option opts [String] :organization_id Organization ID relayed to the PDP (AFNOR XP Z12-013 delegation / multi-tenancy). Required by some PDPs to select the client space.
     # @return [Array<(TaskResponse, Integer, Hash)>] TaskResponse data, response status code and response headers
     def submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post_with_http_info(submit_complete_invoice_request, opts = {})
       if @api_client.config.debugging
@@ -221,6 +226,7 @@ module FactPulse
       if !content_type.nil?
           header_params['Content-Type'] = content_type
       end
+      header_params[:'Organization-Id'] = opts[:'organization_id'] if !opts[:'organization_id'].nil?
 
       # form parameters
       form_params = opts[:form_params] || {}

data/lib/factpulse/api/parse_api.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/api/references_api.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/api/validation_api.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/api_client.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/api_error.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/api_model_base.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/configuration.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/helpers/client.rb

@@ -3,7 +3,11 @@
 # FactPulse SDK - Thin HTTP wrapper with auto-polling.
 #
 # Usage:
-#   client = FactPulseClient.new('email', 'password', 'client_uid')
+#   client = FactPulse::Client.new(email: 'email', password: 'password', client_uid: 'client_uid')
+#   # or with a pre-obtained JWT (e.g. dashboard test token):
+#   client = FactPulse::Client.new(token: 'eyJ...')
+#   # positional form (backward compatible):
+#   client = FactPulse::Client.new('email', 'password', 'client_uid')
 #
 #   # POST /api/v1/processing/invoices/submit-complete-async
 #   result = client.post('processing/invoices/submit-complete-async',
@@ -31,15 +35,38 @@ module FactPulse
   class Client
     DEFAULT_API_URL = 'https://factpulse.fr'
 
-    def initialize(email, password, client_uid, api_url: DEFAULT_API_URL, timeout: 60, polling_timeout: 120)
+    # Create a client.
+    #
+    # Keyword form (recommended):
+    #   FactPulse::Client.new(email: '...', password: '...', client_uid: '...')
+    #   FactPulse::Client.new(token: 'eyJ...')  # pre-obtained JWT (e.g. dashboard test token)
+    #
+    # Positional form (backward compatible with <= 4.3.0):
+    #   FactPulse::Client.new('email', 'password', 'client_uid')
+    def initialize(*args, email: nil, password: nil, client_uid: nil, token: nil,
+                   api_url: DEFAULT_API_URL, timeout: 60, polling_timeout: 120)
+      unless args.empty?
+        if email || password || client_uid || token
+          raise ArgumentError, 'use either positional (email, password, client_uid) or keyword arguments, not both'
+        end
+        unless (2..3).cover?(args.length)
+          raise ArgumentError, "wrong number of arguments (given #{args.length}, expected 3)"
+        end
+        email, password, client_uid = args
+      end
+
+      if token.nil? && (email.nil? || password.nil?)
+        raise ArgumentError, 'provide email: and password: (or token: with a pre-obtained JWT)'
+      end
+
       @email = email
       @password = password
       @client_uid = client_uid
       @api_url = api_url.chomp('/')
       @timeout = timeout
       @polling_timeout = polling_timeout
-      @token = nil
-      @token_expires_at = 0
+      @token = token
+      @token_expires_at = token ? Float::INFINITY : 0
       @token_mutex = Mutex.new
     end
 
@@ -243,6 +270,14 @@ module FactPulse
     end
 
     def refresh_token
+      if @email.nil? || @password.nil?
+        raise Error.new(
+          'Access token expired or rejected, and no email/password available to refresh it. ' \
+          'Provide email: and password:, or create a new client with a fresh token:.',
+          status_code: 401
+        )
+      end
+
       uri = URI("#{@api_url}/api/token/")
       http = Net::HTTP.new(uri.host, uri.port)
       http.use_ssl = uri.scheme == 'https'
@@ -250,7 +285,9 @@ module FactPulse
 
       req = Net::HTTP::Post.new(uri)
       req['Content-Type'] = 'application/json'
-      req.body = JSON.generate(username: @email, password: @password, client_uid: @client_uid)
+      payload = { username: @email, password: @password }
+      payload[:client_uid] = @client_uid if @client_uid
+      req.body = JSON.generate(payload)
 
       response = http.request(req)
 

data/lib/factpulse/models/acknowledgment_status.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/models/action_code_info.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/models/action_codes_response.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/models/additional_document.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/models/afnor_acknowledgement.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/models/afnor_acknowledgement_detail.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/models/afnor_address_read.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 

data/lib/factpulse/models/{afnor_diffusion_status.rb → afnor_contains_or_start_with_operator.rb}

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 
@@ -14,12 +14,12 @@ require 'date'
 require 'time'
 
 module FactPulse
-  class AFNORDiffusionStatus
-    O = "O".freeze
-    P = "P".freeze
+  class AFNORContainsOrStartWithOperator
+    CONTAINS = "contains".freeze
+    START_WITH = "startWith".freeze
 
     def self.all_vars
-      @all_vars ||= [O, P].freeze
+      @all_vars ||= [CONTAINS, START_WITH].freeze
     end
 
     # Builds the enum from string
@@ -33,8 +33,8 @@ module FactPulse
     # @param [String] The enum value in the form of the string
     # @return [String] The enum value
     def build_from_hash(value)
-      return value if AFNORDiffusionStatus.all_vars.include?(value)
-      raise "Invalid ENUM value #{value} for class #AFNORDiffusionStatus"
+      return value if AFNORContainsOrStartWithOperator.all_vars.include?(value)
+      raise "Invalid ENUM value #{value} for class #AFNORContainsOrStartWithOperator"
     end
   end
 end

data/lib/factpulse/models/{afnor_contains_operator.rb → afnor_contains_or_strict_operator.rb}

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 Contact: contact@factpulse.fr
 Generated by: https://openapi-generator.tech
-Generator version: 7.21.0-SNAPSHOT
+Generator version: 7.21.0
 
 =end
 
@@ -14,11 +14,12 @@ require 'date'
 require 'time'
 
 module FactPulse
-  class AFNORContainsOperator
+  class AFNORContainsOrStrictOperator
     CONTAINS = "contains".freeze
+    STRICT = "strict".freeze
 
     def self.all_vars
-      @all_vars ||= [CONTAINS].freeze
+      @all_vars ||= [CONTAINS, STRICT].freeze
     end
 
     # Builds the enum from string
@@ -32,8 +33,8 @@ module FactPulse
     # @param [String] The enum value in the form of the string
     # @return [String] The enum value
     def build_from_hash(value)
-      return value if AFNORContainsOperator.all_vars.include?(value)
-      raise "Invalid ENUM value #{value} for class #AFNORContainsOperator"
+      return value if AFNORContainsOrStrictOperator.all_vars.include?(value)
+      raise "Invalid ENUM value #{value} for class #AFNORContainsOrStrictOperator"
     end
   end
 end

data/lib/factpulse/models/afnor_contains_or_strict_or_start_with_operator.rb

@@ -0,0 +1,41 @@
+=begin
+#FactPulse REST API
+
+# REST API for electronic invoicing in France: Factur-X (CII), UBL 2.1, AFNOR PDP/PA, electronic signatures.  ## 🎯 Main Features  ### 📄 Invoice Generation - **Formats**: CII XML, UBL 2.1 XML, or Factur-X PDF/A-3 - **Profiles** (CII/PDF): MINIMUM, BASIC, EN16931, EXTENDED - **UBL**: Always EN16931 compliant - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT), UBL 2.1 (OASIS) - **Simplified Format**: Generation from SIRET + auto-enrichment (Chorus Pro API + Business Search)  ### ✅ Factur-X - Validation - **XML Validation**: Schematron (45 to 210+ rules depending on profile) - **PDF Validation**: PDF/A-3, Factur-X XMP metadata - **VeraPDF**: Strict PDF/A validation (146+ ISO 19005-3 rules)  ### ✍️ Electronic Signature - **Standards**: PAdES-B-B, PAdES-B-T (RFC 3161 timestamping), PAdES-B-LT (long-term archival) - **eIDAS Levels**: SES (self-signed), AdES (commercial CA), QES (QTSP) - **Validation**: Cryptographic integrity and certificate verification  ### 📋 Flux 6 - Invoice Lifecycle (CDAR) - **CDAR Messages**: Acknowledgements, invoice statuses - **PPF Statuses**: REFUSED (210), PAID (212)  ### 📊 Flux 10 - E-Reporting - **Tax Declarations**: International B2B, B2C - **Flow Types**: 10.1 (B2B transactions), 10.2 (B2B payments), 10.3 (B2C transactions), 10.4 (B2C payments)  ### 📡 AFNOR PDP/PA (XP Z12-013) - **Flow Service**: Submit and search flows to PDPs - **Directory Service**: Company search (SIREN/SIRET) - **Multi-client**: Support for multiple PDP configs per user  ### 🏛️ Chorus Pro - **Public Sector Invoicing**: Complete API for Chorus Pro  ### ⏳ Async Tasks - **Celery**: Asynchronous generation, validation and signing - **Polling**: Status tracking via `/tasks/{task_id}/status` - **Webhooks**: Automatic notifications when tasks complete  ## 🔒 Authentication  All requests require a **JWT token** in the Authorization header: ``` Authorization: Bearer YOUR_JWT_TOKEN ```  ### How to obtain a JWT token?  #### 🔑 Method 1: `/api/token/` API (Recommended)  **URL:** `https://factpulse.fr/api/token/`  This method is **recommended** for integration in your applications and CI/CD workflows.  **Prerequisites:** Having set a password on your account  **For users registered via email/password:** - You already have a password, use it directly  **For users registered via OAuth (Google/GitHub):** - You must first set a password at: https://factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API  **Request example:** ```bash curl -X POST https://factpulse.fr/api/token/ \\   -H \"Content-Type: application/json\" \\   -d '{     \"username\": \"your_email@example.com\",     \"password\": \"your_password\"   }' ```  **Optional `client_uid` parameter:**  To select credentials for a specific client (PA/PDP, Chorus Pro, signing certificates), add `client_uid`:  ```bash curl -X POST https://factpulse.fr/api/token/ \\   -H \"Content-Type: application/json\" \\   -d '{     \"username\": \"your_email@example.com\",     \"password\": \"your_password\",     \"client_uid\": \"550e8400-e29b-41d4-a716-446655440000\"   }' ```  The `client_uid` will be included in the JWT and allow the API to automatically use: - AFNOR/PDP credentials configured for this client - Chorus Pro credentials configured for this client - Electronic signature certificates configured for this client  **Response:** ```json {   \"access\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\",  // Access token (validity: 30 min)   \"refresh\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\"  // Refresh token (validity: 7 days) } ```  **Advantages:** - ✅ Full automation (CI/CD, scripts) - ✅ Programmatic token management - ✅ Refresh token support for automatic access renewal - ✅ Easy integration in any language/tool  #### 🖥️ Method 2: Dashboard Generation (Alternative)  **URL:** https://factpulse.fr/api/dashboard/  This method is suitable for quick tests or occasional use via the graphical interface.  **How it works:** - Log in to the dashboard - Use the \"Generate Test Token\" or \"Generate Production Token\" buttons - Works for **all** users (OAuth and email/password), without requiring a password  **Token types:** - **Test Token**: 24h validity, 1000 calls/day quota (free) - **Production Token**: 7 days validity, quota based on your plan  **Advantages:** - ✅ Quick for API testing - ✅ No password required - ✅ Simple visual interface  **Disadvantages:** - ❌ Requires manual action - ❌ No refresh token - ❌ Less suited for automation  ### 📚 Full Documentation  For more information on authentication and API usage: https://factpulse.fr/documentation-api/     
+
+The version of the OpenAPI document: 1.0.0
+Contact: contact@factpulse.fr
+Generated by: https://openapi-generator.tech
+Generator version: 7.21.0
+
+=end
+
+require 'date'
+require 'time'
+
+module FactPulse
+  class AFNORContainsOrStrictOrStartWithOperator
+    CONTAINS = "contains".freeze
+    STRICT = "strict".freeze
+    START_WITH = "startWith".freeze
+
+    def self.all_vars
+      @all_vars ||= [CONTAINS, STRICT, START_WITH].freeze
+    end
+
+    # Builds the enum from string
+    # @param [String] The enum value in the form of the string
+    # @return [String] The enum value
+    def self.build_from_hash(value)
+      new.build_from_hash(value)
+    end
+
+    # Builds the enum from string
+    # @param [String] The enum value in the form of the string
+    # @return [String] The enum value
+    def build_from_hash(value)
+      return value if AFNORContainsOrStrictOrStartWithOperator.all_vars.include?(value)
+      raise "Invalid ENUM value #{value} for class #AFNORContainsOrStrictOrStartWithOperator"
+    end
+  end
+end