@factpulse/sdk 3.0.9 → 3.0.13

package/docs/InvoiceProcessingApi.md

@@ -1,6 +1,6 @@
 # InvoiceProcessingApi
 
-All URIs are relative to *http://localhost*
+All URIs are relative to *https://factpulse.fr*
 
 |Method | HTTP request | Description|
 |------------- | ------------- | -------------|
@@ -19,7 +19,7 @@ All URIs are relative to *http://localhost*
 # **generateInvoiceApiV1ProcessingGenerateInvoicePost**
 > TaskResponse generateInvoiceApiV1ProcessingGenerateInvoicePost()
 
-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.
 
 ### Example
 
@@ -32,18 +32,24 @@ import {
 const configuration = new Configuration();
 const apiInstance = new InvoiceProcessingApi(configuration);
 
-let invoiceData: 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!              (default to undefined)
+let invoiceData: 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!              (default to undefined)
 let profile: APIProfile; //Factur-X profile: MINIMUM, BASIC, EN16931 or EXTENDED. (optional) (default to undefined)
 let outputFormat: OutputFormat; //Output format: \\\'xml\\\' (XML only) or \\\'pdf\\\' (Factur-X PDF with embedded XML). (optional) (default to undefined)
 let autoEnrich: boolean; //🆕 Enable auto-enrichment from SIRET/SIREN (simplified format only) (optional) (default to true)
 let sourcePdf: File; // (optional) (default to undefined)
+let callbackUrl: string; // (optional) (default to undefined)
+let webhookMode: string; //Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL) (optional) (default to 'inline')
+let skipBrFr: boolean; // (optional) (default to undefined)
 
 const { status, data } = await apiInstance.generateInvoiceApiV1ProcessingGenerateInvoicePost(
     invoiceData,
     profile,
     outputFormat,
     autoEnrich,
-    sourcePdf
+    sourcePdf,
+    callbackUrl,
+    webhookMode,
+    skipBrFr
 );
 ```
 
@@ -51,11 +57,14 @@ const { status, data } = await apiInstance.generateInvoiceApiV1ProcessingGenerat
 
 |Name | Type | Description  | Notes|
 |------------- | ------------- | ------------- | -------------|
-| **invoiceData** | [**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!              | defaults to undefined|
+| **invoiceData** | [**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!              | defaults to undefined|
 | **profile** | **APIProfile** | Factur-X profile: MINIMUM, BASIC, EN16931 or EXTENDED. | (optional) defaults to undefined|
 | **outputFormat** | **OutputFormat** | Output format: \\\'xml\\\' (XML only) or \\\'pdf\\\' (Factur-X PDF with embedded XML). | (optional) defaults to undefined|
 | **autoEnrich** | [**boolean**] | 🆕 Enable auto-enrichment from SIRET/SIREN (simplified format only) | (optional) defaults to true|
 | **sourcePdf** | [**File**] |  | (optional) defaults to undefined|
+| **callbackUrl** | [**string**] |  | (optional) defaults to undefined|
+| **webhookMode** | [**string**] | Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL) | (optional) defaults to 'inline'|
+| **skipBrFr** | [**boolean**] |  | (optional) defaults to undefined|
 
 
 ### Return type
@@ -78,13 +87,14 @@ const { status, data } = await apiInstance.generateInvoiceApiV1ProcessingGenerat
 |**202** | Successful Response |  -  |
 |**400** | Invalid invoice data or missing PDF file |  -  |
 |**422** | Invoice data validation error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
 # **generateTestCertificateApiV1ProcessingGenerateTestCertificatePost**
 > GenerateCertificateResponse generateTestCertificateApiV1ProcessingGenerateTestCertificatePost(generateCertificateRequest)
 
-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)
 
 ### Example
 
@@ -133,6 +143,7 @@ const { status, data } = await apiInstance.generateTestCertificateApiV1Processin
 |**400** | Invalid request (incorrect parameters) |  -  |
 |**500** | Server error during generation |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
@@ -152,7 +163,7 @@ import {
 const configuration = new Configuration();
 const apiInstance = new InvoiceProcessingApi(configuration);
 
-let taskId: string; // (default to undefined)
+let taskId: string; //Celery task ID returned by async endpoints (UUID format) (default to undefined)
 
 const { status, data } = await apiInstance.getTaskStatusApiV1ProcessingTasksTaskIdStatusGet(
     taskId
@@ -163,7 +174,7 @@ const { status, data } = await apiInstance.getTaskStatusApiV1ProcessingTasksTask
 
 |Name | Type | Description  | Notes|
 |------------- | ------------- | ------------- | -------------|
-| **taskId** | [**string**] |  | defaults to undefined|
+| **taskId** | [**string**] | Celery task ID returned by async endpoints (UUID format) | defaults to undefined|
 
 
 ### Return type
@@ -185,6 +196,7 @@ const { status, data } = await apiInstance.getTaskStatusApiV1ProcessingTasksTask
 |-------------|-------------|------------------|
 |**200** | Current task state |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
@@ -279,6 +291,8 @@ const configuration = new Configuration();
 const apiInstance = new InvoiceProcessingApi(configuration);
 
 let pdfFile: File; //PDF file to sign (processed asynchronously) (default to undefined)
+let callbackUrl: string; // (optional) (default to undefined)
+let webhookMode: string; //Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL) (optional) (default to 'inline')
 let reason: string; // (optional) (default to undefined)
 let location: string; // (optional) (default to undefined)
 let contact: string; // (optional) (default to undefined)
@@ -288,6 +302,8 @@ let useTimestamp: boolean; //Enable RFC 3161 timestamping with FreeTSA (PAdES-B-
 
 const { status, data } = await apiInstance.signPdfAsyncApiV1ProcessingSignPdfAsyncPost(
     pdfFile,
+    callbackUrl,
+    webhookMode,
     reason,
     location,
     contact,
@@ -302,6 +318,8 @@ const { status, data } = await apiInstance.signPdfAsyncApiV1ProcessingSignPdfAsy
 |Name | Type | Description  | Notes|
 |------------- | ------------- | ------------- | -------------|
 | **pdfFile** | [**File**] | PDF file to sign (processed asynchronously) | defaults to undefined|
+| **callbackUrl** | [**string**] |  | (optional) defaults to undefined|
+| **webhookMode** | [**string**] | Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL) | (optional) defaults to 'inline'|
 | **reason** | [**string**] |  | (optional) defaults to undefined|
 | **location** | [**string**] |  | (optional) defaults to undefined|
 | **contact** | [**string**] |  | (optional) defaults to undefined|
@@ -385,13 +403,14 @@ const { status, data } = await apiInstance.submitCompleteInvoiceApiV1ProcessingI
 |-------------|-------------|------------------|
 |**200** | Successful Response |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
 # **submitCompleteInvoiceAsyncApiV1ProcessingInvoicesSubmitCompleteAsyncPost**
 > TaskResponse submitCompleteInvoiceAsyncApiV1ProcessingInvoicesSubmitCompleteAsyncPost(submitCompleteInvoiceRequest)
 
-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).
 
 ### Example
 
@@ -406,9 +425,13 @@ const configuration = new Configuration();
 const apiInstance = new InvoiceProcessingApi(configuration);
 
 let submitCompleteInvoiceRequest: SubmitCompleteInvoiceRequest; //
+let callbackUrl: string; //Webhook URL for async notification when submission completes. (optional) (default to undefined)
+let webhookMode: string; //Webhook content delivery: \'inline\' (base64 in payload) or \'download_url\' (temporary URL, 1h TTL) (optional) (default to 'inline')
 
 const { status, data } = await apiInstance.submitCompleteInvoiceAsyncApiV1ProcessingInvoicesSubmitCompleteAsyncPost(
-    submitCompleteInvoiceRequest
+    submitCompleteInvoiceRequest,
+    callbackUrl,
+    webhookMode
 );
 ```
 
@@ -417,6 +440,8 @@ const { status, data } = await apiInstance.submitCompleteInvoiceAsyncApiV1Proces
 |Name | Type | Description  | Notes|
 |------------- | ------------- | ------------- | -------------|
 | **submitCompleteInvoiceRequest** | **SubmitCompleteInvoiceRequest**|  | |
+| **callbackUrl** | [**string**] | Webhook URL for async notification when submission completes. | (optional) defaults to undefined|
+| **webhookMode** | [**string**] | Webhook content delivery: \'inline\' (base64 in payload) or \'download_url\' (temporary URL, 1h TTL) | (optional) defaults to 'inline'|
 
 
 ### Return type
@@ -438,6 +463,7 @@ const { status, data } = await apiInstance.submitCompleteInvoiceAsyncApiV1Proces
 |-------------|-------------|------------------|
 |**202** | Successful Response |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
@@ -460,11 +486,13 @@ const apiInstance = new InvoiceProcessingApi(configuration);
 let pdfFile: File; //Factur-X PDF file to validate (.pdf format). (default to undefined)
 let profile: APIProfile; // (optional) (default to undefined)
 let useVerapdf: boolean; //Enable strict PDF/A validation with VeraPDF (recommended for production). If False, uses basic metadata validation. (optional) (default to false)
+let skipBrFr: boolean; // (optional) (default to undefined)
 
 const { status, data } = await apiInstance.validateFacturxPdfApiV1ProcessingValidateFacturxPdfPost(
     pdfFile,
     profile,
-    useVerapdf
+    useVerapdf,
+    skipBrFr
 );
 ```
 
@@ -475,6 +503,7 @@ const { status, data } = await apiInstance.validateFacturxPdfApiV1ProcessingVali
 | **pdfFile** | [**File**] | Factur-X PDF file to validate (.pdf format). | defaults to undefined|
 | **profile** | **APIProfile** |  | (optional) defaults to undefined|
 | **useVerapdf** | [**boolean**] | Enable strict PDF/A validation with VeraPDF (recommended for production). If False, uses basic metadata validation. | (optional) defaults to false|
+| **skipBrFr** | [**boolean**] |  | (optional) defaults to undefined|
 
 
 ### Return type
@@ -497,13 +526,14 @@ const { status, data } = await apiInstance.validateFacturxPdfApiV1ProcessingVali
 |**200** | Validation completed successfully (check is_compliant field for result) |  -  |
 |**400** | Invalid or unreadable PDF file |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
 # **validateFacturxPdfAsyncApiV1ProcessingValidateFacturxAsyncPost**
 > TaskResponse validateFacturxPdfAsyncApiV1ProcessingValidateFacturxAsyncPost()
 
-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
 
 ### Example
 
@@ -519,11 +549,15 @@ const apiInstance = new InvoiceProcessingApi(configuration);
 let pdfFile: File; //Factur-X PDF file to validate (.pdf format). (default to undefined)
 let profile: APIProfile; // (optional) (default to undefined)
 let useVerapdf: boolean; //Enable strict PDF/A validation with VeraPDF (recommended for production). May take several seconds. (optional) (default to false)
+let callbackUrl: string; // (optional) (default to undefined)
+let webhookMode: string; //Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL) (optional) (default to 'inline')
 
 const { status, data } = await apiInstance.validateFacturxPdfAsyncApiV1ProcessingValidateFacturxAsyncPost(
     pdfFile,
     profile,
-    useVerapdf
+    useVerapdf,
+    callbackUrl,
+    webhookMode
 );
 ```
 
@@ -534,6 +568,8 @@ const { status, data } = await apiInstance.validateFacturxPdfAsyncApiV1Processin
 | **pdfFile** | [**File**] | Factur-X PDF file to validate (.pdf format). | defaults to undefined|
 | **profile** | **APIProfile** |  | (optional) defaults to undefined|
 | **useVerapdf** | [**boolean**] | Enable strict PDF/A validation with VeraPDF (recommended for production). May take several seconds. | (optional) defaults to false|
+| **callbackUrl** | [**string**] |  | (optional) defaults to undefined|
+| **webhookMode** | [**string**] | Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL) | (optional) defaults to 'inline'|
 
 
 ### Return type
