factpulse 3.0.10 → 3.0.14

data/docs/EReportingFlowType.md

@@ -0,0 +1,15 @@
+# FactPulse::EReportingFlowType
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+
+## Example
+
+```ruby
+require 'factpulse'
+
+instance = FactPulse::EReportingFlowType.new()
+```
+

data/docs/ElectronicAddress.md

@@ -4,8 +4,8 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **identifier** | **String** |  |  |
-| **scheme_id** | [**SchemeID**](SchemeID.md) |  | [optional] |
+| **identifier** | **String** | Electronic address identifier (e.g., SIREN, SIRET, routing code) |  |
+| **scheme_id** | [**SchemeID**](SchemeID.md) | Identification scheme (EAS code) | [optional] |
 
 ## Example
 

data/docs/EnrichedInvoiceInfo.md

@@ -4,14 +4,14 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **invoice_number** | **String** |  |  |
+| **invoice_number** | **String** | Invoice number |  |
 | **supplier_id** | **Integer** |  | [optional] |
 | **recipient_id** | **Integer** |  | [optional] |
-| **supplier_name** | **String** |  |  |
-| **recipient_name** | **String** |  |  |
-| **total_net_amount** | **String** |  |  |
-| **vat_amount** | **String** |  |  |
-| **total_gross_amount** | **String** |  |  |
+| **supplier_name** | **String** | Supplier name |  |
+| **recipient_name** | **String** | Recipient name |  |
+| **total_net_amount** | **String** | Total net amount (HT) |  |
+| **vat_amount** | **String** | VAT amount |  |
+| **total_gross_amount** | **String** | Total gross amount (TTC) |  |
 
 ## Example
 

data/docs/FactureElectroniqueModelsInvoiceTypeCode.md

@@ -0,0 +1,15 @@
+# FactPulse::FactureElectroniqueModelsInvoiceTypeCode
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+
+## Example
+
+```ruby
+require 'factpulse'
+
+instance = FactPulse::FactureElectroniqueModelsInvoiceTypeCode.new()
+```
+

data/docs/FactureElectroniqueRestApiSchemasConvertValidationError.md

@@ -0,0 +1,32 @@
+# FactPulse::FactureElectroniqueRestApiSchemasConvertValidationError
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **rule** | **String** | Code de la regle (BR-XX, BR-FR-XX) |  |
+| **bt_code** | **String** |  | [optional] |
+| **severity** | **String** | Gravite: error, warning |  |
+| **message** | **String** | Message d'erreur |  |
+| **suggested_value** | **String** |  | [optional] |
+| **suggested_field** | **String** |  | [optional] |
+| **explanation** | **String** |  | [optional] |
+| **confidence** | **Float** |  | [optional] |
+
+## Example
+
+```ruby
+require 'factpulse'
+
+instance = FactPulse::FactureElectroniqueRestApiSchemasConvertValidationError.new(
+  rule: null,
+  bt_code: null,
+  severity: null,
+  message: null,
+  suggested_value: null,
+  suggested_field: null,
+  explanation: null,
+  confidence: null
+)
+```
+

data/docs/FlowSummary.md

@@ -4,9 +4,9 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **flow_id** | **String** |  |  |
+| **flow_id** | **String** | Unique flow identifier |  |
 | **tracking_id** | **String** |  | [optional] |
-| **name** | **String** |  |  |
+| **name** | **String** | Flow name |  |
 | **flow_type** | **String** |  | [optional] |
 | **flow_direction** | **String** |  | [optional] |
 | **acknowledgment_status** | **String** |  | [optional] |

data/docs/GenerateAggregatedReportResponse.md

@@ -0,0 +1,30 @@
+# FactPulse::GenerateAggregatedReportResponse
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **report_id** | **String** | Report identifier |  |
+| **transmission_type** | **String** | Transmission type (IN or RE) |  |
+| **flow_type** | **String** | AFNOR FlowType determined from content |  |
+| **xml** | **String** | Generated XML content |  |
+| **xml_size** | **Integer** | XML size in bytes |  |
+| **content_summary** | **Hash<String, Object>** | Summary of content (counts by flux type) |  |
+| **message** | **String** | Status message |  |
+
+## Example
+
+```ruby
+require 'factpulse'
+
+instance = FactPulse::GenerateAggregatedReportResponse.new(
+  report_id: null,
+  transmission_type: null,
+  flow_type: null,
+  xml: null,
+  xml_size: null,
+  content_summary: null,
+  message: null
+)
+```
+

data/docs/GenerateEReportingResponse.md

@@ -0,0 +1,26 @@
+# FactPulse::GenerateEReportingResponse
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **report_id** | **String** | Report identifier |  |
+| **flow_type** | **String** | Flux type |  |
+| **xml** | **String** | Generated XML content |  |
+| **xml_size** | **Integer** | XML size in bytes |  |
+| **message** | **String** | Status message |  |
+
+## Example
+
+```ruby
+require 'factpulse'
+
+instance = FactPulse::GenerateEReportingResponse.new(
+  report_id: null,
+  flow_type: null,
+  xml: null,
+  xml_size: null,
+  message: null
+)
+```
+

data/docs/GetChorusProIdRequest.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **credentials** | [**FactureElectroniqueRestApiSchemasChorusProChorusProCredentials**](FactureElectroniqueRestApiSchemasChorusProChorusProCredentials.md) |  | [optional] |
+| **credentials** | [**ChorusProCredentials**](ChorusProCredentials.md) |  | [optional] |
 | **siret** | **String** | Structure SIRET (14 digits) |  |
 | **identifier_type** | **String** | Identifier type (SIRET, SIREN, UE_HORS_FRANCE, etc.) | [optional][default to 'SIRET'] |
 

