factpulse 4.0.1 → 4.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0061473ad13efd96d8c31a87f167aa5c1d8722e43f960266fce4a50b66adee83
-  data.tar.gz: 6d066ab2f7b58959051286436f2a7f5d267873d105ba5fffa8b715a31f6bf57a
+  metadata.gz: ed5220794155d6c2396f8f0d804472921e343e24de4da8a14e39e4635ab3140c
+  data.tar.gz: 4e967d6bd2992759be3e9c26e35f78832fb033c84b676166507ecf434d857b7a
 SHA512:
-  metadata.gz: 3d4487a0f6b114af93c883946f6b5ac51973de38f8de2161e5d125e42e505c14dd6f06f6f1ff9a5c48cf5baaea86971ab626f60af374f7de5aa72ff4c239e9c6
-  data.tar.gz: acec505dcfe90e493a3b5b61b3a479ef507935d5ad7888988f338f64b603a3520ab42a21788ff4c8f441ee2256888b1e2554de46e7e8c9fb2bc04b7b6815197d
+  metadata.gz: 24aee2a48d55854a1695d7e4602f05ae00da5f31e567657b3c168610299ee4640594c448e6c4f8f99a87da7308c98e2345bd02e4e9ca7c348afaa345bc717acc
+  data.tar.gz: 1c3ece1e7befab53f5998e15a469064262e9e6aceabe3a7012c4fa478a46309ad9cfb9c966f04141b881c2d43b020d468ebea1d8f5eff412c1cfdcccbcddc6fa

data/CHANGELOG.md