@@ -556,6 +592,7 @@ const { status, data } = await apiInstance.validateFacturxPdfAsyncApiV1Processin
 |**202** | Successful Response |  -  |
 |**400** | Invalid or unreadable PDF file |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
@@ -609,6 +646,7 @@ const { status, data } = await apiInstance.validatePdfSignatureEndpointApiV1Proc
 |**200** | Validation successful |  -  |
 |**400** | Invalid or unreadable file |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
@@ -630,10 +668,12 @@ const apiInstance = new InvoiceProcessingApi(configuration);
 
 let xmlFile: File; //Factur-X XML file to validate (.xml format). (default to undefined)
 let profile: APIProfile; //Validation profile (MINIMUM, BASIC, EN16931, EXTENDED). (optional) (default to undefined)
+let skipBrFr: boolean; // (optional) (default to undefined)
 
 const { status, data } = await apiInstance.validateXmlApiV1ProcessingValidateXmlPost(
     xmlFile,
-    profile
+    profile,
+    skipBrFr
 );
 ```
 
@@ -643,6 +683,7 @@ const { status, data } = await apiInstance.validateXmlApiV1ProcessingValidateXml
 |------------- | ------------- | ------------- | -------------|
 | **xmlFile** | [**File**] | Factur-X XML file to validate (.xml format). | defaults to undefined|
 | **profile** | **APIProfile** | Validation profile (MINIMUM, BASIC, EN16931, EXTENDED). | (optional) defaults to undefined|
+| **skipBrFr** | [**boolean**] |  | (optional) defaults to undefined|
 
 
 ### Return type
@@ -665,6 +706,7 @@ const { status, data } = await apiInstance.validateXmlApiV1ProcessingValidateXml
 |**200** | Successful Response |  -  |
 |**400** | XML does not comply with Factur-X profile rules |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 

package/docs/InvoiceTypeCode.md

@@ -1,39 +1,17 @@
 # InvoiceTypeCode
 
-Document type according to BR-FR-04 (UNTDID 1001 codes).  | Code | Name | Description | |------|------|-------------| | 380 | INVOICE | Commercial invoice | | 389 | SELF_BILLED_INVOICE | Self-billed invoice | | 393 | FACTORED_INVOICE | Factored invoice | | 501 | SELF_BILLED_FACTORED_INVOICE | Self-billed factored invoice | | 386 | PREPAYMENT_INVOICE | Prepayment invoice | | 500 | SELF_BILLED_PREPAYMENT_INVOICE | Self-billed prepayment invoice | | 384 | CORRECTIVE_INVOICE | Corrective invoice | | 471 | SELF_BILLED_CORRECTIVE_INVOICE | Self-billed corrective invoice | | 472 | FACTORED_CORRECTIVE_INVOICE | Factored corrective invoice | | 473 | SELF_BILLED_FACTORED_CORRECTIVE_INVOICE | Self-billed factored corrective invoice | | 381 | CREDIT_NOTE | Credit note | | 261 | SELF_BILLED_CREDIT_NOTE | Self-billed credit note | | 262 | GLOBAL_ALLOWANCE_CREDIT_NOTE | Credit note for global allowance | | 396 | FACTORED_CREDIT_NOTE | Factored credit note | | 502 | SELF_BILLED_FACTORED_CREDIT_NOTE | Self-billed factored credit note | | 503 | PREPAYMENT_CREDIT_NOTE | Credit note for prepayment invoice |
+Invoice type codes (UNTDID 1001).
 
 ## Enum
 
-* `INVOICE` (value: `'380'`)
+* `_380` (value: `'380'`)
 
-* `SELF_BILLED_INVOICE` (value: `'389'`)
+* `_381` (value: `'381'`)
 
-* `FACTORED_INVOICE` (value: `'393'`)
+* `_384` (value: `'384'`)
 
-* `SELF_BILLED_FACTORED_INVOICE` (value: `'501'`)
+* `_389` (value: `'389'`)
 
-* `PREPAYMENT_INVOICE` (value: `'386'`)
-
-* `SELF_BILLED_PREPAYMENT_INVOICE` (value: `'500'`)
-
-* `CORRECTIVE_INVOICE` (value: `'384'`)
-
-* `SELF_BILLED_CORRECTIVE_INVOICE` (value: `'471'`)
-
-* `FACTORED_CORRECTIVE_INVOICE` (value: `'472'`)
-
-* `SELF_BILLED_FACTORED_CORRECTIVE_INVOICE` (value: `'473'`)
-
-* `CREDIT_NOTE` (value: `'381'`)
-
-* `SELF_BILLED_CREDIT_NOTE` (value: `'261'`)
-
-* `GLOBAL_ALLOWANCE_CREDIT_NOTE` (value: `'262'`)
-
-* `FACTORED_CREDIT_NOTE` (value: `'396'`)
-
-* `SELF_BILLED_FACTORED_CREDIT_NOTE` (value: `'502'`)
-
-* `PREPAYMENT_CREDIT_NOTE` (value: `'503'`)
+* `_386` (value: `'386'`)
 
 [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)

package/docs/InvoiceTypeCodeOutput.md

@@ -0,0 +1,39 @@
+# InvoiceTypeCodeOutput
+
+Document type according to BR-FR-04 (UNTDID 1001 codes).  | Code | Name | Description | |------|------|-------------| | 380 | INVOICE | Commercial invoice | | 389 | SELF_BILLED_INVOICE | Self-billed invoice | | 393 | FACTORED_INVOICE | Factored invoice | | 501 | SELF_BILLED_FACTORED_INVOICE | Self-billed factored invoice | | 386 | PREPAYMENT_INVOICE | Prepayment invoice | | 500 | SELF_BILLED_PREPAYMENT_INVOICE | Self-billed prepayment invoice | | 384 | CORRECTIVE_INVOICE | Corrective invoice | | 471 | SELF_BILLED_CORRECTIVE_INVOICE | Self-billed corrective invoice | | 472 | FACTORED_CORRECTIVE_INVOICE | Factored corrective invoice | | 473 | SELF_BILLED_FACTORED_CORRECTIVE_INVOICE | Self-billed factored corrective invoice | | 381 | CREDIT_NOTE | Credit note | | 261 | SELF_BILLED_CREDIT_NOTE | Self-billed credit note | | 262 | GLOBAL_ALLOWANCE_CREDIT_NOTE | Credit note for global allowance | | 396 | FACTORED_CREDIT_NOTE | Factored credit note | | 502 | SELF_BILLED_FACTORED_CREDIT_NOTE | Self-billed factored credit note | | 503 | PREPAYMENT_CREDIT_NOTE | Credit note for prepayment invoice |
+
+## Enum
+
+* `INVOICE` (value: `'380'`)
+
+* `SELF_BILLED_INVOICE` (value: `'389'`)
+
+* `FACTORED_INVOICE` (value: `'393'`)
+
+* `SELF_BILLED_FACTORED_INVOICE` (value: `'501'`)
+
+* `PREPAYMENT_INVOICE` (value: `'386'`)
+
+* `SELF_BILLED_PREPAYMENT_INVOICE` (value: `'500'`)
+
+* `CORRECTIVE_INVOICE` (value: `'384'`)
+
+* `SELF_BILLED_CORRECTIVE_INVOICE` (value: `'471'`)
+
+* `FACTORED_CORRECTIVE_INVOICE` (value: `'472'`)
+
+* `SELF_BILLED_FACTORED_CORRECTIVE_INVOICE` (value: `'473'`)
+
+* `CREDIT_NOTE` (value: `'381'`)
+
+* `SELF_BILLED_CREDIT_NOTE` (value: `'261'`)
+
+* `GLOBAL_ALLOWANCE_CREDIT_NOTE` (value: `'262'`)
+
+* `FACTORED_CREDIT_NOTE` (value: `'396'`)
+
+* `SELF_BILLED_FACTORED_CREDIT_NOTE` (value: `'502'`)
+
+* `PREPAYMENT_CREDIT_NOTE` (value: `'503'`)
+
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)

package/docs/InvoicingFramework.md

@@ -6,7 +6,7 @@ Defines the invoicing framework.  - invoicing_framework_code: Chorus Pro code (A
 
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
-**invoicing_framework_code** | [**InvoicingFrameworkCode**](InvoicingFrameworkCode.md) |  | [default to undefined]
+**invoicing_framework_code** | [**InvoicingFrameworkCode**](InvoicingFrameworkCode.md) | Chorus Pro framework code (A1, A2, A9, A12) | [default to undefined]
 **operation_nature** | [**OperationNature**](OperationNature.md) |  | [optional] [default to undefined]
 **approver_service_code** | **string** |  | [optional] [default to undefined]
 **approver_structure_code** | **string** |  | [optional] [default to undefined]

package/docs/LineSubType.md

@@ -0,0 +1,13 @@
+# LineSubType
+
+Sub-line type for EXTENDED profile (BT-X-8 / EXT-FR-FE-163).  Defines the role of an invoice line in a hierarchical structure: - DETAIL: Standard billing line, included in VAT calculations - INFORMATION: Additional information line, not included in VAT calculations - GROUP: Grouping/subtotal line, not included in VAT calculations
+
+## Enum
+
+* `Detail` (value: `'DETAIL'`)
+
+* `Information` (value: `'INFORMATION'`)
+
+* `Group` (value: `'GROUP'`)
+
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)

package/docs/LocationInner.md

@@ -0,0 +1,18 @@
+# LocationInner
+
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+
+## Example
+
+```typescript
+import { LocationInner } from '@factpulse/sdk';
+
+const instance: LocationInner = {
+};
+```
+
+[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)

package/docs/PDFXMLVerificationApi.md

@@ -1,6 +1,6 @@
 # PDFXMLVerificationApi
 
-All URIs are relative to *http://localhost*
+All URIs are relative to *https://factpulse.fr*
 
 |Method | HTTP request | Description|
 |------------- | ------------- | -------------|
@@ -27,7 +27,7 @@ import {
 const configuration = new Configuration();
 const apiInstance = new PDFXMLVerificationApi(configuration);
 
-let taskId: string; // (default to undefined)
+let taskId: string; //Celery task ID returned by /verify-async endpoint (default to undefined)
 
 const { status, data } = await apiInstance.getVerificationStatusApiV1VerificationVerifyAsyncTaskIdStatusGet(
     taskId
@@ -38,7 +38,7 @@ const { status, data } = await apiInstance.getVerificationStatusApiV1Verificatio
 
 |Name | Type | Description  | Notes|
 |------------- | ------------- | ------------- | -------------|
-| **taskId** | [**string**] |  | defaults to undefined|
+| **taskId** | [**string**] | Celery task ID returned by /verify-async endpoint | defaults to undefined|
 
 
 ### Return type
@@ -60,6 +60,7 @@ const { status, data } = await apiInstance.getVerificationStatusApiV1Verificatio
 |-------------|-------------|------------------|
 |**200** | Successful Response |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
@@ -79,7 +80,7 @@ import {
 const configuration = new Configuration();
 const apiInstance = new PDFXMLVerificationApi(configuration);
 
-let taskId: string; // (default to undefined)
+let taskId: string; //Celery task ID returned by /verify-async endpoint (default to undefined)
 
 const { status, data } = await apiInstance.getVerificationStatusApiV1VerificationVerifyAsyncTaskIdStatusGet_0(
     taskId
@@ -90,7 +91,7 @@ const { status, data } = await apiInstance.getVerificationStatusApiV1Verificatio
 
 |Name | Type | Description  | Notes|
 |------------- | ------------- | ------------- | -------------|
-| **taskId** | [**string**] |  | defaults to undefined|
+| **taskId** | [**string**] | Celery task ID returned by /verify-async endpoint | defaults to undefined|
 
 
 ### Return type
@@ -112,13 +113,14 @@ const { status, data } = await apiInstance.getVerificationStatusApiV1Verificatio
 |-------------|-------------|------------------|
 |**200** | Successful Response |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
 # **verifyPdfAsyncApiV1VerificationVerifyAsyncPost**
 > TaskResponse verifyPdfAsyncApiV1VerificationVerifyAsyncPost()
 
-Verifies PDF/XML Factur-X compliance asynchronously.  **IMPORTANT**: Only Factur-X PDFs (with embedded XML) are accepted. PDFs without Factur-X XML will return a `NOT_FACTURX` error in the result.  This version uses a Celery task and can call the OCR service if the PDF is an image or if `force_ocr=true`.  **Returns immediately** a task ID. Use `/verify-async/{task_id}/status` to retrieve the result.  **Verification principle (Factur-X 1.08):** - Principle #2: XML can only contain info present in the PDF - Principle #4: All XML info must be present and compliant in the PDF  **Verified fields:** - Identification: BT-1 (invoice #), BT-2 (date), BT-3 (type), BT-5 (currency), BT-23 (framework) - Seller: BT-27 (name), BT-29 (SIRET), BT-30 (SIREN), BT-31 (VAT) - Buyer: BT-44 (name), BT-46 (SIRET), BT-47 (SIREN), BT-48 (VAT) - Amounts: BT-109 (excl. tax), BT-110 (VAT), BT-112 (incl. tax), BT-115 (amount due) - VAT breakdown: BT-116, BT-117, BT-118, BT-119 - Invoice lines: BT-153, BT-129, BT-146, BT-131 - Mandatory notes: PMT, PMD, AAB - Rule BR-FR-09: SIRET/SIREN consistency  **Advantages over synchronous version:** - OCR support for image PDFs (via DocTR service) - Longer timeout for large documents - Doesn\'t block the server
+Verifies PDF/XML Factur-X compliance asynchronously.  **IMPORTANT**: Only Factur-X PDFs (with embedded XML) are accepted. PDFs without Factur-X XML will return a `NOT_FACTURX` error in the result.  This version uses a Celery task and can call the OCR service if the PDF is an image or if `force_ocr=true`.  **Returns immediately** a task ID. Use `/verify-async/{task_id}/status` to retrieve the result.  **Verification principle (Factur-X 1.08):** - Principle #2: XML can only contain info present in the PDF - Principle #4: All XML info must be present and compliant in the PDF  **Verified fields:** - Identification: BT-1 (invoice #), BT-2 (date), BT-3 (type), BT-5 (currency), BT-23 (framework) - Seller: BT-27 (name), BT-29 (SIRET), BT-30 (SIREN), BT-31 (VAT) - Buyer: BT-44 (name), BT-46 (SIRET), BT-47 (SIREN), BT-48 (VAT) - Amounts: BT-109 (excl. tax), BT-110 (VAT), BT-112 (incl. tax), BT-115 (amount due) - VAT breakdown: BT-116, BT-117, BT-118, BT-119 - Invoice lines: BT-153, BT-129, BT-146, BT-131 - Mandatory notes: PMT, PMD, AAB - Rule BR-FR-09: SIRET/SIREN consistency  **Advantages over synchronous version:** - OCR support for image PDFs (via DocTR service) - Longer timeout for large documents - Doesn\'t block the server  ## Webhook notification (recommended)  Instead of polling, you can receive a webhook notification when verification completes:  ``` callback_url=https://your-server.com/webhook ```  The webhook will POST a JSON payload with: - `event_type`: `verification.completed` or `verification.failed` - `data.is_compliant`: Whether the PDF/XML are consistent - `data.compliance_score`: Compliance score (0-1) - `X-Webhook-Signature` header for HMAC verification
 
 ### Example
 