data/docs/GetInvoiceRequest.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **credentials** | [**FactureElectroniqueRestApiSchemasChorusProChorusProCredentials**](FactureElectroniqueRestApiSchemasChorusProChorusProCredentials.md) |  | [optional] |
+| **credentials** | [**ChorusProCredentials**](ChorusProCredentials.md) |  | [optional] |
 | **chorus_invoice_id** | **Integer** | Chorus Pro invoice ID |  |
 
 ## Example

data/docs/GetInvoiceResponse.md

@@ -4,8 +4,8 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **return_code** | **Integer** |  |  |
-| **message** | **String** |  |  |
+| **return_code** | **Integer** | Return code (0 = success) |  |
+| **message** | **String** | Response message |  |
 | **chorus_invoice_id** | **Integer** |  | [optional] |
 | **invoice_number** | **String** |  | [optional] |
 | **invoice_date** | **String** |  | [optional] |

data/docs/GetStructureRequest.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **credentials** | [**FactureElectroniqueRestApiSchemasChorusProChorusProCredentials**](FactureElectroniqueRestApiSchemasChorusProChorusProCredentials.md) |  | [optional] |
+| **credentials** | [**ChorusProCredentials**](ChorusProCredentials.md) |  | [optional] |
 | **structure_id** | **Integer** | Chorus Pro structure ID |  |
 | **language_code** | **String** | Language code (fr, en) | [optional][default to 'fr'] |
 

data/docs/GetStructureResponse.md

@@ -4,8 +4,8 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **return_code** | **Integer** |  |  |
-| **message** | **String** |  |  |
+| **return_code** | **Integer** | Return code (0 = success) |  |
+| **message** | **String** | Response message |  |
 | **structure_id** | **Integer** |  | [optional] |
 | **structure_identifier** | **String** |  | [optional] |
 | **structure_label** | **String** |  | [optional] |

data/docs/HealthApi.md

@@ -1,6 +1,6 @@
 # FactPulse::HealthApi
 
-All URIs are relative to *http://localhost*
+All URIs are relative to *https://factpulse.fr*
 
 | Method | HTTP request | Description |
 | ------ | ------------ | ----------- |

data/docs/IncomingInvoice.md

@@ -7,7 +7,7 @@
 | **flow_id** | **String** |  | [optional] |
 | **source_format** | [**InvoiceFormat**](InvoiceFormat.md) | Invoice source format |  |
 | **supplier_reference** | **String** | Invoice number issued by the supplier (BT-1) |  |
-| **document_type** | [**InvoiceTypeCode**](InvoiceTypeCode.md) | Document type (BT-3) | [optional] |
+| **document_type** | [**InvoiceTypeCodeOutput**](InvoiceTypeCodeOutput.md) | Document type (BT-3) | [optional] |
 | **supplier** | [**IncomingSupplier**](IncomingSupplier.md) | Invoice issuer (SellerTradeParty) |  |
 | **billing_site_name** | **String** | Recipient name / your company (BT-44) |  |
 | **billing_site_siret** | **String** |  | [optional] |

data/docs/InvoiceInput.md

@@ -0,0 +1,48 @@
+# FactPulse::InvoiceInput
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **invoice_id** | **String** | Invoice identifier |  |
+| **issue_date** | **Date** | Invoice issue date |  |
+| **type_code** | [**InvoiceTypeCode**](InvoiceTypeCode.md) | Invoice type code | [optional] |
+| **currency** | [**Currency**](Currency.md) |  | [optional] |
+| **due_date** | **Date** |  | [optional] |
+| **seller_siren** | **String** | Seller SIREN/SIRET |  |
+| **seller_vat_id** | **String** |  | [optional] |
+| **seller_country** | [**Sellercountry**](Sellercountry.md) |  | [optional] |
+| **buyer_id** | **String** |  | [optional] |
+| **buyer_vat_id** | **String** |  | [optional] |
+| **buyer_country** | [**Buyercountry**](Buyercountry.md) |  |  |
+| **tax_exclusive_amount** | [**Taxexclusiveamount1**](Taxexclusiveamount1.md) |  |  |
+| **tax_amount** | [**Taxamount1**](Taxamount1.md) |  |  |
+| **tax_breakdown** | [**Array<TaxBreakdownInput>**](TaxBreakdownInput.md) | VAT breakdown |  |
+| **referenced_invoice_id** | **String** |  | [optional] |
+| **referenced_invoice_date** | **Date** |  | [optional] |
+
+## Example
+
+```ruby
+require 'factpulse'
+
+instance = FactPulse::InvoiceInput.new(
+  invoice_id: FAC-2025-001,
+  issue_date: 2025-01-15,
+  type_code: null,
+  currency: null,
+  due_date: null,
+  seller_siren: 123456789,
+  seller_vat_id: null,
+  seller_country: null,
+  buyer_id: null,
+  buyer_vat_id: null,
+  buyer_country: null,
+  tax_exclusive_amount: null,
+  tax_amount: null,
+  tax_breakdown: null,
+  referenced_invoice_id: null,
+  referenced_invoice_date: null
+)
+```
+

data/docs/InvoiceLine.md

@@ -6,6 +6,8 @@
 | ---- | ---- | ----------- | ----- |
 | **line_number** | **Integer** | Invoice line identifier (BT-126). |  |
 | **line_note** | **String** |  | [optional] |
+| **parent_line_id** | **String** |  | [optional] |
+| **line_sub_type** | [**LineSubType**](LineSubType.md) |  | [optional] |
 | **reference** | **String** |  | [optional] |
 | **buyer_assigned_id** | **String** |  | [optional] |
 | **product_global_id** | **String** |  | [optional] |
