@factpulse/sdk 4.0.1 → 4.0.2

package/dist/esm/api/electronic-signature-api.js

@@ -0,0 +1,446 @@
+/* tslint:disable */
+/* eslint-disable */
+/**
+ * FactPulse REST API
+ *  REST API for electronic invoicing in France: Factur-X, AFNOR PDP/PA, electronic signatures.  ## 🎯 Main Features  ### 📄 Factur-X - Generation - **Formats**: XML only or PDF/A-3 with embedded XML - **Profiles**: MINIMUM, BASIC, EN16931, EXTENDED - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT) - **🆕 Simplified Format**: Generation from SIRET + auto-enrichment (Chorus Pro API + Business Search)  ### ✅ Factur-X - Validation - **XML Validation**: Schematron (45 to 210+ rules depending on profile) - **PDF Validation**: PDF/A-3, Factur-X XMP metadata - **VeraPDF**: Strict PDF/A validation (146+ ISO 19005-3 rules)  ### ✍️ Electronic Signature - **Standards**: PAdES-B-B, PAdES-B-T (RFC 3161 timestamping), PAdES-B-LT (long-term archival) - **eIDAS Levels**: SES (self-signed), AdES (commercial CA), QES (QTSP) - **Validation**: Cryptographic integrity and certificate verification  ### 📋 Flux 6 - Invoice Lifecycle (CDAR) - **CDAR Messages**: Acknowledgements, invoice statuses - **PPF Statuses**: REFUSED (210), PAID (212)  ### 📊 Flux 10 - E-Reporting - **Tax Declarations**: International B2B, B2C - **Flow Types**: 10.1 (B2B transactions), 10.2 (B2B payments), 10.3 (B2C transactions), 10.4 (B2C payments)  ### 📡 AFNOR PDP/PA (XP Z12-013) - **Flow Service**: Submit and search flows to PDPs - **Directory Service**: Company search (SIREN/SIRET) - **Multi-client**: Support for multiple PDP configs per user  ### 🏛️ Chorus Pro - **Public Sector Invoicing**: Complete API for Chorus Pro  ### ⏳ Async Tasks - **Celery**: Asynchronous generation, validation and signing - **Polling**: Status tracking via `/tasks/{task_id}/status` - **Webhooks**: Automatic notifications when tasks complete  ## 🔒 Authentication  All requests require a **JWT token** in the Authorization header: ``` Authorization: Bearer YOUR_JWT_TOKEN ```  ### How to obtain a JWT token?  #### 🔑 Method 1: `/api/token/` API (Recommended)  **URL:** `https://factpulse.fr/api/token/`  This method is **recommended** for integration in your applications and CI/CD workflows.  **Prerequisites:** Having set a password on your account  **For users registered via email/password:** - You already have a password, use it directly  **For users registered via OAuth (Google/GitHub):** - You must first set a password at: https://factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API  **Request example:** ```bash curl -X POST https://factpulse.fr/api/token/ \\   -H \"Content-Type: application/json\" \\   -d \'{     \"username\": \"your_email@example.com\",     \"password\": \"your_password\"   }\' ```  **Optional `client_uid` parameter:**  To select credentials for a specific client (PA/PDP, Chorus Pro, signing certificates), add `client_uid`:  ```bash curl -X POST https://factpulse.fr/api/token/ \\   -H \"Content-Type: application/json\" \\   -d \'{     \"username\": \"your_email@example.com\",     \"password\": \"your_password\",     \"client_uid\": \"550e8400-e29b-41d4-a716-446655440000\"   }\' ```  The `client_uid` will be included in the JWT and allow the API to automatically use: - AFNOR/PDP credentials configured for this client - Chorus Pro credentials configured for this client - Electronic signature certificates configured for this client  **Response:** ```json {   \"access\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\",  // Access token (validity: 30 min)   \"refresh\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\"  // Refresh token (validity: 7 days) } ```  **Advantages:** - ✅ Full automation (CI/CD, scripts) - ✅ Programmatic token management - ✅ Refresh token support for automatic access renewal - ✅ Easy integration in any language/tool  #### 🖥️ Method 2: Dashboard Generation (Alternative)  **URL:** https://factpulse.fr/api/dashboard/  This method is suitable for quick tests or occasional use via the graphical interface.  **How it works:** - Log in to the dashboard - Use the \"Generate Test Token\" or \"Generate Production Token\" buttons - Works for **all** users (OAuth and email/password), without requiring a password  **Token types:** - **Test Token**: 24h validity, 1000 calls/day quota (free) - **Production Token**: 7 days validity, quota based on your plan  **Advantages:** - ✅ Quick for API testing - ✅ No password required - ✅ Simple visual interface  **Disadvantages:** - ❌ Requires manual action - ❌ No refresh token - ❌ Less suited for automation  ### 📚 Full Documentation  For more information on authentication and API usage: https://factpulse.fr/documentation-api/
+ *
+ * The version of the OpenAPI document: 1.0.0
+ * Contact: contact@factpulse.fr
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
+    function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
+    return new (P || (P = Promise))(function (resolve, reject) {
+        function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
+        function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
+        function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
+        step((generator = generator.apply(thisArg, _arguments || [])).next());
+    });
+};
+import globalAxios from 'axios';
+// Some imports not used depending on template conditions
+// @ts-ignore
+import { DUMMY_BASE_URL, assertParamExists, setBearerAuthToObject, setSearchParams, serializeDataIfNeeded, toPathString, createRequestFunction } from '../common';
+// @ts-ignore
+import { BASE_PATH, BaseAPI, operationServerMap } from '../base';
+/**
+ * ElectronicSignatureApi - axios parameter creator
+ */
+export const ElectronicSignatureApiAxiosParamCreator = function (configuration) {
+    return {
+        /**
+         * 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)
+         * @summary Generate a self-signed X.509 test certificate
+         * @param {GenerateCertificateRequest} generateCertificateRequest
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        generateTestCertificateApiV1ProcessingGenerateTestCertificatePost: (generateCertificateRequest_1, ...args_1) => __awaiter(this, [generateCertificateRequest_1, ...args_1], void 0, function* (generateCertificateRequest, options = {}) {
+            // verify required parameter 'generateCertificateRequest' is not null or undefined
+            assertParamExists('generateTestCertificateApiV1ProcessingGenerateTestCertificatePost', 'generateCertificateRequest', generateCertificateRequest);
+            const localVarPath = `/api/v1/processing/generate-test-certificate`;
+            // use dummy base URL string because the URL constructor only accepts absolute URLs.
+            const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL);
+            let baseOptions;
+            if (configuration) {
+                baseOptions = configuration.baseOptions;
+            }
+            const localVarRequestOptions = Object.assign(Object.assign({ method: 'POST' }, baseOptions), options);
+            const localVarHeaderParameter = {};
+            const localVarQueryParameter = {};
+            // authentication HTTPBearer required
+            // http bearer authentication required
+            yield setBearerAuthToObject(localVarHeaderParameter, configuration);
+            localVarHeaderParameter['Content-Type'] = 'application/json';
+            localVarHeaderParameter['Accept'] = 'application/json';
+            setSearchParams(localVarUrlObj, localVarQueryParameter);
+            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
+            localVarRequestOptions.headers = Object.assign(Object.assign(Object.assign({}, localVarHeaderParameter), headersFromBaseOptions), options.headers);
+            localVarRequestOptions.data = serializeDataIfNeeded(generateCertificateRequest, localVarRequestOptions, configuration);
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        }),
+        /**
+         * 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.
+         * @summary Sign a PDF with client\'s certificate (PAdES-B-LT)
+         * @param {File} pdfFile PDF file to sign (will be processed and returned signed in base64)
+         * @param {string | null} [reason]
+         * @param {string | null} [location]
+         * @param {string | null} [contact]
+         * @param {string} [fieldName] PDF signature field name
+         * @param {boolean} [usePadesLt] Enable PAdES-B-LT (long-term archiving with embedded validation data). REQUIRES a certificate with OCSP/CRL access.
+         * @param {boolean} [useTimestamp] Enable RFC 3161 timestamping with FreeTSA (PAdES-B-T)
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        signPdfApiV1ProcessingSignPdfPost: (pdfFile_1, reason_1, location_1, contact_1, fieldName_1, usePadesLt_1, useTimestamp_1, ...args_1) => __awaiter(this, [pdfFile_1, reason_1, location_1, contact_1, fieldName_1, usePadesLt_1, useTimestamp_1, ...args_1], void 0, function* (pdfFile, reason, location, contact, fieldName, usePadesLt, useTimestamp, options = {}) {
+            // verify required parameter 'pdfFile' is not null or undefined
+            assertParamExists('signPdfApiV1ProcessingSignPdfPost', 'pdfFile', pdfFile);
+            const localVarPath = `/api/v1/processing/sign-pdf`;
+            // use dummy base URL string because the URL constructor only accepts absolute URLs.
+            const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL);
+            let baseOptions;
+            if (configuration) {
+                baseOptions = configuration.baseOptions;
+            }
+            const localVarRequestOptions = Object.assign(Object.assign({ method: 'POST' }, baseOptions), options);
+            const localVarHeaderParameter = {};
+            const localVarQueryParameter = {};
+            const localVarFormParams = new ((configuration && configuration.formDataCtor) || FormData)();
+            // authentication HTTPBearer required
+            // http bearer authentication required
+            yield setBearerAuthToObject(localVarHeaderParameter, configuration);
+            if (pdfFile !== undefined) {
+                localVarFormParams.append('pdf_file', pdfFile);
+            }
+            if (reason !== undefined) {
+                localVarFormParams.append('reason', reason);
+            }
+            if (location !== undefined) {
+                localVarFormParams.append('location', location);
+            }
+            if (contact !== undefined) {
+                localVarFormParams.append('contact', contact);
+            }
+            if (fieldName !== undefined) {
+                localVarFormParams.append('field_name', fieldName);
+            }
+            if (usePadesLt !== undefined) {
+                localVarFormParams.append('use_pades_lt', String(usePadesLt));
+            }
+            if (useTimestamp !== undefined) {
+                localVarFormParams.append('use_timestamp', String(useTimestamp));
+            }
+            localVarHeaderParameter['Content-Type'] = 'multipart/form-data';
+            localVarHeaderParameter['Accept'] = 'application/json';
+            setSearchParams(localVarUrlObj, localVarQueryParameter);
+            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
+            localVarRequestOptions.headers = Object.assign(Object.assign(Object.assign({}, localVarHeaderParameter), headersFromBaseOptions), options.headers);
+            localVarRequestOptions.data = localVarFormParams;
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        }),
+        /**
+         * 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).
+         * @summary Sign a PDF asynchronously (Celery)
+         * @param {File} pdfFile PDF file to sign (processed asynchronously)
+         * @param {string | null} [callbackUrl]
+         * @param {string} [webhookMode] Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL)
+         * @param {string | null} [reason]
+         * @param {string | null} [location]
+         * @param {string | null} [contact]
+         * @param {string} [fieldName] PDF signature field name
+         * @param {boolean} [usePadesLt] Enable PAdES-B-LT (long-term archiving with embedded validation data). REQUIRES a certificate with OCSP/CRL access.
+         * @param {boolean} [useTimestamp] Enable RFC 3161 timestamping with FreeTSA (PAdES-B-T)
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        signPdfAsyncApiV1ProcessingSignPdfAsyncPost: (pdfFile_1, callbackUrl_1, webhookMode_1, reason_1, location_1, contact_1, fieldName_1, usePadesLt_1, useTimestamp_1, ...args_1) => __awaiter(this, [pdfFile_1, callbackUrl_1, webhookMode_1, reason_1, location_1, contact_1, fieldName_1, usePadesLt_1, useTimestamp_1, ...args_1], void 0, function* (pdfFile, callbackUrl, webhookMode, reason, location, contact, fieldName, usePadesLt, useTimestamp, options = {}) {
+            // verify required parameter 'pdfFile' is not null or undefined
+            assertParamExists('signPdfAsyncApiV1ProcessingSignPdfAsyncPost', 'pdfFile', pdfFile);
+            const localVarPath = `/api/v1/processing/sign-pdf-async`;
+            // use dummy base URL string because the URL constructor only accepts absolute URLs.
+            const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL);
+            let baseOptions;
+            if (configuration) {
+                baseOptions = configuration.baseOptions;
+            }
+            const localVarRequestOptions = Object.assign(Object.assign({ method: 'POST' }, baseOptions), options);
+            const localVarHeaderParameter = {};
+            const localVarQueryParameter = {};
+            const localVarFormParams = new ((configuration && configuration.formDataCtor) || FormData)();
+            // authentication HTTPBearer required
+            // http bearer authentication required
+            yield setBearerAuthToObject(localVarHeaderParameter, configuration);
+            if (pdfFile !== undefined) {
+                localVarFormParams.append('pdf_file', pdfFile);
+            }
+            if (callbackUrl !== undefined) {
+                localVarFormParams.append('callback_url', callbackUrl);
+            }
+            if (webhookMode !== undefined) {
+                localVarFormParams.append('webhook_mode', webhookMode);
+            }
+            if (reason !== undefined) {
+                localVarFormParams.append('reason', reason);
+            }
+            if (location !== undefined) {
+                localVarFormParams.append('location', location);
+            }
+            if (contact !== undefined) {
+                localVarFormParams.append('contact', contact);
+            }
+            if (fieldName !== undefined) {
+                localVarFormParams.append('field_name', fieldName);
+            }
+            if (usePadesLt !== undefined) {
+                localVarFormParams.append('use_pades_lt', String(usePadesLt));
+            }
+            if (useTimestamp !== undefined) {
+                localVarFormParams.append('use_timestamp', String(useTimestamp));
+            }
+            localVarHeaderParameter['Content-Type'] = 'multipart/form-data';
+            localVarHeaderParameter['Accept'] = 'application/json';
+            setSearchParams(localVarUrlObj, localVarQueryParameter);
+            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
+            localVarRequestOptions.headers = Object.assign(Object.assign(Object.assign({}, localVarHeaderParameter), headersFromBaseOptions), options.headers);
+            localVarRequestOptions.data = localVarFormParams;
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        }),
+        /**
+         * 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.
+         * @summary Validate electronic signatures of a PDF
+         * @param {File} pdfFile PDF file to validate (will be analyzed to detect and validate signatures)
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        validatePdfSignatureEndpointApiV1ProcessingValidatePdfSignaturePost: (pdfFile_1, ...args_1) => __awaiter(this, [pdfFile_1, ...args_1], void 0, function* (pdfFile, options = {}) {
+            // verify required parameter 'pdfFile' is not null or undefined
+            assertParamExists('validatePdfSignatureEndpointApiV1ProcessingValidatePdfSignaturePost', 'pdfFile', pdfFile);
+            const localVarPath = `/api/v1/processing/validate-pdf-signature`;
+            // use dummy base URL string because the URL constructor only accepts absolute URLs.
+            const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL);
+            let baseOptions;
+            if (configuration) {
+                baseOptions = configuration.baseOptions;
+            }
+            const localVarRequestOptions = Object.assign(Object.assign({ method: 'POST' }, baseOptions), options);
+            const localVarHeaderParameter = {};
+            const localVarQueryParameter = {};
+            const localVarFormParams = new ((configuration && configuration.formDataCtor) || FormData)();
+            // authentication HTTPBearer required
+            // http bearer authentication required
+            yield setBearerAuthToObject(localVarHeaderParameter, configuration);
+            if (pdfFile !== undefined) {
+                localVarFormParams.append('pdf_file', pdfFile);
+            }
+            localVarHeaderParameter['Content-Type'] = 'multipart/form-data';
+            localVarHeaderParameter['Accept'] = 'application/json';
+            setSearchParams(localVarUrlObj, localVarQueryParameter);
+            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
+            localVarRequestOptions.headers = Object.assign(Object.assign(Object.assign({}, localVarHeaderParameter), headersFromBaseOptions), options.headers);
+            localVarRequestOptions.data = localVarFormParams;
+            return {
+                url: toPathString(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        }),
+    };
+};
+/**
+ * ElectronicSignatureApi - functional programming interface
+ */
+export const ElectronicSignatureApiFp = function (configuration) {
+    const localVarAxiosParamCreator = ElectronicSignatureApiAxiosParamCreator(configuration);
+    return {
+        /**
+         * 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)
+         * @summary Generate a self-signed X.509 test certificate
+         * @param {GenerateCertificateRequest} generateCertificateRequest
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        generateTestCertificateApiV1ProcessingGenerateTestCertificatePost(generateCertificateRequest, options) {
+            return __awaiter(this, void 0, void 0, function* () {
+                var _a, _b, _c;
+                const localVarAxiosArgs = yield localVarAxiosParamCreator.generateTestCertificateApiV1ProcessingGenerateTestCertificatePost(generateCertificateRequest, options);
+                const localVarOperationServerIndex = (_a = configuration === null || configuration === void 0 ? void 0 : configuration.serverIndex) !== null && _a !== void 0 ? _a : 0;
+                const localVarOperationServerBasePath = (_c = (_b = operationServerMap['ElectronicSignatureApi.generateTestCertificateApiV1ProcessingGenerateTestCertificatePost']) === null || _b === void 0 ? void 0 : _b[localVarOperationServerIndex]) === null || _c === void 0 ? void 0 : _c.url;
+                return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+            });
+        },
+        /**
+         * 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.
+         * @summary Sign a PDF with client\'s certificate (PAdES-B-LT)
+         * @param {File} pdfFile PDF file to sign (will be processed and returned signed in base64)
+         * @param {string | null} [reason]
+         * @param {string | null} [location]
+         * @param {string | null} [contact]
+         * @param {string} [fieldName] PDF signature field name
+         * @param {boolean} [usePadesLt] Enable PAdES-B-LT (long-term archiving with embedded validation data). REQUIRES a certificate with OCSP/CRL access.
+         * @param {boolean} [useTimestamp] Enable RFC 3161 timestamping with FreeTSA (PAdES-B-T)
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        signPdfApiV1ProcessingSignPdfPost(pdfFile, reason, location, contact, fieldName, usePadesLt, useTimestamp, options) {
+            return __awaiter(this, void 0, void 0, function* () {
+                var _a, _b, _c;
+                const localVarAxiosArgs = yield localVarAxiosParamCreator.signPdfApiV1ProcessingSignPdfPost(pdfFile, reason, location, contact, fieldName, usePadesLt, useTimestamp, options);
+                const localVarOperationServerIndex = (_a = configuration === null || configuration === void 0 ? void 0 : configuration.serverIndex) !== null && _a !== void 0 ? _a : 0;
+                const localVarOperationServerBasePath = (_c = (_b = operationServerMap['ElectronicSignatureApi.signPdfApiV1ProcessingSignPdfPost']) === null || _b === void 0 ? void 0 : _b[localVarOperationServerIndex]) === null || _c === void 0 ? void 0 : _c.url;
+                return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+            });
+        },
+        /**
+         * 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).
+         * @summary Sign a PDF asynchronously (Celery)
+         * @param {File} pdfFile PDF file to sign (processed asynchronously)
+         * @param {string | null} [callbackUrl]
+         * @param {string} [webhookMode] Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL)
+         * @param {string | null} [reason]
+         * @param {string | null} [location]
+         * @param {string | null} [contact]
+         * @param {string} [fieldName] PDF signature field name
+         * @param {boolean} [usePadesLt] Enable PAdES-B-LT (long-term archiving with embedded validation data). REQUIRES a certificate with OCSP/CRL access.
+         * @param {boolean} [useTimestamp] Enable RFC 3161 timestamping with FreeTSA (PAdES-B-T)
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        signPdfAsyncApiV1ProcessingSignPdfAsyncPost(pdfFile, callbackUrl, webhookMode, reason, location, contact, fieldName, usePadesLt, useTimestamp, options) {
+            return __awaiter(this, void 0, void 0, function* () {
+                var _a, _b, _c;
+                const localVarAxiosArgs = yield localVarAxiosParamCreator.signPdfAsyncApiV1ProcessingSignPdfAsyncPost(pdfFile, callbackUrl, webhookMode, reason, location, contact, fieldName, usePadesLt, useTimestamp, options);
+                const localVarOperationServerIndex = (_a = configuration === null || configuration === void 0 ? void 0 : configuration.serverIndex) !== null && _a !== void 0 ? _a : 0;
+                const localVarOperationServerBasePath = (_c = (_b = operationServerMap['ElectronicSignatureApi.signPdfAsyncApiV1ProcessingSignPdfAsyncPost']) === null || _b === void 0 ? void 0 : _b[localVarOperationServerIndex]) === null || _c === void 0 ? void 0 : _c.url;
+                return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+            });
+        },
+        /**
+         * 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.
+         * @summary Validate electronic signatures of a PDF
+         * @param {File} pdfFile PDF file to validate (will be analyzed to detect and validate signatures)
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        validatePdfSignatureEndpointApiV1ProcessingValidatePdfSignaturePost(pdfFile, options) {
+            return __awaiter(this, void 0, void 0, function* () {
+                var _a, _b, _c;
+                const localVarAxiosArgs = yield localVarAxiosParamCreator.validatePdfSignatureEndpointApiV1ProcessingValidatePdfSignaturePost(pdfFile, options);
+                const localVarOperationServerIndex = (_a = configuration === null || configuration === void 0 ? void 0 : configuration.serverIndex) !== null && _a !== void 0 ? _a : 0;
+                const localVarOperationServerBasePath = (_c = (_b = operationServerMap['ElectronicSignatureApi.validatePdfSignatureEndpointApiV1ProcessingValidatePdfSignaturePost']) === null || _b === void 0 ? void 0 : _b[localVarOperationServerIndex]) === null || _c === void 0 ? void 0 : _c.url;
+                return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+            });
+        },
+    };
+};
+/**
+ * ElectronicSignatureApi - factory interface
+ */
+export const ElectronicSignatureApiFactory = function (configuration, basePath, axios) {
+    const localVarFp = ElectronicSignatureApiFp(configuration);
+    return {
+        /**
+         * 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)
+         * @summary Generate a self-signed X.509 test certificate
+         * @param {GenerateCertificateRequest} generateCertificateRequest
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        generateTestCertificateApiV1ProcessingGenerateTestCertificatePost(generateCertificateRequest, options) {
+            return localVarFp.generateTestCertificateApiV1ProcessingGenerateTestCertificatePost(generateCertificateRequest, options).then((request) => request(axios, basePath));
+        },
+        /**
+         * 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.
+         * @summary Sign a PDF with client\'s certificate (PAdES-B-LT)
+         * @param {File} pdfFile PDF file to sign (will be processed and returned signed in base64)
+         * @param {string | null} [reason]
+         * @param {string | null} [location]
+         * @param {string | null} [contact]
+         * @param {string} [fieldName] PDF signature field name
+         * @param {boolean} [usePadesLt] Enable PAdES-B-LT (long-term archiving with embedded validation data). REQUIRES a certificate with OCSP/CRL access.
+         * @param {boolean} [useTimestamp] Enable RFC 3161 timestamping with FreeTSA (PAdES-B-T)
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        signPdfApiV1ProcessingSignPdfPost(pdfFile, reason, location, contact, fieldName, usePadesLt, useTimestamp, options) {
+            return localVarFp.signPdfApiV1ProcessingSignPdfPost(pdfFile, reason, location, contact, fieldName, usePadesLt, useTimestamp, options).then((request) => request(axios, basePath));
+        },
+        /**
+         * 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).
+         * @summary Sign a PDF asynchronously (Celery)
+         * @param {File} pdfFile PDF file to sign (processed asynchronously)
+         * @param {string | null} [callbackUrl]
+         * @param {string} [webhookMode] Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL)
+         * @param {string | null} [reason]
+         * @param {string | null} [location]
+         * @param {string | null} [contact]
+         * @param {string} [fieldName] PDF signature field name
+         * @param {boolean} [usePadesLt] Enable PAdES-B-LT (long-term archiving with embedded validation data). REQUIRES a certificate with OCSP/CRL access.
+         * @param {boolean} [useTimestamp] Enable RFC 3161 timestamping with FreeTSA (PAdES-B-T)
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        signPdfAsyncApiV1ProcessingSignPdfAsyncPost(pdfFile, callbackUrl, webhookMode, reason, location, contact, fieldName, usePadesLt, useTimestamp, options) {
+            return localVarFp.signPdfAsyncApiV1ProcessingSignPdfAsyncPost(pdfFile, callbackUrl, webhookMode, reason, location, contact, fieldName, usePadesLt, useTimestamp, options).then((request) => request(axios, basePath));
+        },
+        /**
+         * 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.
+         * @summary Validate electronic signatures of a PDF
+         * @param {File} pdfFile PDF file to validate (will be analyzed to detect and validate signatures)
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        validatePdfSignatureEndpointApiV1ProcessingValidatePdfSignaturePost(pdfFile, options) {
+            return localVarFp.validatePdfSignatureEndpointApiV1ProcessingValidatePdfSignaturePost(pdfFile, options).then((request) => request(axios, basePath));
+        },
+    };
+};
+/**
+ * ElectronicSignatureApi - object-oriented interface
+ */
+export class ElectronicSignatureApi extends BaseAPI {
+    /**
+     * 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)
+     * @summary Generate a self-signed X.509 test certificate
+     * @param {GenerateCertificateRequest} generateCertificateRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateTestCertificateApiV1ProcessingGenerateTestCertificatePost(generateCertificateRequest, options) {
+        return ElectronicSignatureApiFp(this.configuration).generateTestCertificateApiV1ProcessingGenerateTestCertificatePost(generateCertificateRequest, options).then((request) => request(this.axios, this.basePath));
+    }
+    /**
+     * 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.
+     * @summary Sign a PDF with client\'s certificate (PAdES-B-LT)
+     * @param {File} pdfFile PDF file to sign (will be processed and returned signed in base64)
+     * @param {string | null} [reason]
+     * @param {string | null} [location]
+     * @param {string | null} [contact]
+     * @param {string} [fieldName] PDF signature field name
+     * @param {boolean} [usePadesLt] Enable PAdES-B-LT (long-term archiving with embedded validation data). REQUIRES a certificate with OCSP/CRL access.
+     * @param {boolean} [useTimestamp] Enable RFC 3161 timestamping with FreeTSA (PAdES-B-T)
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    signPdfApiV1ProcessingSignPdfPost(pdfFile, reason, location, contact, fieldName, usePadesLt, useTimestamp, options) {
+        return ElectronicSignatureApiFp(this.configuration).signPdfApiV1ProcessingSignPdfPost(pdfFile, reason, location, contact, fieldName, usePadesLt, useTimestamp, options).then((request) => request(this.axios, this.basePath));
+    }
+    /**
+     * 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).
+     * @summary Sign a PDF asynchronously (Celery)
+     * @param {File} pdfFile PDF file to sign (processed asynchronously)
+     * @param {string | null} [callbackUrl]
+     * @param {string} [webhookMode] Webhook content delivery: \\\'inline\\\' (base64 in payload) or \\\'download_url\\\' (temporary URL, 1h TTL)
+     * @param {string | null} [reason]
+     * @param {string | null} [location]
+     * @param {string | null} [contact]
+     * @param {string} [fieldName] PDF signature field name
+     * @param {boolean} [usePadesLt] Enable PAdES-B-LT (long-term archiving with embedded validation data). REQUIRES a certificate with OCSP/CRL access.
+     * @param {boolean} [useTimestamp] Enable RFC 3161 timestamping with FreeTSA (PAdES-B-T)
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    signPdfAsyncApiV1ProcessingSignPdfAsyncPost(pdfFile, callbackUrl, webhookMode, reason, location, contact, fieldName, usePadesLt, useTimestamp, options) {
+        return ElectronicSignatureApiFp(this.configuration).signPdfAsyncApiV1ProcessingSignPdfAsyncPost(pdfFile, callbackUrl, webhookMode, reason, location, contact, fieldName, usePadesLt, useTimestamp, options).then((request) => request(this.axios, this.basePath));
+    }
+    /**
+     * 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.
+     * @summary Validate electronic signatures of a PDF
+     * @param {File} pdfFile PDF file to validate (will be analyzed to detect and validate signatures)
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validatePdfSignatureEndpointApiV1ProcessingValidatePdfSignaturePost(pdfFile, options) {
+        return ElectronicSignatureApiFp(this.configuration).validatePdfSignatureEndpointApiV1ProcessingValidatePdfSignaturePost(pdfFile, options).then((request) => request(this.axios, this.basePath));
+    }
+}