@@ -133,10 +135,14 @@ const apiInstance = new PDFXMLVerificationApi(configuration);
 
 let pdfFile: File; //Factur-X PDF file to verify (default to undefined)
 let forceOcr: boolean; //Force OCR usage even if PDF contains native text (optional) (default to false)
+let callbackUrl: string; // (optional) (default to undefined)
+let webhookMode: string; //Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL) (optional) (default to 'inline')
 
 const { status, data } = await apiInstance.verifyPdfAsyncApiV1VerificationVerifyAsyncPost(
     pdfFile,
-    forceOcr
+    forceOcr,
+    callbackUrl,
+    webhookMode
 );
 ```
 
@@ -146,6 +152,8 @@ const { status, data } = await apiInstance.verifyPdfAsyncApiV1VerificationVerify
 |------------- | ------------- | ------------- | -------------|
 | **pdfFile** | [**File**] | Factur-X PDF file to verify | defaults to undefined|
 | **forceOcr** | [**boolean**] | Force OCR usage even if PDF contains native text | (optional) defaults to false|
+| **callbackUrl** | [**string**] |  | (optional) defaults to undefined|
+| **webhookMode** | [**string**] | Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL) | (optional) defaults to 'inline'|
 
 
 ### Return type
@@ -167,13 +175,14 @@ const { status, data } = await apiInstance.verifyPdfAsyncApiV1VerificationVerify
 |-------------|-------------|------------------|
 |**202** | Successful Response |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
 # **verifyPdfAsyncApiV1VerificationVerifyAsyncPost_0**
 > TaskResponse verifyPdfAsyncApiV1VerificationVerifyAsyncPost_0()
 
-Verifies PDF/XML Factur-X compliance asynchronously.  **IMPORTANT**: Only Factur-X PDFs (with embedded XML) are accepted. PDFs without Factur-X XML will return a `NOT_FACTURX` error in the result.  This version uses a Celery task and can call the OCR service if the PDF is an image or if `force_ocr=true`.  **Returns immediately** a task ID. Use `/verify-async/{task_id}/status` to retrieve the result.  **Verification principle (Factur-X 1.08):** - Principle #2: XML can only contain info present in the PDF - Principle #4: All XML info must be present and compliant in the PDF  **Verified fields:** - Identification: BT-1 (invoice #), BT-2 (date), BT-3 (type), BT-5 (currency), BT-23 (framework) - Seller: BT-27 (name), BT-29 (SIRET), BT-30 (SIREN), BT-31 (VAT) - Buyer: BT-44 (name), BT-46 (SIRET), BT-47 (SIREN), BT-48 (VAT) - Amounts: BT-109 (excl. tax), BT-110 (VAT), BT-112 (incl. tax), BT-115 (amount due) - VAT breakdown: BT-116, BT-117, BT-118, BT-119 - Invoice lines: BT-153, BT-129, BT-146, BT-131 - Mandatory notes: PMT, PMD, AAB - Rule BR-FR-09: SIRET/SIREN consistency  **Advantages over synchronous version:** - OCR support for image PDFs (via DocTR service) - Longer timeout for large documents - Doesn\'t block the server
+Verifies PDF/XML Factur-X compliance asynchronously.  **IMPORTANT**: Only Factur-X PDFs (with embedded XML) are accepted. PDFs without Factur-X XML will return a `NOT_FACTURX` error in the result.  This version uses a Celery task and can call the OCR service if the PDF is an image or if `force_ocr=true`.  **Returns immediately** a task ID. Use `/verify-async/{task_id}/status` to retrieve the result.  **Verification principle (Factur-X 1.08):** - Principle #2: XML can only contain info present in the PDF - Principle #4: All XML info must be present and compliant in the PDF  **Verified fields:** - Identification: BT-1 (invoice #), BT-2 (date), BT-3 (type), BT-5 (currency), BT-23 (framework) - Seller: BT-27 (name), BT-29 (SIRET), BT-30 (SIREN), BT-31 (VAT) - Buyer: BT-44 (name), BT-46 (SIRET), BT-47 (SIREN), BT-48 (VAT) - Amounts: BT-109 (excl. tax), BT-110 (VAT), BT-112 (incl. tax), BT-115 (amount due) - VAT breakdown: BT-116, BT-117, BT-118, BT-119 - Invoice lines: BT-153, BT-129, BT-146, BT-131 - Mandatory notes: PMT, PMD, AAB - Rule BR-FR-09: SIRET/SIREN consistency  **Advantages over synchronous version:** - OCR support for image PDFs (via DocTR service) - Longer timeout for large documents - Doesn\'t block the server  ## Webhook notification (recommended)  Instead of polling, you can receive a webhook notification when verification completes:  ``` callback_url=https://your-server.com/webhook ```  The webhook will POST a JSON payload with: - `event_type`: `verification.completed` or `verification.failed` - `data.is_compliant`: Whether the PDF/XML are consistent - `data.compliance_score`: Compliance score (0-1) - `X-Webhook-Signature` header for HMAC verification
 
 ### Example
 