@@ -45,6 +47,8 @@ require 'factpulse'
 instance = FactPulse::InvoiceLine.new(
   line_number: null,
   line_note: null,
+  parent_line_id: null,
+  line_sub_type: null,
   reference: null,
   buyer_assigned_id: null,
   product_global_id: null,

data/docs/InvoiceNote.md

@@ -5,7 +5,7 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **subject_code** | **String** |  | [optional] |
-| **content** | **String** |  |  |
+| **content** | **String** | Note content |  |
 
 ## Example
 

data/docs/InvoicePaymentInput.md

@@ -0,0 +1,26 @@
+# FactPulse::InvoicePaymentInput
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **invoice_id** | **String** | Invoice identifier |  |
+| **invoice_date** | **Date** | Original invoice date |  |
+| **payment_date** | **Date** | Payment date |  |
+| **currency** | [**Currency**](Currency.md) |  | [optional] |
+| **amounts_by_rate** | [**Array<PaymentAmountByRate>**](PaymentAmountByRate.md) | Payment amounts by VAT rate |  |
+
+## Example
+
+```ruby
+require 'factpulse'
+
+instance = FactPulse::InvoicePaymentInput.new(
+  invoice_id: FAC-2025-001,
+  invoice_date: 2025-01-15,
+  payment_date: 2025-01-25,
+  currency: null,
+  amounts_by_rate: null
+)
+```
+

data/docs/InvoiceProcessingApi.md

@@ -1,6 +1,6 @@
 # FactPulse::InvoiceProcessingApi
 
-All URIs are relative to *http://localhost*
+All URIs are relative to *https://factpulse.fr*
 
 | Method | HTTP request | Description |
 | ------ | ------------ | ----------- |
@@ -23,7 +23,7 @@ All URIs are relative to *http://localhost*
 
 Generate a Factur-X invoice
 
-Generates an electronic invoice in Factur-X format compliant with European standards.  ## Applied Standards  - **Factur-X** (France): FNFE-MPE standard (Forum National de la Facture Électronique) - **ZUGFeRD** (Germany): German format compatible with Factur-X - **EN 16931**: European semantic standard for electronic invoicing - **ISO 19005-3** (PDF/A-3): Long-term electronic archiving - **Cross Industry Invoice (CII)**: UN/CEFACT XML syntax  ## 🆕 New: Simplified format with auto-enrichment (P0.1)  You can now create an invoice by providing only: - An invoice number - A sender SIRET + **IBAN** (required) - A recipient SIRET - Invoice lines (description, quantity, net price)  **Simplified format example**: ```json {   \"number\": \"FACT-2025-001\",   \"sender\": {     \"siret\": \"92019522900017\",     \"iban\": \"FR7630001007941234567890185\"   },   \"recipient\": {\"siret\": \"35600000000048\"},   \"lines\": [     {\"description\": \"Service\", \"quantity\": 10, \"unitPrice\": 100.00, \"vatRate\": 20.0}   ] } ```  **⚠️ Required fields (simplified format)**: - `number`: Unique invoice number - `sender.siret`: Sender's SIRET (14 digits) - `sender.iban`: Bank account IBAN (no public API to retrieve it) - `recipient.siret`: Recipient's SIRET - `lines[]`: At least one invoice line  **What happens automatically with `auto_enrich=True`**: - ✅ Name enrichment from Chorus Pro API - ✅ Address enrichment from Business Search API (free, public) - ✅ Automatic intra-EU VAT calculation (FR + key + SIREN) - ✅ Chorus Pro ID retrieval for electronic invoicing - ✅ Net/VAT/Gross totals calculation - ✅ Date generation (today + 30-day due date) - ✅ Multi-rate VAT handling  **Supported identifiers**: - SIRET (14 digits): Specific establishment ⭐ Recommended - SIREN (9 digits): Company (auto-selection of headquarters) - Special types: UE_HORS_FRANCE, RIDET, TAHITI, etc.  ## Checks performed during generation  ### 1. Data validation (Pydantic) - Data types (amounts as Decimal, ISO 8601 dates) - Formats (14-digit SIRET, 9-digit SIREN, IBAN) - Required fields per profile - Amount consistency (Net + VAT = Gross)  ### 2. CII-compliant XML generation - Serialization according to Cross Industry Invoice XSD schema - Correct UN/CEFACT namespaces - Hierarchical structure respected - UTF-8 encoding without BOM  ### 3. Schematron validation - Business rules for selected profile (MINIMUM, BASIC, EN16931, EXTENDED) - Element cardinality (required, optional, repeatable) - Calculation rules (totals, VAT, discounts) - European EN 16931 compliance  ### 4. PDF/A-3 conversion (if output_format='pdf') - Source PDF conversion to PDF/A-3 via Ghostscript - Factur-X XML embedding in PDF - Compliant XMP metadata - ICC sRGB color profile - Removal of forbidden elements (JavaScript, forms)  ## How it works  1. **Submission**: Invoice is queued in Celery for asynchronous processing 2. **Immediate return**: You receive a `task_id` (HTTP 202 Accepted) 3. **Tracking**: Use the `/tasks/{task_id}/status` endpoint to track progress  ## Output formats  - **xml**: Generates only Factur-X XML (recommended for testing) - **pdf**: Generates PDF/A-3 with embedded XML (requires `source_pdf`)  ## Factur-X profiles  - **MINIMUM**: Minimal data (simplified invoice) - **BASIC**: Basic information (SMEs) - **EN16931**: European standard (recommended, compliant with directive 2014/55/EU) - **EXTENDED**: All available data (large accounts)  ## What you get  After successful processing (status `completed`): - **XML only**: Base64-encoded Factur-X compliant XML file - **PDF/A-3**: PDF with embedded XML, ready for sending/archiving - **Metadata**: Profile, Factur-X version, file size - **Validation**: Schematron compliance confirmation  ## Validation  Data is automatically validated according to detected format. On error, a 422 status is returned with invalid field details.
+Generates an electronic invoice in Factur-X format compliant with European standards.  ## Applied Standards  - **Factur-X** (France): FNFE-MPE standard (Forum National de la Facture Électronique) - **ZUGFeRD** (Germany): German format compatible with Factur-X - **EN 16931**: European semantic standard for electronic invoicing - **ISO 19005-3** (PDF/A-3): Long-term electronic archiving - **Cross Industry Invoice (CII)**: UN/CEFACT XML syntax  ## 🆕 New: Simplified format with auto-enrichment (P0.1)  You can now create an invoice by providing only: - An invoice number - A supplier SIRET + **IBAN** (required) - A recipient SIRET - Invoice lines (description, quantity, net price)  **Simplified format example**: ```json {   \"number\": \"FACT-2025-001\",   \"supplier\": {     \"siret\": \"92019522900017\",     \"iban\": \"FR7630001007941234567890185\"   },   \"recipient\": {\"siret\": \"35600000000048\"},   \"lines\": [     {\"description\": \"Service\", \"quantity\": 10, \"unitPrice\": 100.00, \"vatRate\": 20.0}   ] } ```  **⚠️ Required fields (simplified format)**: - `number`: Unique invoice number - `supplier.siret`: Supplier's SIRET (14 digits) - `supplier.iban`: Bank account IBAN (no public API to retrieve it) - `recipient.siret`: Recipient's SIRET - `lines[]`: At least one invoice line  **What happens automatically with `auto_enrich=True`**: - ✅ Name enrichment from Chorus Pro API - ✅ Address enrichment from Business Search API (free, public) - ✅ Automatic intra-EU VAT calculation (FR + key + SIREN) - ✅ Chorus Pro ID retrieval for electronic invoicing - ✅ Net/VAT/Gross totals calculation - ✅ Date generation (today + 30-day due date) - ✅ Multi-rate VAT handling  **Supported identifiers**: - SIRET (14 digits): Specific establishment ⭐ Recommended - SIREN (9 digits): Company (auto-selection of headquarters) - Special types: UE_HORS_FRANCE, RIDET, TAHITI, etc.  ## Checks performed during generation  ### 1. Data validation (Pydantic) - Data types (amounts as Decimal, ISO 8601 dates) - Formats (14-digit SIRET, 9-digit SIREN, IBAN) - Required fields per profile - Amount consistency (Net + VAT = Gross)  ### 2. CII-compliant XML generation - Serialization according to Cross Industry Invoice XSD schema - Correct UN/CEFACT namespaces - Hierarchical structure respected - UTF-8 encoding without BOM  ### 3. Schematron validation - Business rules for selected profile (MINIMUM, BASIC, EN16931, EXTENDED) - Element cardinality (required, optional, repeatable) - Calculation rules (totals, VAT, discounts) - European EN 16931 compliance  ### 4. PDF/A-3 conversion (if output_format='pdf') - Source PDF conversion to PDF/A-3 via Ghostscript - Factur-X XML embedding in PDF - Compliant XMP metadata - ICC sRGB color profile - Removal of forbidden elements (JavaScript, forms)  ## How it works  1. **Submission**: Invoice is queued in Celery for asynchronous processing 2. **Immediate return**: You receive a `task_id` (HTTP 202 Accepted) 3. **Tracking**: Use the `/tasks/{task_id}/status` endpoint to track progress  ## Webhook notification (recommended)  Instead of polling, you can receive a webhook notification when the task completes:  ``` callback_url=https://your-server.com/webhook ```  The webhook will POST a JSON payload with: - `event_type`: `generation.completed` or `generation.failed` - `data.task_id`: The Celery task ID - `data.content_b64` or `data.xml_content`: The generated content - `X-Webhook-Signature` header for HMAC verification  See `/docs/WEBHOOKS.md` for full documentation.  ## Output formats  - **xml**: Generates only Factur-X XML (recommended for testing) - **pdf**: Generates PDF/A-3 with embedded XML (requires `source_pdf`)  ## Factur-X profiles  - **MINIMUM**: Minimal data (simplified invoice) - **BASIC**: Basic information (SMEs) - **EN16931**: European standard (recommended, compliant with directive 2014/55/EU) - **EXTENDED**: All available data (large accounts)  ## What you get  After successful processing (status `completed`): - **XML only**: Base64-encoded Factur-X compliant XML file - **PDF/A-3**: PDF with embedded XML, ready for sending/archiving - **Metadata**: Profile, Factur-X version, file size - **Validation**: Schematron compliance confirmation  ## Validation  Data is automatically validated according to detected format. On error, a 422 status is returned with invalid field details.
 
 ### Examples
 
@@ -37,12 +37,15 @@ FactPulse.configure do |config|
 end
 
 api_instance = FactPulse::InvoiceProcessingApi.new
-invoice_data = 'invoice_data_example' # String | Invoice data in JSON format.              Two formats accepted:             1. **Classic format**: Complete FactureFacturX structure (all fields)             2. **Simplified format** (🆕 P0.1): Minimal structure with auto-enrichment              Format is detected automatically!             
+invoice_data = 'invoice_data_example' # String | Invoice data in JSON format.              Two formats accepted:             1. **Classic format**: Complete FacturXInvoice structure (all fields)             2. **Simplified format** (🆕 P0.1): Minimal structure with auto-enrichment              Format is detected automatically!             
 opts = {
   profile: FactPulse::APIProfile::MINIMUM, # APIProfile | Factur-X profile: MINIMUM, BASIC, EN16931 or EXTENDED.
   output_format: FactPulse::OutputFormat::XML, # OutputFormat | Output format: 'xml' (XML only) or 'pdf' (Factur-X PDF with embedded XML).
   auto_enrich: true, # Boolean | 🆕 Enable auto-enrichment from SIRET/SIREN (simplified format only)
-  source_pdf: File.new('/path/to/some/file') # File | 
+  source_pdf: File.new('/path/to/some/file'), # File | 
+  callback_url: 'callback_url_example', # String | 
+  webhook_mode: 'webhook_mode_example', # String | Webhook content delivery: 'inline' (base64 in payload) or 'download_url' (temporary URL, 1h TTL)
+  skip_br_fr: true # Boolean | 
 }
 
 begin
@@ -76,11 +79,14 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **invoice_data** | **String** | Invoice data in JSON format.              Two formats accepted:             1. **Classic format**: Complete FactureFacturX structure (all fields)             2. **Simplified format** (🆕 P0.1): Minimal structure with auto-enrichment              Format is detected automatically!              |  |
+| **invoice_data** | **String** | Invoice data in JSON format.              Two formats accepted:             1. **Classic format**: Complete FacturXInvoice structure (all fields)             2. **Simplified format** (🆕 P0.1): Minimal structure with auto-enrichment              Format is detected automatically!              |  |
 | **profile** | [**APIProfile**](APIProfile.md) | Factur-X profile: MINIMUM, BASIC, EN16931 or EXTENDED. | [optional] |
 | **output_format** | [**OutputFormat**](OutputFormat.md) | Output format: 'xml' (XML only) or 'pdf' (Factur-X PDF with embedded XML). | [optional] |
 | **auto_enrich** | **Boolean** | 🆕 Enable auto-enrichment from SIRET/SIREN (simplified format only) | [optional][default to true] |
 | **source_pdf** | **File** |  | [optional] |
+| **callback_url** | **String** |  | [optional] |
+| **webhook_mode** | **String** | Webhook content delivery: 'inline' (base64 in payload) or 'download_url' (temporary URL, 1h TTL) | [optional][default to 'inline'] |
+| **skip_br_fr** | **Boolean** |  | [optional] |
 
 ### Return type
 
@@ -102,7 +108,7 @@ end
 
 Generate a self-signed X.509 test certificate
 
-Generates a self-signed X.509 certificate for PDF electronic signature testing.      **⚠️ WARNING: TEST certificate only!**      This certificate is:     - ✅ Suitable for testing and development     - ✅ Compatible with PDF signing (PAdES)     - ✅ Compliant with eIDAS **SES** level (Simple Electronic Signature)     - ❌ **NEVER usable in production**     - ❌ **Not recognized** by browsers and PDF readers     - ❌ **No legal value**      ## eIDAS levels      - **SES** (Simple): Self-signed certificate ← Generated by this endpoint     - **AdES** (Advanced): Commercial CA certificate (Let's Encrypt, etc.)     - **QES** (Qualified): Qualified certificate from QTSP (CertEurope, Universign, etc.)      ## Usage      Once generated, the certificate can be:      1. **Saved in Django** (recommended):        - Django Admin > Signing Certificates        - Upload `certificate_pem` and `private_key_pem`      2. **Used directly**:        - Sign a PDF with `/sign-pdf`        - The certificate will be automatically used      ## Example call      ```bash     curl -X POST \"https://www.factpulse.fr/api/v1/processing/generate-test-certificate\" \\       -H \"Authorization: Bearer eyJ0eXAi...\" \\       -H \"Content-Type: application/json\" \\       -d '{         \"cn\": \"Test Client XYZ\",         \"organization\": \"Client XYZ Ltd\",         \"email\": \"contact@xyz.com\",         \"validity_days\": 365       }'     ```      ## Use cases      - PDF signature testing in development     - Electronic signature POC     - Training and demos     - Automated integration tests      ## Technical compliance      Certificate generated with:     - RSA key 2048 or 4096 bits     - SHA-256 algorithm     - Key Usage extensions: `digitalSignature`, `contentCommitment` (non-repudiation)     - Extended Key Usage extensions: `codeSigning`, `emailProtection`     - Validity: 1 day to 10 years (configurable)     - Format: PEM (certificate and key)     - Optional: PKCS#12 (.p12)
+Generates a self-signed X.509 certificate for PDF electronic signature testing.      **⚠️ WARNING: TEST certificate only!**      This certificate is:     - ✅ Suitable for testing and development     - ✅ Compatible with PDF signing (PAdES)     - ✅ Compliant with eIDAS **SES** level (Simple Electronic Signature)     - ❌ **NEVER usable in production**     - ❌ **Not recognized** by browsers and PDF readers     - ❌ **No legal value**      ## eIDAS levels      - **SES** (Simple): Self-signed certificate ← Generated by this endpoint     - **AdES** (Advanced): Commercial CA certificate (Let's Encrypt, etc.)     - **QES** (Qualified): Qualified certificate from QTSP (CertEurope, Universign, etc.)      ## Usage      Once generated, the certificate can be:      1. **Saved in Django** (recommended):        - Django Admin > Signing Certificates        - Upload `certificate_pem` and `private_key_pem`      2. **Used directly**:        - Sign a PDF with `/sign-pdf`        - The certificate will be automatically used      ## Example call      ```bash     curl -X POST \"https://factpulse.fr/api/v1/processing/generate-test-certificate\" \\       -H \"Authorization: Bearer eyJ0eXAi...\" \\       -H \"Content-Type: application/json\" \\       -d '{         \"cn\": \"Test Client XYZ\",         \"organization\": \"Client XYZ Ltd\",         \"email\": \"contact@xyz.com\",         \"validity_days\": 365       }'     ```      ## Use cases      - PDF signature testing in development     - Electronic signature POC     - Training and demos     - Automated integration tests      ## Technical compliance      Certificate generated with:     - RSA key 2048 or 4096 bits     - SHA-256 algorithm     - Key Usage extensions: `digitalSignature`, `contentCommitment` (non-repudiation)     - Extended Key Usage extensions: `codeSigning`, `emailProtection`     - Validity: 1 day to 10 years (configurable)     - Format: PEM (certificate and key)     - Optional: PKCS#12 (.p12)
 
 ### Examples
 
@@ -185,7 +191,7 @@ FactPulse.configure do |config|
 end
 
 api_instance = FactPulse::InvoiceProcessingApi.new
-task_id = 'task_id_example' # String | 
+task_id = 'task_id_example' # String | Celery task ID returned by async endpoints (UUID format)
 
 begin
   # Get task generation status
@@ -218,7 +224,7 @@ end
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **task_id** | **String** |  |  |
+| **task_id** | **String** | Celery task ID returned by async endpoints (UUID format) |  |
 
 ### Return type
 
@@ -339,6 +345,8 @@ end
 api_instance = FactPulse::InvoiceProcessingApi.new
 pdf_file = File.new('/path/to/some/file') # File | PDF file to sign (processed asynchronously)
 opts = {
+  callback_url: 'callback_url_example', # String | 
+  webhook_mode: 'webhook_mode_example', # String | Webhook content delivery: 'inline' (base64 in payload) or 'download_url' (temporary URL, 1h TTL)
   reason: 'reason_example', # String | 
   location: 'location_example', # String | 
   contact: 'contact_example', # String | 
@@ -379,6 +387,8 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **pdf_file** | **File** | PDF file to sign (processed asynchronously) |  |
+| **callback_url** | **String** |  | [optional] |
+| **webhook_mode** | **String** | Webhook content delivery: 'inline' (base64 in payload) or 'download_url' (temporary URL, 1h TTL) | [optional][default to 'inline'] |
 | **reason** | **String** |  | [optional] |
 | **location** | **String** |  | [optional] |
 | **contact** | **String** |  | [optional] |
@@ -471,11 +481,11 @@ end
 
 ## submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post
 
-> <TaskResponse> submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post(submit_complete_invoice_request)
+> <TaskResponse> submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post(submit_complete_invoice_request, opts)
 
 Submit a complete invoice (asynchronous with Celery)
 
-Asynchronous version of the `/invoices/submit-complete` endpoint using Celery for background processing.      **Automated workflow (same as synchronous version):**     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      **Differences with synchronous version:**     - ✅ **Non-blocking**: Returns immediately with a `task_id` (HTTP 202 Accepted)     - ✅ **Background processing**: Invoice is processed by a Celery worker     - ✅ **Progress tracking**: Use `/tasks/{task_id}/status` to track status     - ✅ **Ideal for high volumes**: Allows processing many invoices in parallel      **How to use:**     1. **Submission**: Call this endpoint with your invoice data     2. **Immediate return**: You receive a `task_id` (e.g., \"abc123-def456\")     3. **Tracking**: Call `/tasks/{task_id}/status` to check progress     4. **Result**: When `status = \"SUCCESS\"`, the `result` field contains the complete response      **Credentials and signature**: Same modes as the synchronous version (JWT or payload).
+Asynchronous version of the `/invoices/submit-complete` endpoint using Celery for background processing.      **Automated workflow (same as synchronous version):**     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      **Differences with synchronous version:**     - ✅ **Non-blocking**: Returns immediately with a `task_id` (HTTP 202 Accepted)     - ✅ **Background processing**: Invoice is processed by a Celery worker     - ✅ **Progress tracking**: Use `/tasks/{task_id}/status` to track status     - ✅ **Ideal for high volumes**: Allows processing many invoices in parallel      **How to use:**     1. **Submission**: Call this endpoint with your invoice data     2. **Immediate return**: You receive a `task_id` (e.g., \"abc123-def456\")     3. **Tracking**: Call `/tasks/{task_id}/status` to check progress     4. **Result**: When `status = \"SUCCESS\"`, the `result` field contains the complete response      **Webhook notification (recommended):**      Instead of polling, add `?callback_url=https://your-server.com/webhook` to receive automatic notification:     - `event_type`: `submission.completed`, `submission.failed`, or `submission.partial`     - `data.submission_result`: Complete submission result     - `X-Webhook-Signature` header for HMAC verification      **Credentials and signature**: Same modes as the synchronous version (JWT or payload).
 
 ### Examples
 
@@ -490,10 +500,14 @@ end
 
 api_instance = FactPulse::InvoiceProcessingApi.new
 submit_complete_invoice_request = FactPulse::SubmitCompleteInvoiceRequest.new({invoice_data: FactPulse::SimplifiedInvoiceData.new({number: 'number_example', supplier: { key: 3.56}, recipient: { key: 3.56}, lines: [{ key: 3.56}]}), source_pdf: 'source_pdf_example', destination: FactPulse::AFNORDestination.new}) # SubmitCompleteInvoiceRequest | 
+opts = {
+  callback_url: 'callback_url_example', # String | Webhook URL for async notification when submission completes.
+  webhook_mode: 'webhook_mode_example' # String | Webhook content delivery: 'inline' (base64 in payload) or 'download_url' (temporary URL, 1h TTL)
+}
 
 begin
   # Submit a complete invoice (asynchronous with Celery)
-  result = api_instance.submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post(submit_complete_invoice_request)
+  result = api_instance.submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post(submit_complete_invoice_request, opts)
   p result
 rescue FactPulse::ApiError => e
   puts "Error when calling InvoiceProcessingApi->submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post: #{e}"
@@ -504,12 +518,12 @@ end
 
 This returns an Array which contains the response data, status code and headers.
 
-> <Array(<TaskResponse>, Integer, Hash)> submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post_with_http_info(submit_complete_invoice_request)
+> <Array(<TaskResponse>, Integer, Hash)> submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post_with_http_info(submit_complete_invoice_request, opts)
 
 ```ruby
 begin
   # Submit a complete invoice (asynchronous with Celery)
-  data, status_code, headers = api_instance.submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post_with_http_info(submit_complete_invoice_request)
+  data, status_code, headers = api_instance.submit_complete_invoice_async_api_v1_processing_invoices_submit_complete_async_post_with_http_info(submit_complete_invoice_request, opts)
   p status_code # => 2xx
   p headers # => { ... }
   p data # => <TaskResponse>
@@ -523,6 +537,8 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **submit_complete_invoice_request** | [**SubmitCompleteInvoiceRequest**](SubmitCompleteInvoiceRequest.md) |  |  |
+| **callback_url** | **String** | Webhook URL for async notification when submission completes. | [optional] |
+| **webhook_mode** | **String** | Webhook content delivery: &#39;inline&#39; (base64 in payload) or &#39;download_url&#39; (temporary URL, 1h TTL) | [optional][default to &#39;inline&#39;] |
 
 ### Return type
 
@@ -561,7 +577,8 @@ api_instance = FactPulse::InvoiceProcessingApi.new
 pdf_file = File.new('/path/to/some/file') # File | Factur-X PDF file to validate (.pdf format).
 opts = {
   profile: FactPulse::APIProfile::MINIMUM, # APIProfile | 
-  use_verapdf: true # Boolean | Enable strict PDF/A validation with VeraPDF (recommended for production). If False, uses basic metadata validation.
+  use_verapdf: true, # Boolean | Enable strict PDF/A validation with VeraPDF (recommended for production). If False, uses basic metadata validation.
+  skip_br_fr: true # Boolean | 
 }
 
 begin
@@ -598,6 +615,7 @@ end
 | **pdf_file** | **File** | Factur-X PDF file to validate (.pdf format). |  |
 | **profile** | [**APIProfile**](APIProfile.md) |  | [optional] |
 | **use_verapdf** | **Boolean** | Enable strict PDF/A validation with VeraPDF (recommended for production). If False, uses basic metadata validation. | [optional][default to false] |
+| **skip_br_fr** | **Boolean** |  | [optional] |
 
 ### Return type
 
@@ -619,7 +637,7 @@ end
 
 Validate a Factur-X PDF (asynchronous with polling)
 
-Validates a Factur-X PDF asynchronously with polling system.  ## How it works  1. **Submission**: PDF is queued for asynchronous validation 2. **Immediate return**: You receive a `task_id` (HTTP 202) 3. **Tracking**: Use the `/tasks/{task_id}/status` endpoint to track progress  ## Advantages of asynchronous mode  - **No timeout**: Ideal for large PDFs or VeraPDF validation (which can take several seconds) - **Scalability**: Validations are processed by dedicated Celery workers - **Status tracking**: Allows you to monitor validation progress - **Non-blocking**: Your client doesn't wait during validation  ## When to use this mode?  - **VeraPDF validation enabled** (`use_verapdf=True`): Strict validation can take 2-10 seconds - **Large PDF files**: PDFs > 1 MB - **Batch processing**: Validating multiple invoices in parallel - **Asynchronous integration**: Your system supports polling  ## Checks performed  ### 1. Factur-X XML extraction and validation - Verifies presence of Factur-X compliant embedded XML file - Automatically detects profile used (MINIMUM, BASIC, EN16931, EXTENDED) - Validates XML against detected profile's Schematron rules  ### 2. PDF/A compliance - **Without VeraPDF**: Basic metadata validation (fast, ~100ms) - **With VeraPDF**: Strict ISO 19005 validation (146+ rules, 2-10s)   - Detects PDF/A version (PDF/A-1, PDF/A-3, etc.)   - Detailed non-compliance reports  ### 3. XMP metadata - Verifies presence of XMP metadata in PDF - Validates Factur-X metadata compliance (profile, version) - Extracts all available XMP metadata  ### 4. Electronic signatures - Detects presence of electronic signatures or seals - Extracts information about each signature (signer, date, reason) - Counts number of signatures present  ## Parameters  - **pdf_file**: The Factur-X PDF file to validate - **profile**: Expected Factur-X profile (optional). If not specified, profile   will be auto-detected from embedded XML file. - **use_verapdf**: Enable strict PDF/A validation with VeraPDF.   ⚠️ **Warning**: VeraPDF can take 2-10 seconds depending on PDF size.   Recommended only in asynchronous mode to avoid timeouts.  ## Retrieving results  After submission, use `GET /tasks/{task_id}/status` endpoint to retrieve the result.  **Polling example**: ```python import requests import time  # 1. Submit task response = requests.post(\"/validate-facturx-async\", files={\"pdf_file\": pdf_file}) task_id = response.json()[\"taskId\"]  # 2. Poll every 2 seconds while True:     status_response = requests.get(f\"/tasks/{task_id}/status\")     status = status_response.json()      if status[\"status\"] == \"SUCCESS\":         result = status[\"result\"][\"validation_result\"]         print(f\"Compliant: {result['is_compliant']}\")         break     elif status[\"status\"] == \"FAILURE\":         print(f\"Error: {status['result']['errorMessage']}\")         break      time.sleep(2)  # Wait 2 seconds before next check ```  ## Use cases  - Validate invoices before sending with VeraPDF (strict validation) - Process invoice batches in parallel - Integrate validation into an asynchronous pipeline - Validate large PDFs without timeout risk
+Validates a Factur-X PDF asynchronously with polling system.  ## How it works  1. **Submission**: PDF is queued for asynchronous validation 2. **Immediate return**: You receive a `task_id` (HTTP 202) 3. **Tracking**: Use the `/tasks/{task_id}/status` endpoint to track progress  ## Advantages of asynchronous mode  - **No timeout**: Ideal for large PDFs or VeraPDF validation (which can take several seconds) - **Scalability**: Validations are processed by dedicated Celery workers - **Status tracking**: Allows you to monitor validation progress - **Non-blocking**: Your client doesn't wait during validation  ## Webhook notification (recommended)  Instead of polling, you can receive a webhook notification when validation completes:  ``` callback_url=https://your-server.com/webhook webhook_mode=download_url  # Optional: get download URL instead of base64 ```  The webhook will POST a JSON payload with: - `event_type`: `validation.completed` or `validation.failed` - `data.is_compliant`: Whether the PDF is Factur-X compliant - `data.detected_profile`: The detected Factur-X profile - `X-Webhook-Signature` header for HMAC verification  ## When to use this mode?  - **VeraPDF validation enabled** (`use_verapdf=True`): Strict validation can take 2-10 seconds - **Large PDF files**: PDFs > 1 MB - **Batch processing**: Validating multiple invoices in parallel - **Asynchronous integration**: Your system supports polling  ## Checks performed  ### 1. Factur-X XML extraction and validation - Verifies presence of Factur-X compliant embedded XML file - Automatically detects profile used (MINIMUM, BASIC, EN16931, EXTENDED) - Validates XML against detected profile's Schematron rules  ### 2. PDF/A compliance - **Without VeraPDF**: Basic metadata validation (fast, ~100ms) - **With VeraPDF**: Strict ISO 19005 validation (146+ rules, 2-10s)   - Detects PDF/A version (PDF/A-1, PDF/A-3, etc.)   - Detailed non-compliance reports  ### 3. XMP metadata - Verifies presence of XMP metadata in PDF - Validates Factur-X metadata compliance (profile, version) - Extracts all available XMP metadata  ### 4. Electronic signatures - Detects presence of electronic signatures or seals - Extracts information about each signature (signer, date, reason) - Counts number of signatures present  ## Parameters  - **pdf_file**: The Factur-X PDF file to validate - **profile**: Expected Factur-X profile (optional). If not specified, profile   will be auto-detected from embedded XML file. - **use_verapdf**: Enable strict PDF/A validation with VeraPDF.   ⚠️ **Warning**: VeraPDF can take 2-10 seconds depending on PDF size.   Recommended only in asynchronous mode to avoid timeouts.  ## Retrieving results  After submission, use `GET /tasks/{task_id}/status` endpoint to retrieve the result.  **Polling example**: ```python import requests import time  # 1. Submit task response = requests.post(\"/validate-facturx-async\", files={\"pdf_file\": pdf_file}) task_id = response.json()[\"taskId\"]  # 2. Poll every 2 seconds while True:     status_response = requests.get(f\"/tasks/{task_id}/status\")     status = status_response.json()      if status[\"status\"] == \"SUCCESS\":         result = status[\"result\"][\"validation_result\"]         print(f\"Compliant: {result['is_compliant']}\")         break     elif status[\"status\"] == \"FAILURE\":         print(f\"Error: {status['result']['errorMessage']}\")         break      time.sleep(2)  # Wait 2 seconds before next check ```  ## Use cases  - Validate invoices before sending with VeraPDF (strict validation) - Process invoice batches in parallel - Integrate validation into an asynchronous pipeline - Validate large PDFs without timeout risk
 
 ### Examples
 
@@ -636,7 +654,9 @@ api_instance = FactPulse::InvoiceProcessingApi.new
 pdf_file = File.new('/path/to/some/file') # File | Factur-X PDF file to validate (.pdf format).
 opts = {
   profile: FactPulse::APIProfile::MINIMUM, # APIProfile | 
-  use_verapdf: true # Boolean | Enable strict PDF/A validation with VeraPDF (recommended for production). May take several seconds.
+  use_verapdf: true, # Boolean | Enable strict PDF/A validation with VeraPDF (recommended for production). May take several seconds.
+  callback_url: 'callback_url_example', # String | 
+  webhook_mode: 'webhook_mode_example' # String | Webhook content delivery: 'inline' (base64 in payload) or 'download_url' (temporary URL, 1h TTL)
 }
 
 begin
@@ -673,6 +693,8 @@ end
 | **pdf_file** | **File** | Factur-X PDF file to validate (.pdf format). |  |
 | **profile** | [**APIProfile**](APIProfile.md) |  | [optional] |
 | **use_verapdf** | **Boolean** | Enable strict PDF/A validation with VeraPDF (recommended for production). May take several seconds. | [optional][default to false] |
+| **callback_url** | **String** |  | [optional] |
+| **webhook_mode** | **String** | Webhook content delivery: &#39;inline&#39; (base64 in payload) or &#39;download_url&#39; (temporary URL, 1h TTL) | [optional][default to &#39;inline&#39;] |
 
 ### Return type
 
@@ -779,7 +801,8 @@ end
 api_instance = FactPulse::InvoiceProcessingApi.new
 xml_file = File.new('/path/to/some/file') # File | Factur-X XML file to validate (.xml format).
 opts = {
-  profile: FactPulse::APIProfile::MINIMUM # APIProfile | Validation profile (MINIMUM, BASIC, EN16931, EXTENDED).
+  profile: FactPulse::APIProfile::MINIMUM, # APIProfile | Validation profile (MINIMUM, BASIC, EN16931, EXTENDED).
+  skip_br_fr: true # Boolean | 
 }
 
 begin
@@ -815,6 +838,7 @@ end
 | ---- | ---- | ----------- | ----- |
 | **xml_file** | **File** | Factur-X XML file to validate (.xml format). |  |
 | **profile** | [**APIProfile**](APIProfile.md) | Validation profile (MINIMUM, BASIC, EN16931, EXTENDED). | [optional] |
+| **skip_br_fr** | **Boolean** |  | [optional] |
 
 ### Return type
 

data/docs/InvoiceTypeCodeOutput.md

@@ -0,0 +1,15 @@
+# FactPulse::InvoiceTypeCodeOutput
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+
+## Example
+
+```ruby
+require 'factpulse'
+
+instance = FactPulse::InvoiceTypeCodeOutput.new()
+```
+

data/docs/InvoicingFramework.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **invoicing_framework_code** | [**InvoicingFrameworkCode**](InvoicingFrameworkCode.md) |  |  |
+| **invoicing_framework_code** | [**InvoicingFrameworkCode**](InvoicingFrameworkCode.md) | Chorus Pro framework code (A1, A2, A9, A12) |  |
 | **operation_nature** | [**OperationNature**](OperationNature.md) |  | [optional] |
 | **approver_service_code** | **String** |  | [optional] |
 | **approver_structure_code** | **String** |  | [optional] |

data/docs/LineSubType.md

@@ -0,0 +1,15 @@
+# FactPulse::LineSubType
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+
+## Example
+
+```ruby
+require 'factpulse'
+
+instance = FactPulse::LineSubType.new()
+```
+