@factpulse/sdk 3.0.9 → 3.0.13

package/dist/api/ereporting-api.d.ts

@@ -0,0 +1,443 @@
+/**
+ * FactPulse REST API
+ *  REST API for electronic invoicing in France: Factur-X, AFNOR PDP/PA, electronic signatures.  ## 🎯 Main Features  ### 📄 Factur-X Invoice 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)  ### ✅ Validation and Compliance - **XML Validation**: Schematron (45 to 210+ rules depending on profile) - **PDF Validation**: PDF/A-3, Factur-X XMP metadata, electronic signatures - **VeraPDF**: Strict PDF/A validation (146+ ISO 19005-3 rules) - **Asynchronous Processing**: Celery support for heavy validations (VeraPDF)  ### 📡 AFNOR PDP/PA Integration (XP Z12-013) - **Flow Submission**: Send invoices to Partner Dematerialization Platforms - **Flow Search**: View submitted invoices - **Download**: Retrieve PDF/A-3 with XML - **Directory Service**: Company search (SIREN/SIRET) - **Multi-client**: Support for multiple PDP configs per user (stored credentials or zero-storage)  ### ✍️ PDF 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 - **Certificate Generation**: Self-signed X.509 certificates for testing  ### 🔄 Asynchronous Processing - **Celery**: Asynchronous generation, validation and signing - **Polling**: Status tracking via `/tasks/{task_id}/status` - **No timeout**: Ideal for large files or heavy validations  ## 🔒 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.
+ */
+import type { Configuration } from '../configuration';
+import type { AxiosPromise, AxiosInstance, RawAxiosRequestConfig } from 'axios';
+import { type RequestArgs, BaseAPI } from '../base';
+import type { CreateAggregatedReportRequest } from '../models';
+import type { CreateEReportingRequest } from '../models';
+import type { GenerateAggregatedReportResponse } from '../models';
+import type { GenerateEReportingResponse } from '../models';
+import type { SubmitAggregatedReportRequest } from '../models';
+import type { SubmitEReportingRequest } from '../models';
+import type { SubmitEReportingResponse } from '../models';
+import type { ValidateEReportingRequest } from '../models';
+import type { ValidateEReportingResponse } from '../models';
+/**
+ * EReportingApi - axios parameter creator
+ */
+export declare const EReportingApiAxiosParamCreator: (configuration?: Configuration) => {
+    /**
+     * Generate a PPF-compliant aggregated e-reporting XML containing multiple flux types in a single file.  This endpoint creates a Report XML that can contain: - **TransactionsReport**: Invoice (10.1) AND/OR Transactions (10.3) - **PaymentsReport**: Invoice payments (10.2) AND/OR Transaction payments (10.4)  The AFNOR FlowType is automatically determined based on content: - Single type → Specific FlowType (e.g., AggregatedCustomerTransactionReport) - Multiple types → MultiFlowReport  **CategoryCode (TT-81)** must use PPF-compliant values: - TLB1: Goods deliveries - TPS1: Service provisions - TNT1: Non-taxed transactions - TMA1: Mixed transactions
+     * @summary Generate aggregated e-reporting XML (PPF-compliant)
+     * @param {CreateAggregatedReportRequest} createAggregatedReportRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateAggregatedEreportingApiV1EreportingGenerateAggregatedPost: (createAggregatedReportRequest: CreateAggregatedReportRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Generate e-reporting XML (FRR format) from structured data.  Supports all four flow types: - **10.1**: Unitary B2B international transactions (use `invoices` field) - **10.2**: Payments for B2B international invoices (use `invoicePayments` field) - **10.3**: Aggregated B2C transactions (use `transactions` field) - **10.4**: Aggregated B2C payments (use `aggregatedPayments` field)  The generated XML is compliant with DGFIP specifications and ready for submission to a PA (Plateforme Agréée).
+     * @summary Generate e-reporting XML
+     * @param {CreateEReportingRequest} createEReportingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateEreportingApiV1EreportingGeneratePost: (createEReportingRequest: CreateEReportingRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Generate e-reporting XML and return as downloadable file.
+     * @summary Generate and download e-reporting XML
+     * @param {CreateEReportingRequest} createEReportingRequest
+     * @param {string | null} [filename] Output filename (default: ereporting_{reportId}.xml)
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateEreportingDownloadApiV1EreportingGenerateDownloadPost: (createEReportingRequest: CreateEReportingRequest, filename?: string | null, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Returns the list of valid CategoryCode values (TT-81) for e-reporting transactions.  Source: Annexe 6 - Format sémantique FE e-reporting v1.9
+     * @summary List PPF-compliant category codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listCategoryCodesApiV1EreportingCategoryCodesGet: (options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Returns the list of supported e-reporting flow types with descriptions.
+     * @summary List available flow types
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listFlowTypesApiV1EreportingFlowTypesGet: (options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Generate and submit a PPF-compliant aggregated e-reporting to a PA/PDP.  Combines generation and submission in a single call. Automatically determines the AFNOR FlowType based on content.
+     * @summary Submit aggregated e-reporting to PA/PDP
+     * @param {SubmitAggregatedReportRequest} submitAggregatedReportRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitAggregatedEreportingApiV1EreportingSubmitAggregatedPost: (submitAggregatedReportRequest: SubmitAggregatedReportRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Generate and submit e-reporting to a PA (Plateforme Agréée).  Authentication strategies (same as invoices): 1. **JWT with client_uid** (recommended): PDP credentials fetched from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in request  The e-reporting is submitted using the AFNOR Flow Service API with syntax=FRR (FRench Reporting).
+     * @summary Submit e-reporting to PA/PDP
+     * @param {SubmitEReportingRequest} submitEReportingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitEreportingApiV1EreportingSubmitPost: (submitEReportingRequest: SubmitEReportingRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Submit a pre-generated e-reporting XML file directly to a PA/PDP.  This endpoint is designed for clients who generate their own PPF-compliant XML and only need FactPulse for the PDP submission.  **Process:** 1. Validates the XML against PPF XSD schemas 2. Determines the appropriate AFNOR FlowType 3. Submits to the configured PDP/PA 4. Returns the flowId for tracking  **Authentication:** Same strategies as /submit endpoint (JWT or zero-storage credentials).
+     * @summary Submit pre-generated e-reporting XML
+     * @param {File} xmlFile E-reporting XML file
+     * @param {string | null} [trackingId]
+     * @param {boolean} [skipValidation] Skip XSD validation
+     * @param {string | null} [pdpFlowServiceUrl]
+     * @param {string | null} [pdpTokenUrl]
+     * @param {string | null} [pdpClientId]
+     * @param {string | null} [pdpClientSecret]
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitXmlEreportingApiV1EreportingSubmitXmlPost: (xmlFile: File, trackingId?: string | null, skipValidation?: boolean, pdpFlowServiceUrl?: string | null, pdpTokenUrl?: string | null, pdpClientId?: string | null, pdpClientSecret?: string | null, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Validates aggregated e-reporting data without generating XML.
+     * @summary Validate aggregated e-reporting data
+     * @param {CreateAggregatedReportRequest} createAggregatedReportRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateAggregatedEreportingApiV1EreportingValidateAggregatedPost: (createAggregatedReportRequest: CreateAggregatedReportRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Validate e-reporting data without generating or submitting.  Performs: - Schema validation - Business rule validation (correct flux type vs data) - Data consistency checks (tax totals, dates, etc.)  Returns validation errors and warnings.
+     * @summary Validate e-reporting data
+     * @param {ValidateEReportingRequest} validateEReportingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateEreportingApiV1EreportingValidatePost: (validateEReportingRequest: ValidateEReportingRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Validates an e-reporting XML file against:  1. **XSD schemas**: Official PPF e-reporting XSD (structure, types, cardinality) 2. **Business rules**: ISO codes and enum validation    - Currency codes (ISO 4217: EUR, USD, GBP, etc.)    - Country codes (ISO 3166-1 alpha-2: FR, DE, US, etc.)    - Scheme IDs (0009=SIRET, 0002=SIREN, etc.)    - Role codes (UNCL 3035: SE=Seller, BY=Buyer, WK=Working party, etc.)  Returns validation status and detailed error messages if invalid.
+     * @summary Validate e-reporting XML against PPF XSD schemas and business rules
+     * @param {File} xmlFile E-reporting XML file to validate
+     * @param {boolean} [validateBusinessRules] Also validate business rules (ISO codes, enums)
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateXmlEreportingApiV1EreportingValidateXmlPost: (xmlFile: File, validateBusinessRules?: boolean, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+};
+/**
+ * EReportingApi - functional programming interface
+ */
+export declare const EReportingApiFp: (configuration?: Configuration) => {
+    /**
+     * Generate a PPF-compliant aggregated e-reporting XML containing multiple flux types in a single file.  This endpoint creates a Report XML that can contain: - **TransactionsReport**: Invoice (10.1) AND/OR Transactions (10.3) - **PaymentsReport**: Invoice payments (10.2) AND/OR Transaction payments (10.4)  The AFNOR FlowType is automatically determined based on content: - Single type → Specific FlowType (e.g., AggregatedCustomerTransactionReport) - Multiple types → MultiFlowReport  **CategoryCode (TT-81)** must use PPF-compliant values: - TLB1: Goods deliveries - TPS1: Service provisions - TNT1: Non-taxed transactions - TMA1: Mixed transactions
+     * @summary Generate aggregated e-reporting XML (PPF-compliant)
+     * @param {CreateAggregatedReportRequest} createAggregatedReportRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateAggregatedEreportingApiV1EreportingGenerateAggregatedPost(createAggregatedReportRequest: CreateAggregatedReportRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<GenerateAggregatedReportResponse>>;
+    /**
+     * Generate e-reporting XML (FRR format) from structured data.  Supports all four flow types: - **10.1**: Unitary B2B international transactions (use `invoices` field) - **10.2**: Payments for B2B international invoices (use `invoicePayments` field) - **10.3**: Aggregated B2C transactions (use `transactions` field) - **10.4**: Aggregated B2C payments (use `aggregatedPayments` field)  The generated XML is compliant with DGFIP specifications and ready for submission to a PA (Plateforme Agréée).
+     * @summary Generate e-reporting XML
+     * @param {CreateEReportingRequest} createEReportingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateEreportingApiV1EreportingGeneratePost(createEReportingRequest: CreateEReportingRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<GenerateEReportingResponse>>;
+    /**
+     * Generate e-reporting XML and return as downloadable file.
+     * @summary Generate and download e-reporting XML
+     * @param {CreateEReportingRequest} createEReportingRequest
+     * @param {string | null} [filename] Output filename (default: ereporting_{reportId}.xml)
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateEreportingDownloadApiV1EreportingGenerateDownloadPost(createEReportingRequest: CreateEReportingRequest, filename?: string | null, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
+    /**
+     * Returns the list of valid CategoryCode values (TT-81) for e-reporting transactions.  Source: Annexe 6 - Format sémantique FE e-reporting v1.9
+     * @summary List PPF-compliant category codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listCategoryCodesApiV1EreportingCategoryCodesGet(options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<{
+        [key: string]: any;
+    }>>;
+    /**
+     * Returns the list of supported e-reporting flow types with descriptions.
+     * @summary List available flow types
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listFlowTypesApiV1EreportingFlowTypesGet(options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<{
+        [key: string]: any;
+    }>>;
+    /**
+     * Generate and submit a PPF-compliant aggregated e-reporting to a PA/PDP.  Combines generation and submission in a single call. Automatically determines the AFNOR FlowType based on content.
+     * @summary Submit aggregated e-reporting to PA/PDP
+     * @param {SubmitAggregatedReportRequest} submitAggregatedReportRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitAggregatedEreportingApiV1EreportingSubmitAggregatedPost(submitAggregatedReportRequest: SubmitAggregatedReportRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SubmitEReportingResponse>>;
+    /**
+     * Generate and submit e-reporting to a PA (Plateforme Agréée).  Authentication strategies (same as invoices): 1. **JWT with client_uid** (recommended): PDP credentials fetched from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in request  The e-reporting is submitted using the AFNOR Flow Service API with syntax=FRR (FRench Reporting).
+     * @summary Submit e-reporting to PA/PDP
+     * @param {SubmitEReportingRequest} submitEReportingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitEreportingApiV1EreportingSubmitPost(submitEReportingRequest: SubmitEReportingRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SubmitEReportingResponse>>;
+    /**
+     * Submit a pre-generated e-reporting XML file directly to a PA/PDP.  This endpoint is designed for clients who generate their own PPF-compliant XML and only need FactPulse for the PDP submission.  **Process:** 1. Validates the XML against PPF XSD schemas 2. Determines the appropriate AFNOR FlowType 3. Submits to the configured PDP/PA 4. Returns the flowId for tracking  **Authentication:** Same strategies as /submit endpoint (JWT or zero-storage credentials).
+     * @summary Submit pre-generated e-reporting XML
+     * @param {File} xmlFile E-reporting XML file
+     * @param {string | null} [trackingId]
+     * @param {boolean} [skipValidation] Skip XSD validation
+     * @param {string | null} [pdpFlowServiceUrl]
+     * @param {string | null} [pdpTokenUrl]
+     * @param {string | null} [pdpClientId]
+     * @param {string | null} [pdpClientSecret]
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitXmlEreportingApiV1EreportingSubmitXmlPost(xmlFile: File, trackingId?: string | null, skipValidation?: boolean, pdpFlowServiceUrl?: string | null, pdpTokenUrl?: string | null, pdpClientId?: string | null, pdpClientSecret?: string | null, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SubmitEReportingResponse>>;
+    /**
+     * Validates aggregated e-reporting data without generating XML.
+     * @summary Validate aggregated e-reporting data
+     * @param {CreateAggregatedReportRequest} createAggregatedReportRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateAggregatedEreportingApiV1EreportingValidateAggregatedPost(createAggregatedReportRequest: CreateAggregatedReportRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<{
+        [key: string]: any;
+    }>>;
+    /**
+     * Validate e-reporting data without generating or submitting.  Performs: - Schema validation - Business rule validation (correct flux type vs data) - Data consistency checks (tax totals, dates, etc.)  Returns validation errors and warnings.
+     * @summary Validate e-reporting data
+     * @param {ValidateEReportingRequest} validateEReportingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateEreportingApiV1EreportingValidatePost(validateEReportingRequest: ValidateEReportingRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<ValidateEReportingResponse>>;
+    /**
+     * Validates an e-reporting XML file against:  1. **XSD schemas**: Official PPF e-reporting XSD (structure, types, cardinality) 2. **Business rules**: ISO codes and enum validation    - Currency codes (ISO 4217: EUR, USD, GBP, etc.)    - Country codes (ISO 3166-1 alpha-2: FR, DE, US, etc.)    - Scheme IDs (0009=SIRET, 0002=SIREN, etc.)    - Role codes (UNCL 3035: SE=Seller, BY=Buyer, WK=Working party, etc.)  Returns validation status and detailed error messages if invalid.
+     * @summary Validate e-reporting XML against PPF XSD schemas and business rules
+     * @param {File} xmlFile E-reporting XML file to validate
+     * @param {boolean} [validateBusinessRules] Also validate business rules (ISO codes, enums)
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateXmlEreportingApiV1EreportingValidateXmlPost(xmlFile: File, validateBusinessRules?: boolean, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<{
+        [key: string]: any;
+    }>>;
+};
+/**
+ * EReportingApi - factory interface
+ */
+export declare const EReportingApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
+    /**
+     * Generate a PPF-compliant aggregated e-reporting XML containing multiple flux types in a single file.  This endpoint creates a Report XML that can contain: - **TransactionsReport**: Invoice (10.1) AND/OR Transactions (10.3) - **PaymentsReport**: Invoice payments (10.2) AND/OR Transaction payments (10.4)  The AFNOR FlowType is automatically determined based on content: - Single type → Specific FlowType (e.g., AggregatedCustomerTransactionReport) - Multiple types → MultiFlowReport  **CategoryCode (TT-81)** must use PPF-compliant values: - TLB1: Goods deliveries - TPS1: Service provisions - TNT1: Non-taxed transactions - TMA1: Mixed transactions
+     * @summary Generate aggregated e-reporting XML (PPF-compliant)
+     * @param {CreateAggregatedReportRequest} createAggregatedReportRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateAggregatedEreportingApiV1EreportingGenerateAggregatedPost(createAggregatedReportRequest: CreateAggregatedReportRequest, options?: RawAxiosRequestConfig): AxiosPromise<GenerateAggregatedReportResponse>;
+    /**
+     * Generate e-reporting XML (FRR format) from structured data.  Supports all four flow types: - **10.1**: Unitary B2B international transactions (use `invoices` field) - **10.2**: Payments for B2B international invoices (use `invoicePayments` field) - **10.3**: Aggregated B2C transactions (use `transactions` field) - **10.4**: Aggregated B2C payments (use `aggregatedPayments` field)  The generated XML is compliant with DGFIP specifications and ready for submission to a PA (Plateforme Agréée).
+     * @summary Generate e-reporting XML
+     * @param {CreateEReportingRequest} createEReportingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateEreportingApiV1EreportingGeneratePost(createEReportingRequest: CreateEReportingRequest, options?: RawAxiosRequestConfig): AxiosPromise<GenerateEReportingResponse>;
+    /**
+     * Generate e-reporting XML and return as downloadable file.
+     * @summary Generate and download e-reporting XML
+     * @param {CreateEReportingRequest} createEReportingRequest
+     * @param {string | null} [filename] Output filename (default: ereporting_{reportId}.xml)
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateEreportingDownloadApiV1EreportingGenerateDownloadPost(createEReportingRequest: CreateEReportingRequest, filename?: string | null, options?: RawAxiosRequestConfig): AxiosPromise<void>;
+    /**
+     * Returns the list of valid CategoryCode values (TT-81) for e-reporting transactions.  Source: Annexe 6 - Format sémantique FE e-reporting v1.9
+     * @summary List PPF-compliant category codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listCategoryCodesApiV1EreportingCategoryCodesGet(options?: RawAxiosRequestConfig): AxiosPromise<{
+        [key: string]: any;
+    }>;
+    /**
+     * Returns the list of supported e-reporting flow types with descriptions.
+     * @summary List available flow types
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listFlowTypesApiV1EreportingFlowTypesGet(options?: RawAxiosRequestConfig): AxiosPromise<{
+        [key: string]: any;
+    }>;
+    /**
+     * Generate and submit a PPF-compliant aggregated e-reporting to a PA/PDP.  Combines generation and submission in a single call. Automatically determines the AFNOR FlowType based on content.
+     * @summary Submit aggregated e-reporting to PA/PDP
+     * @param {SubmitAggregatedReportRequest} submitAggregatedReportRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitAggregatedEreportingApiV1EreportingSubmitAggregatedPost(submitAggregatedReportRequest: SubmitAggregatedReportRequest, options?: RawAxiosRequestConfig): AxiosPromise<SubmitEReportingResponse>;
+    /**
+     * Generate and submit e-reporting to a PA (Plateforme Agréée).  Authentication strategies (same as invoices): 1. **JWT with client_uid** (recommended): PDP credentials fetched from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in request  The e-reporting is submitted using the AFNOR Flow Service API with syntax=FRR (FRench Reporting).
+     * @summary Submit e-reporting to PA/PDP
+     * @param {SubmitEReportingRequest} submitEReportingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitEreportingApiV1EreportingSubmitPost(submitEReportingRequest: SubmitEReportingRequest, options?: RawAxiosRequestConfig): AxiosPromise<SubmitEReportingResponse>;
+    /**
+     * Submit a pre-generated e-reporting XML file directly to a PA/PDP.  This endpoint is designed for clients who generate their own PPF-compliant XML and only need FactPulse for the PDP submission.  **Process:** 1. Validates the XML against PPF XSD schemas 2. Determines the appropriate AFNOR FlowType 3. Submits to the configured PDP/PA 4. Returns the flowId for tracking  **Authentication:** Same strategies as /submit endpoint (JWT or zero-storage credentials).
+     * @summary Submit pre-generated e-reporting XML
+     * @param {File} xmlFile E-reporting XML file
+     * @param {string | null} [trackingId]
+     * @param {boolean} [skipValidation] Skip XSD validation
+     * @param {string | null} [pdpFlowServiceUrl]
+     * @param {string | null} [pdpTokenUrl]
+     * @param {string | null} [pdpClientId]
+     * @param {string | null} [pdpClientSecret]
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitXmlEreportingApiV1EreportingSubmitXmlPost(xmlFile: File, trackingId?: string | null, skipValidation?: boolean, pdpFlowServiceUrl?: string | null, pdpTokenUrl?: string | null, pdpClientId?: string | null, pdpClientSecret?: string | null, options?: RawAxiosRequestConfig): AxiosPromise<SubmitEReportingResponse>;
+    /**
+     * Validates aggregated e-reporting data without generating XML.
+     * @summary Validate aggregated e-reporting data
+     * @param {CreateAggregatedReportRequest} createAggregatedReportRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateAggregatedEreportingApiV1EreportingValidateAggregatedPost(createAggregatedReportRequest: CreateAggregatedReportRequest, options?: RawAxiosRequestConfig): AxiosPromise<{
+        [key: string]: any;
+    }>;
+    /**
+     * Validate e-reporting data without generating or submitting.  Performs: - Schema validation - Business rule validation (correct flux type vs data) - Data consistency checks (tax totals, dates, etc.)  Returns validation errors and warnings.
+     * @summary Validate e-reporting data
+     * @param {ValidateEReportingRequest} validateEReportingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateEreportingApiV1EreportingValidatePost(validateEReportingRequest: ValidateEReportingRequest, options?: RawAxiosRequestConfig): AxiosPromise<ValidateEReportingResponse>;
+    /**
+     * Validates an e-reporting XML file against:  1. **XSD schemas**: Official PPF e-reporting XSD (structure, types, cardinality) 2. **Business rules**: ISO codes and enum validation    - Currency codes (ISO 4217: EUR, USD, GBP, etc.)    - Country codes (ISO 3166-1 alpha-2: FR, DE, US, etc.)    - Scheme IDs (0009=SIRET, 0002=SIREN, etc.)    - Role codes (UNCL 3035: SE=Seller, BY=Buyer, WK=Working party, etc.)  Returns validation status and detailed error messages if invalid.
+     * @summary Validate e-reporting XML against PPF XSD schemas and business rules
+     * @param {File} xmlFile E-reporting XML file to validate
+     * @param {boolean} [validateBusinessRules] Also validate business rules (ISO codes, enums)
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateXmlEreportingApiV1EreportingValidateXmlPost(xmlFile: File, validateBusinessRules?: boolean, options?: RawAxiosRequestConfig): AxiosPromise<{
+        [key: string]: any;
+    }>;
+};
+/**
+ * EReportingApi - object-oriented interface
+ */
+export declare class EReportingApi extends BaseAPI {
+    /**
+     * Generate a PPF-compliant aggregated e-reporting XML containing multiple flux types in a single file.  This endpoint creates a Report XML that can contain: - **TransactionsReport**: Invoice (10.1) AND/OR Transactions (10.3) - **PaymentsReport**: Invoice payments (10.2) AND/OR Transaction payments (10.4)  The AFNOR FlowType is automatically determined based on content: - Single type → Specific FlowType (e.g., AggregatedCustomerTransactionReport) - Multiple types → MultiFlowReport  **CategoryCode (TT-81)** must use PPF-compliant values: - TLB1: Goods deliveries - TPS1: Service provisions - TNT1: Non-taxed transactions - TMA1: Mixed transactions
+     * @summary Generate aggregated e-reporting XML (PPF-compliant)
+     * @param {CreateAggregatedReportRequest} createAggregatedReportRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateAggregatedEreportingApiV1EreportingGenerateAggregatedPost(createAggregatedReportRequest: CreateAggregatedReportRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<GenerateAggregatedReportResponse, any, {}>>;
+    /**
+     * Generate e-reporting XML (FRR format) from structured data.  Supports all four flow types: - **10.1**: Unitary B2B international transactions (use `invoices` field) - **10.2**: Payments for B2B international invoices (use `invoicePayments` field) - **10.3**: Aggregated B2C transactions (use `transactions` field) - **10.4**: Aggregated B2C payments (use `aggregatedPayments` field)  The generated XML is compliant with DGFIP specifications and ready for submission to a PA (Plateforme Agréée).
+     * @summary Generate e-reporting XML
+     * @param {CreateEReportingRequest} createEReportingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateEreportingApiV1EreportingGeneratePost(createEReportingRequest: CreateEReportingRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<GenerateEReportingResponse, any, {}>>;
+    /**
+     * Generate e-reporting XML and return as downloadable file.
+     * @summary Generate and download e-reporting XML
+     * @param {CreateEReportingRequest} createEReportingRequest
+     * @param {string | null} [filename] Output filename (default: ereporting_{reportId}.xml)
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateEreportingDownloadApiV1EreportingGenerateDownloadPost(createEReportingRequest: CreateEReportingRequest, filename?: string | null, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<void, any, {}>>;
+    /**
+     * Returns the list of valid CategoryCode values (TT-81) for e-reporting transactions.  Source: Annexe 6 - Format sémantique FE e-reporting v1.9
+     * @summary List PPF-compliant category codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listCategoryCodesApiV1EreportingCategoryCodesGet(options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<{
+        [key: string]: any;
+    }, any, {}>>;
+    /**
+     * Returns the list of supported e-reporting flow types with descriptions.
+     * @summary List available flow types
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listFlowTypesApiV1EreportingFlowTypesGet(options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<{
+        [key: string]: any;
+    }, any, {}>>;
+    /**
+     * Generate and submit a PPF-compliant aggregated e-reporting to a PA/PDP.  Combines generation and submission in a single call. Automatically determines the AFNOR FlowType based on content.
+     * @summary Submit aggregated e-reporting to PA/PDP
+     * @param {SubmitAggregatedReportRequest} submitAggregatedReportRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitAggregatedEreportingApiV1EreportingSubmitAggregatedPost(submitAggregatedReportRequest: SubmitAggregatedReportRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SubmitEReportingResponse, any, {}>>;
+    /**
+     * Generate and submit e-reporting to a PA (Plateforme Agréée).  Authentication strategies (same as invoices): 1. **JWT with client_uid** (recommended): PDP credentials fetched from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in request  The e-reporting is submitted using the AFNOR Flow Service API with syntax=FRR (FRench Reporting).
+     * @summary Submit e-reporting to PA/PDP
+     * @param {SubmitEReportingRequest} submitEReportingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitEreportingApiV1EreportingSubmitPost(submitEReportingRequest: SubmitEReportingRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SubmitEReportingResponse, any, {}>>;
+    /**
+     * Submit a pre-generated e-reporting XML file directly to a PA/PDP.  This endpoint is designed for clients who generate their own PPF-compliant XML and only need FactPulse for the PDP submission.  **Process:** 1. Validates the XML against PPF XSD schemas 2. Determines the appropriate AFNOR FlowType 3. Submits to the configured PDP/PA 4. Returns the flowId for tracking  **Authentication:** Same strategies as /submit endpoint (JWT or zero-storage credentials).
+     * @summary Submit pre-generated e-reporting XML
+     * @param {File} xmlFile E-reporting XML file
+     * @param {string | null} [trackingId]
+     * @param {boolean} [skipValidation] Skip XSD validation
+     * @param {string | null} [pdpFlowServiceUrl]
+     * @param {string | null} [pdpTokenUrl]
+     * @param {string | null} [pdpClientId]
+     * @param {string | null} [pdpClientSecret]
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitXmlEreportingApiV1EreportingSubmitXmlPost(xmlFile: File, trackingId?: string | null, skipValidation?: boolean, pdpFlowServiceUrl?: string | null, pdpTokenUrl?: string | null, pdpClientId?: string | null, pdpClientSecret?: string | null, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SubmitEReportingResponse, any, {}>>;
+    /**
+     * Validates aggregated e-reporting data without generating XML.
+     * @summary Validate aggregated e-reporting data
+     * @param {CreateAggregatedReportRequest} createAggregatedReportRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateAggregatedEreportingApiV1EreportingValidateAggregatedPost(createAggregatedReportRequest: CreateAggregatedReportRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<{
+        [key: string]: any;
+    }, any, {}>>;
+    /**
+     * Validate e-reporting data without generating or submitting.  Performs: - Schema validation - Business rule validation (correct flux type vs data) - Data consistency checks (tax totals, dates, etc.)  Returns validation errors and warnings.
+     * @summary Validate e-reporting data
+     * @param {ValidateEReportingRequest} validateEReportingRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateEreportingApiV1EreportingValidatePost(validateEReportingRequest: ValidateEReportingRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<ValidateEReportingResponse, any, {}>>;
+    /**
+     * Validates an e-reporting XML file against:  1. **XSD schemas**: Official PPF e-reporting XSD (structure, types, cardinality) 2. **Business rules**: ISO codes and enum validation    - Currency codes (ISO 4217: EUR, USD, GBP, etc.)    - Country codes (ISO 3166-1 alpha-2: FR, DE, US, etc.)    - Scheme IDs (0009=SIRET, 0002=SIREN, etc.)    - Role codes (UNCL 3035: SE=Seller, BY=Buyer, WK=Working party, etc.)  Returns validation status and detailed error messages if invalid.
+     * @summary Validate e-reporting XML against PPF XSD schemas and business rules
+     * @param {File} xmlFile E-reporting XML file to validate
+     * @param {boolean} [validateBusinessRules] Also validate business rules (ISO codes, enums)
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateXmlEreportingApiV1EreportingValidateXmlPost(xmlFile: File, validateBusinessRules?: boolean, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<{
+        [key: string]: any;
+    }, any, {}>>;
+}