@@ -188,10 +197,14 @@ const apiInstance = new PDFXMLVerificationApi(configuration);
 
 let pdfFile: File; //Factur-X PDF file to verify (default to undefined)
 let forceOcr: boolean; //Force OCR usage even if PDF contains native text (optional) (default to false)
+let callbackUrl: string; // (optional) (default to undefined)
+let webhookMode: string; //Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL) (optional) (default to 'inline')
 
 const { status, data } = await apiInstance.verifyPdfAsyncApiV1VerificationVerifyAsyncPost_0(
     pdfFile,
-    forceOcr
+    forceOcr,
+    callbackUrl,
+    webhookMode
 );
 ```
 
@@ -201,6 +214,8 @@ const { status, data } = await apiInstance.verifyPdfAsyncApiV1VerificationVerify
 |------------- | ------------- | ------------- | -------------|
 | **pdfFile** | [**File**] | Factur-X PDF file to verify | defaults to undefined|
 | **forceOcr** | [**boolean**] | Force OCR usage even if PDF contains native text | (optional) defaults to false|
+| **callbackUrl** | [**string**] |  | (optional) defaults to undefined|
+| **webhookMode** | [**string**] | Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL) | (optional) defaults to 'inline'|
 
 
 ### Return type
@@ -222,6 +237,7 @@ const { status, data } = await apiInstance.verifyPdfAsyncApiV1VerificationVerify
 |-------------|-------------|------------------|
 |**202** | Successful Response |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
@@ -276,6 +292,7 @@ const { status, data } = await apiInstance.verifyPdfSyncApiV1VerificationVerifyP
 |**400** | Verification error (non Factur-X PDF, invalid, etc.) |  -  |
 |**413** | PDF too large or too many pages |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
@@ -330,6 +347,7 @@ const { status, data } = await apiInstance.verifyPdfSyncApiV1VerificationVerifyP
 |**400** | Verification error (non Factur-X PDF, invalid, etc.) |  -  |
 |**413** | PDF too large or too many pages |  -  |
 |**422** | Validation Error |  -  |
+|**401** | Authentication required - Invalid or missing JWT token |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)