@@ -7,11 +7,11 @@ et ce projet adhère au [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ## [Unreleased]
 
-## [4.0.1] - 2026-01-20
+## [4.0.2] - 2026-01-24
 
 ### Fixed
-- Gestion post multipart
+- Meilleures conformité validation/génération erportings
 
 
-[Unreleased]: https://github.com/factpulse/sdk-ruby/compare/v4.0.1...HEAD
-[4.0.1]: https://github.com/factpulse/sdk-ruby/releases/tag/v4.0.1
+[Unreleased]: https://github.com/factpulse/sdk-ruby/compare/v4.0.2...HEAD
+[4.0.2]: https://github.com/factpulse/sdk-ruby/releases/tag/v4.0.2

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    factpulse (4.0.1)
+    factpulse (4.0.2)
       typhoeus (~> 1.0, >= 1.0.1)
 
 GEM

data/docs/AFNORPDPPAApi.md

@@ -4,75 +4,8 @@ All URIs are relative to *https://factpulse.fr*
 
 | Method | HTTP request | Description |
 | ------ | ------------ | ----------- |
-| [**get_afnor_credentials_api_v1_afnor_credentials_get**](AFNORPDPPAApi.md#get_afnor_credentials_api_v1_afnor_credentials_get) | **GET** /api/v1/afnor/credentials | Retrieve stored AFNOR credentials |
 | [**get_flux_entrant_api_v1_afnor_incoming_flows_flow_id_get**](AFNORPDPPAApi.md#get_flux_entrant_api_v1_afnor_incoming_flows_flow_id_get) | **GET** /api/v1/afnor/incoming-flows/{flow_id} | Retrieve and extract an incoming invoice |
-| [**oauth_token_proxy_api_v1_afnor_oauth_token_post**](AFNORPDPPAApi.md#oauth_token_proxy_api_v1_afnor_oauth_token_post) | **POST** /api/v1/afnor/oauth/token | OAuth2 endpoint for AFNOR authentication |
-
-
-## get_afnor_credentials_api_v1_afnor_credentials_get
-
-> Object get_afnor_credentials_api_v1_afnor_credentials_get
-
-Retrieve stored AFNOR credentials
-
-Retrieves stored AFNOR/PDP credentials for the JWT's client_uid. This endpoint is used by the SDK in 'stored' mode to retrieve credentials before performing AFNOR OAuth itself.
-
-### Examples
-
-```ruby
-require 'time'
-require 'factpulse'
-# setup authorization
-FactPulse.configure do |config|
-  # Configure Bearer authorization: HTTPBearer
-  config.access_token = 'YOUR_BEARER_TOKEN'
-end
-
-api_instance = FactPulse::AFNORPDPPAApi.new
-
-begin
-  # Retrieve stored AFNOR credentials
-  result = api_instance.get_afnor_credentials_api_v1_afnor_credentials_get
-  p result
-rescue FactPulse::ApiError => e
-  puts "Error when calling AFNORPDPPAApi->get_afnor_credentials_api_v1_afnor_credentials_get: #{e}"
-end
-```
-
-#### Using the get_afnor_credentials_api_v1_afnor_credentials_get_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(Object, Integer, Hash)> get_afnor_credentials_api_v1_afnor_credentials_get_with_http_info
-
-```ruby
-begin
-  # Retrieve stored AFNOR credentials
-  data, status_code, headers = api_instance.get_afnor_credentials_api_v1_afnor_credentials_get_with_http_info
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => Object
-rescue FactPulse::ApiError => e
-  puts "Error when calling AFNORPDPPAApi->get_afnor_credentials_api_v1_afnor_credentials_get_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-This endpoint does not need any parameter.
-
-### Return type
-
-**Object**
-
-### Authorization
-
-[HTTPBearer](../README.md#HTTPBearer)
-
-### HTTP request headers
-
-- **Content-Type**: Not defined
-- **Accept**: application/json
+| [**oauth_token_proxy_api_v1_afnor_oauth_token_post**](AFNORPDPPAApi.md#oauth_token_proxy_api_v1_afnor_oauth_token_post) | **POST** /api/v1/afnor/oauth/token | Test PDP OAuth2 credentials |
 
 
 ## get_flux_entrant_api_v1_afnor_incoming_flows_flow_id_get
@@ -152,9 +85,9 @@ end
 
 > Object oauth_token_proxy_api_v1_afnor_oauth_token_post
 
-OAuth2 endpoint for AFNOR authentication
+Test PDP OAuth2 credentials
 
-OAuth2 proxy endpoint to obtain an AFNOR access token. Proxies to AFNOR mock (sandbox) or real PDP depending on MOCK_AFNOR_BASE_URL. This endpoint is public (no Django auth required) as it is called by the AFNOR SDK.
+OAuth2 proxy to validate PDP credentials. Use this endpoint to verify that OAuth credentials (client_id, client_secret) are valid before saving a PDP configuration. This endpoint is public (no authentication required).
 
 ### Examples
 
@@ -165,7 +98,7 @@ require 'factpulse'
 api_instance = FactPulse::AFNORPDPPAApi.new
 
 begin
-  # OAuth2 endpoint for AFNOR authentication
+  # Test PDP OAuth2 credentials
   result = api_instance.oauth_token_proxy_api_v1_afnor_oauth_token_post
   p result
 rescue FactPulse::ApiError => e
@@ -181,7 +114,7 @@ This returns an Array which contains the response data, status code and headers.
 
 ```ruby
 begin
-  # OAuth2 endpoint for AFNOR authentication
+  # Test PDP OAuth2 credentials
   data, status_code, headers = api_instance.oauth_token_proxy_api_v1_afnor_oauth_token_post_with_http_info
   p status_code # => 2xx
   p headers # => { ... }

data/docs/AsyncTasksApi.md

@@ -0,0 +1,77 @@
+# FactPulse::AsyncTasksApi
+
+All URIs are relative to *https://factpulse.fr*
+
+| Method | HTTP request | Description |
+| ------ | ------------ | ----------- |
+| [**get_task_status_api_v1_processing_tasks_task_id_status_get**](AsyncTasksApi.md#get_task_status_api_v1_processing_tasks_task_id_status_get) | **GET** /api/v1/processing/tasks/{task_id}/status | Get task generation status |
+
+
+## get_task_status_api_v1_processing_tasks_task_id_status_get
+
+> <AsyncTaskStatus> get_task_status_api_v1_processing_tasks_task_id_status_get(task_id)
+
+Get task generation status
+
+Retrieves the progress status of an invoice generation task.  ## Possible states  The `status` field uses the `CeleryStatus` enum with values: - **PENDING, STARTED, SUCCESS, FAILURE, RETRY**  See the `CeleryStatus` schema documentation for details.  ## Business result  When `status=\"SUCCESS\"`, the `result` field contains: - `status`: \"SUCCESS\" or \"ERROR\" (business result) - `content_b64`: Base64 encoded content (if success) - `errorCode`, `errorMessage`, `details`: AFNOR format (if business error)  ## Usage  Poll this endpoint every 2-3 seconds until `status` is `SUCCESS` or `FAILURE`.
+
+### Examples
+
+```ruby
+require 'time'
+require 'factpulse'
+# setup authorization
+FactPulse.configure do |config|
+  # Configure Bearer authorization: HTTPBearer
+  config.access_token = 'YOUR_BEARER_TOKEN'
+end
+
+api_instance = FactPulse::AsyncTasksApi.new
+task_id = 'task_id_example' # String | Celery task ID returned by async endpoints (UUID format)
+
+begin
+  # Get task generation status
+  result = api_instance.get_task_status_api_v1_processing_tasks_task_id_status_get(task_id)
+  p result
+rescue FactPulse::ApiError => e
+  puts "Error when calling AsyncTasksApi->get_task_status_api_v1_processing_tasks_task_id_status_get: #{e}"
+end
+```
+
+#### Using the get_task_status_api_v1_processing_tasks_task_id_status_get_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<AsyncTaskStatus>, Integer, Hash)> get_task_status_api_v1_processing_tasks_task_id_status_get_with_http_info(task_id)
+
+```ruby
+begin
+  # Get task generation status
+  data, status_code, headers = api_instance.get_task_status_api_v1_processing_tasks_task_id_status_get_with_http_info(task_id)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <AsyncTaskStatus>
+rescue FactPulse::ApiError => e
+  puts "Error when calling AsyncTasksApi->get_task_status_api_v1_processing_tasks_task_id_status_get_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **task_id** | **String** | Celery task ID returned by async endpoints (UUID format) |  |
+
+### Return type
+
+[**AsyncTaskStatus**](AsyncTaskStatus.md)
+
+### Authorization
+
+[HTTPBearer](../README.md#HTTPBearer)
+
+### HTTP request headers
+
+- **Content-Type**: Not defined
+- **Accept**: application/json
+

data/docs/ChorusProCredentials.md

@@ -4,11 +4,11 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **piste_client_id** | **String** | PISTE Client ID (government API portal) |  |
-| **piste_client_secret** | **String** | PISTE Client Secret |  |
-| **chorus_pro_login** | **String** | Chorus Pro login |  |
-| **chorus_pro_password** | **String** | Chorus Pro password |  |
-| **sandbox** | **Boolean** | Use sandbox environment (true) or production (false) | [optional][default to true] |
+| **piste_client_id** | **String** |  | [optional] |
+| **piste_client_secret** | **String** |  | [optional] |
+| **chorus_login** | **String** |  | [optional] |
+| **chorus_password** | **String** |  | [optional] |
+| **sandbox_mode** | **Boolean** | [MODE 2] Use sandbox mode (default: True) | [optional][default to true] |
 
 ## Example
 
@@ -18,9 +18,9 @@ require 'factpulse'
 instance = FactPulse::ChorusProCredentials.new(
   piste_client_id: null,
   piste_client_secret: null,
-  chorus_pro_login: null,
-  chorus_pro_password: null,
-  sandbox: null
+  chorus_login: null,
+  chorus_password: null,
+  sandbox_mode: null
 )
 ```
 

data/docs/ChorusProDestination.md

@@ -5,7 +5,7 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **type** | **String** |  | [optional][default to 'chorus_pro'] |
-| **credentials** | [**FactureElectroniqueRestApiSchemasProcessingChorusProCredentials**](FactureElectroniqueRestApiSchemasProcessingChorusProCredentials.md) |  | [optional] |
+| **credentials** | [**ChorusProCredentials**](ChorusProCredentials.md) |  | [optional] |
 
 ## Example
 

data/docs/CreateAggregatedReportRequest.md

@@ -7,7 +7,8 @@
 | **report_id** | **String** | Report identifier (generated by caller) |  |
 | **report_name** | **String** |  | [optional] |
 | **transmission_type** | [**TransmissionTypeCode**](TransmissionTypeCode.md) | Transmission type: IN=Initial, RE=Rectificative (TT-4) | [optional] |
-| **sender** | [**ReportSender**](ReportSender.md) | Report sender/declarant |  |
+| **sender** | [**ReportSender**](ReportSender.md) | Report sender (PA transmitting the report) |  |
+| **issuer** | [**ReportIssuer**](ReportIssuer.md) |  | [optional] |
 | **period** | [**ReportPeriod**](ReportPeriod.md) | Reporting period |  |
 | **invoices** | [**Array<InvoiceInput>**](InvoiceInput.md) |  | [optional] |
 | **transactions** | [**Array<AggregatedTransactionInput>**](AggregatedTransactionInput.md) |  | [optional] |
@@ -24,6 +25,7 @@ instance = FactPulse::CreateAggregatedReportRequest.new(
   report_name: null,
   transmission_type: null,
   sender: null,
+  issuer: null,
   period: null,
   invoices: null,
   transactions: null,

data/docs/CreateEReportingRequest.md

@@ -8,7 +8,8 @@
 | **report_name** | **String** |  | [optional] |
 | **flow_type** | [**EReportingFlowType**](EReportingFlowType.md) | E-Reporting flux type (for internal routing) |  |
 | **transmission_type** | [**TransmissionTypeCode**](TransmissionTypeCode.md) | Transmission type (TT-4 TypeCode): IN=Initial, RE=Rectificative | [optional] |
-| **sender** | [**ReportSender**](ReportSender.md) | Report sender (declarant) |  |
+| **sender** | [**ReportSender**](ReportSender.md) | Report sender (PA transmitting the report) |  |
+| **issuer** | [**ReportIssuer**](ReportIssuer.md) |  | [optional] |
 | **period** | [**ReportPeriod**](ReportPeriod.md) | Reporting period |  |
 | **invoices** | [**Array<InvoiceInput>**](InvoiceInput.md) |  | [optional] |
 | **transactions** | [**Array<AggregatedTransactionInput>**](AggregatedTransactionInput.md) |  | [optional] |
@@ -26,6 +27,7 @@ instance = FactPulse::CreateEReportingRequest.new(
   flow_type: null,
   transmission_type: null,
   sender: null,
+  issuer: null,
   period: null,
   invoices: null,
   transactions: null,

data/docs/ElectronicSignatureApi.md

@@ -0,0 +1,319 @@
+# FactPulse::ElectronicSignatureApi
+
+All URIs are relative to *https://factpulse.fr*
+
+| Method | HTTP request | Description |
+| ------ | ------------ | ----------- |
+| [**generate_test_certificate_api_v1_processing_generate_test_certificate_post**](ElectronicSignatureApi.md#generate_test_certificate_api_v1_processing_generate_test_certificate_post) | **POST** /api/v1/processing/generate-test-certificate | Generate a self-signed X.509 test certificate |
+| [**sign_pdf_api_v1_processing_sign_pdf_post**](ElectronicSignatureApi.md#sign_pdf_api_v1_processing_sign_pdf_post) | **POST** /api/v1/processing/sign-pdf | Sign a PDF with client's certificate (PAdES-B-LT) |
+| [**sign_pdf_async_api_v1_processing_sign_pdf_async_post**](ElectronicSignatureApi.md#sign_pdf_async_api_v1_processing_sign_pdf_async_post) | **POST** /api/v1/processing/sign-pdf-async | Sign a PDF asynchronously (Celery) |
+| [**validate_pdf_signature_endpoint_api_v1_processing_validate_pdf_signature_post**](ElectronicSignatureApi.md#validate_pdf_signature_endpoint_api_v1_processing_validate_pdf_signature_post) | **POST** /api/v1/processing/validate-pdf-signature | Validate electronic signatures of a PDF |
+
+
+## generate_test_certificate_api_v1_processing_generate_test_certificate_post
+
+> <GenerateCertificateResponse> generate_test_certificate_api_v1_processing_generate_test_certificate_post(generate_certificate_request)
+
+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://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
+
+```ruby
+require 'time'
+require 'factpulse'
+# setup authorization
+FactPulse.configure do |config|
+  # Configure Bearer authorization: HTTPBearer
+  config.access_token = 'YOUR_BEARER_TOKEN'
+end
+
+api_instance = FactPulse::ElectronicSignatureApi.new
+generate_certificate_request = FactPulse::GenerateCertificateRequest.new # GenerateCertificateRequest | 
+
+begin
+  # Generate a self-signed X.509 test certificate
+  result = api_instance.generate_test_certificate_api_v1_processing_generate_test_certificate_post(generate_certificate_request)
+  p result
+rescue FactPulse::ApiError => e
+  puts "Error when calling ElectronicSignatureApi->generate_test_certificate_api_v1_processing_generate_test_certificate_post: #{e}"
+end
+```
+
+#### Using the generate_test_certificate_api_v1_processing_generate_test_certificate_post_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(<GenerateCertificateResponse>, Integer, Hash)> generate_test_certificate_api_v1_processing_generate_test_certificate_post_with_http_info(generate_certificate_request)
+
+```ruby
+begin
+  # Generate a self-signed X.509 test certificate
+  data, status_code, headers = api_instance.generate_test_certificate_api_v1_processing_generate_test_certificate_post_with_http_info(generate_certificate_request)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => <GenerateCertificateResponse>
+rescue FactPulse::ApiError => e
+  puts "Error when calling ElectronicSignatureApi->generate_test_certificate_api_v1_processing_generate_test_certificate_post_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **generate_certificate_request** | [**GenerateCertificateRequest**](GenerateCertificateRequest.md) |  |  |
+
+### Return type
+
+[**GenerateCertificateResponse**](GenerateCertificateResponse.md)
+
+### Authorization
+
+[HTTPBearer](../README.md#HTTPBearer)
+
+### HTTP request headers
+
+- **Content-Type**: application/json
+- **Accept**: application/json
+
+
+## sign_pdf_api_v1_processing_sign_pdf_post
+
+> Object sign_pdf_api_v1_processing_sign_pdf_post(pdf_file, opts)
+
+Sign a PDF with client's certificate (PAdES-B-LT)
+
+Signs an uploaded PDF with the electronic certificate configured for the client (via client_uid from JWT).      **Supported standards**: PAdES-B-B, PAdES-B-T (timestamping), PAdES-B-LT (long-term archiving).      **eIDAS levels**: SES (self-signed), AdES (commercial CA), QES (PSCO - out of scope).      **Security**: Double authentication X-Internal-Secret + JWT Bearer to retrieve the certificate.      **⚠️ Legal disclaimer**: Generated signatures are electronic seals as defined by     the eIDAS regulation. The level of legal validity depends on the certificate used (SES/AdES/QES).     FactPulse does not provide QES qualified certificates - you must obtain a certificate from     a PSCO (qualified Trust Service Provider) for maximum legal validity.
+
+### Examples
+
+```ruby
+require 'time'
+require 'factpulse'
+# setup authorization
+FactPulse.configure do |config|
+  # Configure Bearer authorization: HTTPBearer
+  config.access_token = 'YOUR_BEARER_TOKEN'
+end
+
+api_instance = FactPulse::ElectronicSignatureApi.new
+pdf_file = File.new('/path/to/some/file') # File | PDF file to sign (will be processed and returned signed in base64)
+opts = {
+  reason: 'reason_example', # String | 
+  location: 'location_example', # String | 
+  contact: 'contact_example', # String | 
+  field_name: 'field_name_example', # String | PDF signature field name
+  use_pades_lt: true, # Boolean | Enable PAdES-B-LT (long-term archiving with embedded validation data). REQUIRES a certificate with OCSP/CRL access.
+  use_timestamp: true # Boolean | Enable RFC 3161 timestamping with FreeTSA (PAdES-B-T)
+}
+
+begin
+  # Sign a PDF with client's certificate (PAdES-B-LT)
+  result = api_instance.sign_pdf_api_v1_processing_sign_pdf_post(pdf_file, opts)
+  p result
+rescue FactPulse::ApiError => e
+  puts "Error when calling ElectronicSignatureApi->sign_pdf_api_v1_processing_sign_pdf_post: #{e}"
+end
+```
+
+#### Using the sign_pdf_api_v1_processing_sign_pdf_post_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(Object, Integer, Hash)> sign_pdf_api_v1_processing_sign_pdf_post_with_http_info(pdf_file, opts)
+
+```ruby
+begin
+  # Sign a PDF with client's certificate (PAdES-B-LT)
+  data, status_code, headers = api_instance.sign_pdf_api_v1_processing_sign_pdf_post_with_http_info(pdf_file, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => Object
+rescue FactPulse::ApiError => e
+  puts "Error when calling ElectronicSignatureApi->sign_pdf_api_v1_processing_sign_pdf_post_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **pdf_file** | **File** | PDF file to sign (will be processed and returned signed in base64) |  |
+| **reason** | **String** |  | [optional] |
+| **location** | **String** |  | [optional] |
+| **contact** | **String** |  | [optional] |
+| **field_name** | **String** | PDF signature field name | [optional][default to &#39;FactPulseSignature&#39;] |
+| **use_pades_lt** | **Boolean** | Enable PAdES-B-LT (long-term archiving with embedded validation data). REQUIRES a certificate with OCSP/CRL access. | [optional][default to false] |
+| **use_timestamp** | **Boolean** | Enable RFC 3161 timestamping with FreeTSA (PAdES-B-T) | [optional][default to true] |
+
+### Return type
+
+**Object**
+
+### Authorization
+
+[HTTPBearer](../README.md#HTTPBearer)
+
+### HTTP request headers
+
+- **Content-Type**: multipart/form-data
+- **Accept**: application/json
+
+
+## sign_pdf_async_api_v1_processing_sign_pdf_async_post
+
+> Object sign_pdf_async_api_v1_processing_sign_pdf_async_post(pdf_file, opts)
+
+Sign a PDF asynchronously (Celery)
+
+Signs an uploaded PDF asynchronously via a Celery task.      **Difference with /sign-pdf**:     - `/sign-pdf`: Synchronous signature (blocking until completion)     - `/sign-pdf-async`: Asynchronous signature (returns immediately with task_id)      **Async advantages**:     - No timeout for large files     - No blocking of FastAPI worker     - Progress tracking via task_id     - Ideal for batch processing      **Supported standards**: PAdES-B-B, PAdES-B-T (timestamping), PAdES-B-LT (long-term archiving).      **⚠️ Legal disclaimer**: Same as /sign-pdf (see that endpoint's documentation).
+
+### Examples
+
+```ruby
+require 'time'
+require 'factpulse'
+# setup authorization
+FactPulse.configure do |config|
+  # Configure Bearer authorization: HTTPBearer
+  config.access_token = 'YOUR_BEARER_TOKEN'
+end
+
+api_instance = FactPulse::ElectronicSignatureApi.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 | 
+  field_name: 'field_name_example', # String | PDF signature field name
+  use_pades_lt: true, # Boolean | Enable PAdES-B-LT (long-term archiving with embedded validation data). REQUIRES a certificate with OCSP/CRL access.
+  use_timestamp: true # Boolean | Enable RFC 3161 timestamping with FreeTSA (PAdES-B-T)
+}
+
+begin
+  # Sign a PDF asynchronously (Celery)
+  result = api_instance.sign_pdf_async_api_v1_processing_sign_pdf_async_post(pdf_file, opts)
+  p result
+rescue FactPulse::ApiError => e
+  puts "Error when calling ElectronicSignatureApi->sign_pdf_async_api_v1_processing_sign_pdf_async_post: #{e}"
+end
+```
+
+#### Using the sign_pdf_async_api_v1_processing_sign_pdf_async_post_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(Object, Integer, Hash)> sign_pdf_async_api_v1_processing_sign_pdf_async_post_with_http_info(pdf_file, opts)
+
+```ruby
+begin
+  # Sign a PDF asynchronously (Celery)
+  data, status_code, headers = api_instance.sign_pdf_async_api_v1_processing_sign_pdf_async_post_with_http_info(pdf_file, opts)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => Object
+rescue FactPulse::ApiError => e
+  puts "Error when calling ElectronicSignatureApi->sign_pdf_async_api_v1_processing_sign_pdf_async_post_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **pdf_file** | **File** | PDF file to sign (processed asynchronously) |  |
+| **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;] |
+| **reason** | **String** |  | [optional] |
+| **location** | **String** |  | [optional] |
+| **contact** | **String** |  | [optional] |
+| **field_name** | **String** | PDF signature field name | [optional][default to &#39;FactPulseSignature&#39;] |
+| **use_pades_lt** | **Boolean** | Enable PAdES-B-LT (long-term archiving with embedded validation data). REQUIRES a certificate with OCSP/CRL access. | [optional][default to false] |
+| **use_timestamp** | **Boolean** | Enable RFC 3161 timestamping with FreeTSA (PAdES-B-T) | [optional][default to true] |
+
+### Return type
+
+**Object**
+
+### Authorization
+
+[HTTPBearer](../README.md#HTTPBearer)
+
+### HTTP request headers
+
+- **Content-Type**: multipart/form-data
+- **Accept**: application/json
+
+
+## validate_pdf_signature_endpoint_api_v1_processing_validate_pdf_signature_post
+
+> Object validate_pdf_signature_endpoint_api_v1_processing_validate_pdf_signature_post(pdf_file)
+
+Validate electronic signatures of a PDF
+
+Validates electronic signatures present in an uploaded PDF.      **Verifications performed**:     - Presence of signatures     - Document integrity (not modified since signing)     - Certificate validity     - Chain of trust (if available)     - Presence of timestamp (PAdES-B-T)     - Validation data (PAdES-B-LT)      **Supported standards**: PAdES-B-B, PAdES-B-T, PAdES-B-LT, ISO 32000-2.      **⚠️ Note**: This validation is technical (cryptographic integrity). Legal validity     depends on the eIDAS level of the certificate (SES/AdES/QES) and the context of use.
+
+### Examples
+
+```ruby
+require 'time'
+require 'factpulse'
+# setup authorization
+FactPulse.configure do |config|
+  # Configure Bearer authorization: HTTPBearer
+  config.access_token = 'YOUR_BEARER_TOKEN'
+end
+
+api_instance = FactPulse::ElectronicSignatureApi.new
+pdf_file = File.new('/path/to/some/file') # File | PDF file to validate (will be analyzed to detect and validate signatures)
+
+begin
+  # Validate electronic signatures of a PDF
+  result = api_instance.validate_pdf_signature_endpoint_api_v1_processing_validate_pdf_signature_post(pdf_file)
+  p result
+rescue FactPulse::ApiError => e
+  puts "Error when calling ElectronicSignatureApi->validate_pdf_signature_endpoint_api_v1_processing_validate_pdf_signature_post: #{e}"
+end
+```
+
+#### Using the validate_pdf_signature_endpoint_api_v1_processing_validate_pdf_signature_post_with_http_info variant
+
+This returns an Array which contains the response data, status code and headers.
+
+> <Array(Object, Integer, Hash)> validate_pdf_signature_endpoint_api_v1_processing_validate_pdf_signature_post_with_http_info(pdf_file)
+
+```ruby
+begin
+  # Validate electronic signatures of a PDF
+  data, status_code, headers = api_instance.validate_pdf_signature_endpoint_api_v1_processing_validate_pdf_signature_post_with_http_info(pdf_file)
+  p status_code # => 2xx
+  p headers # => { ... }
+  p data # => Object
+rescue FactPulse::ApiError => e
+  puts "Error when calling ElectronicSignatureApi->validate_pdf_signature_endpoint_api_v1_processing_validate_pdf_signature_post_with_http_info: #{e}"
+end
+```
+
+### Parameters
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **pdf_file** | **File** | PDF file to validate (will be analyzed to detect and validate signatures) |  |
+
+### Return type
+
+**Object**
+
+### Authorization
+
+[HTTPBearer](../README.md#HTTPBearer)
+
+### HTTP request headers
+
+- **Content-Type**: multipart/form-data
+- **Accept**: application/json
+

data/docs/EncaisseeRequest.md

@@ -6,14 +6,16 @@
 | ---- | ---- | ----------- | ----- |
 | **invoice_id** | **String** | Identifiant de la facture (BT-1) |  |
 | **invoice_issue_date** | **Date** | Date d'émission de la facture (YYYY-MM-DD) |  |
+| **invoice_buyer_siren** | **String** | SIREN de l'acheteur (destinataire du statut) |  |
+| **invoice_buyer_electronic_address** | **String** | Adresse électronique de l'acheteur (MDT-73) |  |
+| **amount** | [**Amount**](Amount.md) |  |  |
+| **currency** | **String** | Code devise ISO 4217 | [optional][default to 'EUR'] |
 | **sender_siren** | **String** |  | [optional] |
-| **flow_type** | **String** | Type de flux: SupplierInvoiceLC (acheteur) ou CustomerInvoiceLC (vendeur) | [optional][default to 'SupplierInvoiceLC'] |
+| **flow_type** | **String** | Type de flux (CustomerInvoiceLC pour facture émise) | [optional][default to 'CustomerInvoiceLC'] |
 | **pdp_flow_service_url** | **String** |  | [optional] |
 | **pdp_token_url** | **String** |  | [optional] |
 | **pdp_client_id** | **String** |  | [optional] |
 | **pdp_client_secret** | **String** |  | [optional] |
-| **amount** | [**Amount**](Amount.md) |  |  |
-| **currency** | **String** | Code devise ISO 4217 | [optional][default to 'EUR'] |
 
 ## Example
 
@@ -23,14 +25,16 @@ require 'factpulse'
 instance = FactPulse::EncaisseeRequest.new(
   invoice_id: null,
   invoice_issue_date: null,
+  invoice_buyer_siren: null,
+  invoice_buyer_electronic_address: null,
+  amount: null,
+  currency: null,
   sender_siren: null,
   flow_type: null,
   pdp_flow_service_url: null,
   pdp_token_url: null,
   pdp_client_id: null,
-  pdp_client_secret: null,
-  amount: null,
-  currency: null
+  pdp_client_secret: null
 )
 ```