@factpulse/sdk 4.0.0 → 4.0.2

package/dist/api/flux6-invoice-lifecycle-cdarapi.d.ts

@@ -0,0 +1,361 @@
+/**
+ * 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.
+ */
+import type { Configuration } from '../configuration';
+import type { AxiosPromise, AxiosInstance, RawAxiosRequestConfig } from 'axios';
+import { type RequestArgs, BaseAPI } from '../base';
+import type { ActionCodesResponse } from '../models';
+import type { CreateCDARRequest } from '../models';
+import type { EncaisseeRequest } from '../models';
+import type { GenerateCDARResponse } from '../models';
+import type { ReasonCodesResponse } from '../models';
+import type { RefuseeRequest } from '../models';
+import type { SimplifiedCDARResponse } from '../models';
+import type { StatusCodesResponse } from '../models';
+import type { SubmitCDARRequest } from '../models';
+import type { SubmitCDARResponse } from '../models';
+import type { SubmitCDARXMLRequest } from '../models';
+import type { ValidateCDARRequest } from '../models';
+import type { ValidateCDARResponse } from '../models';
+/**
+ * Flux6InvoiceLifecycleCDARApi - axios parameter creator
+ */
+export declare const Flux6InvoiceLifecycleCDARApiAxiosParamCreator: (configuration?: Configuration) => {
+    /**
+     * Generate a CDAR XML message (Cross Domain Acknowledgement and Response) to communicate the status of an invoice.  **Message types:** - **23** (Processing): Standard lifecycle message - **305** (Transmission): Inter-platform transmission message  **Business rules:** - BR-FR-CDV-14: Status 212 (PAID) requires a paid amount - BR-FR-CDV-15: Statuses 206/207/208/210/213/501 require a reason code
+     * @summary Generate a CDAR message
+     * @param {CreateCDARRequest} createCDARRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateCdarApiV1CdarGeneratePost: (createCDARRequest: CreateCDARRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Returns the complete list of action codes (BR-FR-CDV-CL-10).  These codes indicate the requested action on the invoice.
+     * @summary List of CDAR action codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getActionCodesApiV1CdarActionCodesGet: (options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Returns the complete list of status reason codes (BR-FR-CDV-CL-09).  These codes explain the reason for a particular status.
+     * @summary List of CDAR reason codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getReasonCodesApiV1CdarReasonCodesGet: (options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Returns the complete list of invoice status codes (BR-FR-CDV-CL-06).  These codes indicate the lifecycle state of an invoice.
+     * @summary List of CDAR status codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getStatusCodesApiV1CdarStatusCodesGet: (options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Generate a CDAR message and submit it to the PA/PDP platform.  **Authentication strategies:** 1. **JWT with client_uid** (recommended): PDP credentials retrieved from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in the request  **Flow types (flowType):** - `CustomerInvoiceLC`: Client-side lifecycle (buyer) - `SupplierInvoiceLC`: Supplier-side lifecycle (seller)
+     * @summary Generate and submit a CDAR message
+     * @param {SubmitCDARRequest} submitCDARRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitCdarApiV1CdarSubmitPost: (submitCDARRequest: SubmitCDARRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Submit a pre-generated CDAR XML message to the PA/PDP platform.  Useful for submitting XML generated by other systems.  **Validation:** The XML is validated against XSD and Schematron BR-FR-CDV rules BEFORE submission. Invalid XML will be rejected with detailed error messages.  **Authentication strategies:** 1. **JWT with client_uid** (recommended): PDP credentials retrieved from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in the request
+     * @summary Submit a pre-generated CDAR XML
+     * @param {SubmitCDARXMLRequest} submitCDARXMLRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitCdarXmlApiV1CdarSubmitXmlPost: (submitCDARXMLRequest: SubmitCDARXMLRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * **Simplified endpoint for OD** - Submit a PAID status (212) for an **ISSUED** invoice.  This status is **mandatory for PPF** (BR-FR-CDV-14 requires the paid amount).  **Use case:** The **seller** confirms payment receipt for an invoice they issued.  **Who issues this status?** - **Issuer (IssuerTradeParty):** The seller (SE = Seller) who received payment - **Recipient (RecipientTradeParty):** The buyer (BY = Buyer) who paid  **Reference:** XP Z12-014 Annex B, example UC1_F202500003_07-CDV-212_Encaissee.xml  **Authentication:** JWT Bearer (recommended) or PDP credentials in request.
+     * @summary [Simplified] Submit PAID status (212) - Issued invoice
+     * @param {EncaisseeRequest} encaisseeRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitEncaisseeApiV1CdarEncaisseePost: (encaisseeRequest: EncaisseeRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * **Simplified endpoint for OD** - Submit a REFUSED status (210) for a **RECEIVED** invoice.  This status is **mandatory for PPF** (BR-FR-CDV-15 requires a reason code).  **Use case:** The **buyer** refuses an invoice they received.  **Who issues this status?** - **Issuer (IssuerTradeParty):** The buyer (BY = Buyer) refusing the invoice - **Recipient (RecipientTradeParty):** The seller (SE = Seller) who issued the invoice  **Reference:** XP Z12-014 Annex B, example UC3_F202500005_04-CDV-210_Refusee.xml  **Allowed reason codes (BR-FR-CDV-CL-09):** - `TX_TVA_ERR`: Incorrect VAT rate - `MONTANTTOTAL_ERR`: Incorrect total amount - `CALCUL_ERR`: Calculation error - `NON_CONFORME`: Non-compliant - `DOUBLON`: Duplicate - `DEST_ERR`: Wrong recipient - `TRANSAC_INC`: Incomplete transaction - `EMMET_INC`: Unknown issuer - `CONTRAT_TERM`: Contract terminated - `DOUBLE_FACT`: Double billing - `CMD_ERR`: Order error - `ADR_ERR`: Address error - `REF_CT_ABSENT`: Missing contract reference  **Authentication:** JWT Bearer (recommended) or PDP credentials in request.
+     * @summary [Simplified] Submit REFUSED status (210) - Received invoice
+     * @param {RefuseeRequest} refuseeRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitRefuseeApiV1CdarRefuseePost: (refuseeRequest: RefuseeRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Validate CDAR structured data without generating XML.  **Note:** This endpoint validates structured data fields only. Use `/validate-xml` to validate a pre-generated CDAR XML file against XSD and Schematron.  Checks: - Field formats (SIREN, dates, etc.) - Enum codes (status, reason, action) - Business rules BR-FR-CDV-*
+     * @summary Validate CDAR structured data
+     * @param {ValidateCDARRequest} validateCDARRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateCdarApiV1CdarValidatePost: (validateCDARRequest: ValidateCDARRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Validates a CDAR XML file against:  1. **XSD schema**: UN/CEFACT D22B CrossDomainAcknowledgementAndResponse 2. **Schematron BR-FR-CDV**: French business rules for invoice lifecycle  Returns validation status and detailed error messages if invalid.  **Note:** Use `/validate` to validate structured data fields (JSON).
+     * @summary Validate CDAR XML against XSD and Schematron BR-FR-CDV
+     * @param {File} xmlFile CDAR XML file to validate
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateXmlCdarApiV1CdarValidateXmlPost: (xmlFile: File, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+};
+/**
+ * Flux6InvoiceLifecycleCDARApi - functional programming interface
+ */
+export declare const Flux6InvoiceLifecycleCDARApiFp: (configuration?: Configuration) => {
+    /**
+     * Generate a CDAR XML message (Cross Domain Acknowledgement and Response) to communicate the status of an invoice.  **Message types:** - **23** (Processing): Standard lifecycle message - **305** (Transmission): Inter-platform transmission message  **Business rules:** - BR-FR-CDV-14: Status 212 (PAID) requires a paid amount - BR-FR-CDV-15: Statuses 206/207/208/210/213/501 require a reason code
+     * @summary Generate a CDAR message
+     * @param {CreateCDARRequest} createCDARRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateCdarApiV1CdarGeneratePost(createCDARRequest: CreateCDARRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<GenerateCDARResponse>>;
+    /**
+     * Returns the complete list of action codes (BR-FR-CDV-CL-10).  These codes indicate the requested action on the invoice.
+     * @summary List of CDAR action codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getActionCodesApiV1CdarActionCodesGet(options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<ActionCodesResponse>>;
+    /**
+     * Returns the complete list of status reason codes (BR-FR-CDV-CL-09).  These codes explain the reason for a particular status.
+     * @summary List of CDAR reason codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getReasonCodesApiV1CdarReasonCodesGet(options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<ReasonCodesResponse>>;
+    /**
+     * Returns the complete list of invoice status codes (BR-FR-CDV-CL-06).  These codes indicate the lifecycle state of an invoice.
+     * @summary List of CDAR status codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getStatusCodesApiV1CdarStatusCodesGet(options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<StatusCodesResponse>>;
+    /**
+     * Generate a CDAR message and submit it to the PA/PDP platform.  **Authentication strategies:** 1. **JWT with client_uid** (recommended): PDP credentials retrieved from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in the request  **Flow types (flowType):** - `CustomerInvoiceLC`: Client-side lifecycle (buyer) - `SupplierInvoiceLC`: Supplier-side lifecycle (seller)
+     * @summary Generate and submit a CDAR message
+     * @param {SubmitCDARRequest} submitCDARRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitCdarApiV1CdarSubmitPost(submitCDARRequest: SubmitCDARRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SubmitCDARResponse>>;
+    /**
+     * Submit a pre-generated CDAR XML message to the PA/PDP platform.  Useful for submitting XML generated by other systems.  **Validation:** The XML is validated against XSD and Schematron BR-FR-CDV rules BEFORE submission. Invalid XML will be rejected with detailed error messages.  **Authentication strategies:** 1. **JWT with client_uid** (recommended): PDP credentials retrieved from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in the request
+     * @summary Submit a pre-generated CDAR XML
+     * @param {SubmitCDARXMLRequest} submitCDARXMLRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitCdarXmlApiV1CdarSubmitXmlPost(submitCDARXMLRequest: SubmitCDARXMLRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SubmitCDARResponse>>;
+    /**
+     * **Simplified endpoint for OD** - Submit a PAID status (212) for an **ISSUED** invoice.  This status is **mandatory for PPF** (BR-FR-CDV-14 requires the paid amount).  **Use case:** The **seller** confirms payment receipt for an invoice they issued.  **Who issues this status?** - **Issuer (IssuerTradeParty):** The seller (SE = Seller) who received payment - **Recipient (RecipientTradeParty):** The buyer (BY = Buyer) who paid  **Reference:** XP Z12-014 Annex B, example UC1_F202500003_07-CDV-212_Encaissee.xml  **Authentication:** JWT Bearer (recommended) or PDP credentials in request.
+     * @summary [Simplified] Submit PAID status (212) - Issued invoice
+     * @param {EncaisseeRequest} encaisseeRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitEncaisseeApiV1CdarEncaisseePost(encaisseeRequest: EncaisseeRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SimplifiedCDARResponse>>;
+    /**
+     * **Simplified endpoint for OD** - Submit a REFUSED status (210) for a **RECEIVED** invoice.  This status is **mandatory for PPF** (BR-FR-CDV-15 requires a reason code).  **Use case:** The **buyer** refuses an invoice they received.  **Who issues this status?** - **Issuer (IssuerTradeParty):** The buyer (BY = Buyer) refusing the invoice - **Recipient (RecipientTradeParty):** The seller (SE = Seller) who issued the invoice  **Reference:** XP Z12-014 Annex B, example UC3_F202500005_04-CDV-210_Refusee.xml  **Allowed reason codes (BR-FR-CDV-CL-09):** - `TX_TVA_ERR`: Incorrect VAT rate - `MONTANTTOTAL_ERR`: Incorrect total amount - `CALCUL_ERR`: Calculation error - `NON_CONFORME`: Non-compliant - `DOUBLON`: Duplicate - `DEST_ERR`: Wrong recipient - `TRANSAC_INC`: Incomplete transaction - `EMMET_INC`: Unknown issuer - `CONTRAT_TERM`: Contract terminated - `DOUBLE_FACT`: Double billing - `CMD_ERR`: Order error - `ADR_ERR`: Address error - `REF_CT_ABSENT`: Missing contract reference  **Authentication:** JWT Bearer (recommended) or PDP credentials in request.
+     * @summary [Simplified] Submit REFUSED status (210) - Received invoice
+     * @param {RefuseeRequest} refuseeRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitRefuseeApiV1CdarRefuseePost(refuseeRequest: RefuseeRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SimplifiedCDARResponse>>;
+    /**
+     * Validate CDAR structured data without generating XML.  **Note:** This endpoint validates structured data fields only. Use `/validate-xml` to validate a pre-generated CDAR XML file against XSD and Schematron.  Checks: - Field formats (SIREN, dates, etc.) - Enum codes (status, reason, action) - Business rules BR-FR-CDV-*
+     * @summary Validate CDAR structured data
+     * @param {ValidateCDARRequest} validateCDARRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateCdarApiV1CdarValidatePost(validateCDARRequest: ValidateCDARRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<ValidateCDARResponse>>;
+    /**
+     * Validates a CDAR XML file against:  1. **XSD schema**: UN/CEFACT D22B CrossDomainAcknowledgementAndResponse 2. **Schematron BR-FR-CDV**: French business rules for invoice lifecycle  Returns validation status and detailed error messages if invalid.  **Note:** Use `/validate` to validate structured data fields (JSON).
+     * @summary Validate CDAR XML against XSD and Schematron BR-FR-CDV
+     * @param {File} xmlFile CDAR XML file to validate
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateXmlCdarApiV1CdarValidateXmlPost(xmlFile: File, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<{
+        [key: string]: any;
+    }>>;
+};
+/**
+ * Flux6InvoiceLifecycleCDARApi - factory interface
+ */
+export declare const Flux6InvoiceLifecycleCDARApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
+    /**
+     * Generate a CDAR XML message (Cross Domain Acknowledgement and Response) to communicate the status of an invoice.  **Message types:** - **23** (Processing): Standard lifecycle message - **305** (Transmission): Inter-platform transmission message  **Business rules:** - BR-FR-CDV-14: Status 212 (PAID) requires a paid amount - BR-FR-CDV-15: Statuses 206/207/208/210/213/501 require a reason code
+     * @summary Generate a CDAR message
+     * @param {CreateCDARRequest} createCDARRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateCdarApiV1CdarGeneratePost(createCDARRequest: CreateCDARRequest, options?: RawAxiosRequestConfig): AxiosPromise<GenerateCDARResponse>;
+    /**
+     * Returns the complete list of action codes (BR-FR-CDV-CL-10).  These codes indicate the requested action on the invoice.
+     * @summary List of CDAR action codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getActionCodesApiV1CdarActionCodesGet(options?: RawAxiosRequestConfig): AxiosPromise<ActionCodesResponse>;
+    /**
+     * Returns the complete list of status reason codes (BR-FR-CDV-CL-09).  These codes explain the reason for a particular status.
+     * @summary List of CDAR reason codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getReasonCodesApiV1CdarReasonCodesGet(options?: RawAxiosRequestConfig): AxiosPromise<ReasonCodesResponse>;
+    /**
+     * Returns the complete list of invoice status codes (BR-FR-CDV-CL-06).  These codes indicate the lifecycle state of an invoice.
+     * @summary List of CDAR status codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getStatusCodesApiV1CdarStatusCodesGet(options?: RawAxiosRequestConfig): AxiosPromise<StatusCodesResponse>;
+    /**
+     * Generate a CDAR message and submit it to the PA/PDP platform.  **Authentication strategies:** 1. **JWT with client_uid** (recommended): PDP credentials retrieved from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in the request  **Flow types (flowType):** - `CustomerInvoiceLC`: Client-side lifecycle (buyer) - `SupplierInvoiceLC`: Supplier-side lifecycle (seller)
+     * @summary Generate and submit a CDAR message
+     * @param {SubmitCDARRequest} submitCDARRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitCdarApiV1CdarSubmitPost(submitCDARRequest: SubmitCDARRequest, options?: RawAxiosRequestConfig): AxiosPromise<SubmitCDARResponse>;
+    /**
+     * Submit a pre-generated CDAR XML message to the PA/PDP platform.  Useful for submitting XML generated by other systems.  **Validation:** The XML is validated against XSD and Schematron BR-FR-CDV rules BEFORE submission. Invalid XML will be rejected with detailed error messages.  **Authentication strategies:** 1. **JWT with client_uid** (recommended): PDP credentials retrieved from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in the request
+     * @summary Submit a pre-generated CDAR XML
+     * @param {SubmitCDARXMLRequest} submitCDARXMLRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitCdarXmlApiV1CdarSubmitXmlPost(submitCDARXMLRequest: SubmitCDARXMLRequest, options?: RawAxiosRequestConfig): AxiosPromise<SubmitCDARResponse>;
+    /**
+     * **Simplified endpoint for OD** - Submit a PAID status (212) for an **ISSUED** invoice.  This status is **mandatory for PPF** (BR-FR-CDV-14 requires the paid amount).  **Use case:** The **seller** confirms payment receipt for an invoice they issued.  **Who issues this status?** - **Issuer (IssuerTradeParty):** The seller (SE = Seller) who received payment - **Recipient (RecipientTradeParty):** The buyer (BY = Buyer) who paid  **Reference:** XP Z12-014 Annex B, example UC1_F202500003_07-CDV-212_Encaissee.xml  **Authentication:** JWT Bearer (recommended) or PDP credentials in request.
+     * @summary [Simplified] Submit PAID status (212) - Issued invoice
+     * @param {EncaisseeRequest} encaisseeRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitEncaisseeApiV1CdarEncaisseePost(encaisseeRequest: EncaisseeRequest, options?: RawAxiosRequestConfig): AxiosPromise<SimplifiedCDARResponse>;
+    /**
+     * **Simplified endpoint for OD** - Submit a REFUSED status (210) for a **RECEIVED** invoice.  This status is **mandatory for PPF** (BR-FR-CDV-15 requires a reason code).  **Use case:** The **buyer** refuses an invoice they received.  **Who issues this status?** - **Issuer (IssuerTradeParty):** The buyer (BY = Buyer) refusing the invoice - **Recipient (RecipientTradeParty):** The seller (SE = Seller) who issued the invoice  **Reference:** XP Z12-014 Annex B, example UC3_F202500005_04-CDV-210_Refusee.xml  **Allowed reason codes (BR-FR-CDV-CL-09):** - `TX_TVA_ERR`: Incorrect VAT rate - `MONTANTTOTAL_ERR`: Incorrect total amount - `CALCUL_ERR`: Calculation error - `NON_CONFORME`: Non-compliant - `DOUBLON`: Duplicate - `DEST_ERR`: Wrong recipient - `TRANSAC_INC`: Incomplete transaction - `EMMET_INC`: Unknown issuer - `CONTRAT_TERM`: Contract terminated - `DOUBLE_FACT`: Double billing - `CMD_ERR`: Order error - `ADR_ERR`: Address error - `REF_CT_ABSENT`: Missing contract reference  **Authentication:** JWT Bearer (recommended) or PDP credentials in request.
+     * @summary [Simplified] Submit REFUSED status (210) - Received invoice
+     * @param {RefuseeRequest} refuseeRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitRefuseeApiV1CdarRefuseePost(refuseeRequest: RefuseeRequest, options?: RawAxiosRequestConfig): AxiosPromise<SimplifiedCDARResponse>;
+    /**
+     * Validate CDAR structured data without generating XML.  **Note:** This endpoint validates structured data fields only. Use `/validate-xml` to validate a pre-generated CDAR XML file against XSD and Schematron.  Checks: - Field formats (SIREN, dates, etc.) - Enum codes (status, reason, action) - Business rules BR-FR-CDV-*
+     * @summary Validate CDAR structured data
+     * @param {ValidateCDARRequest} validateCDARRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateCdarApiV1CdarValidatePost(validateCDARRequest: ValidateCDARRequest, options?: RawAxiosRequestConfig): AxiosPromise<ValidateCDARResponse>;
+    /**
+     * Validates a CDAR XML file against:  1. **XSD schema**: UN/CEFACT D22B CrossDomainAcknowledgementAndResponse 2. **Schematron BR-FR-CDV**: French business rules for invoice lifecycle  Returns validation status and detailed error messages if invalid.  **Note:** Use `/validate` to validate structured data fields (JSON).
+     * @summary Validate CDAR XML against XSD and Schematron BR-FR-CDV
+     * @param {File} xmlFile CDAR XML file to validate
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateXmlCdarApiV1CdarValidateXmlPost(xmlFile: File, options?: RawAxiosRequestConfig): AxiosPromise<{
+        [key: string]: any;
+    }>;
+};
+/**
+ * Flux6InvoiceLifecycleCDARApi - object-oriented interface
+ */
+export declare class Flux6InvoiceLifecycleCDARApi extends BaseAPI {
+    /**
+     * Generate a CDAR XML message (Cross Domain Acknowledgement and Response) to communicate the status of an invoice.  **Message types:** - **23** (Processing): Standard lifecycle message - **305** (Transmission): Inter-platform transmission message  **Business rules:** - BR-FR-CDV-14: Status 212 (PAID) requires a paid amount - BR-FR-CDV-15: Statuses 206/207/208/210/213/501 require a reason code
+     * @summary Generate a CDAR message
+     * @param {CreateCDARRequest} createCDARRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    generateCdarApiV1CdarGeneratePost(createCDARRequest: CreateCDARRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<GenerateCDARResponse, any, {}>>;
+    /**
+     * Returns the complete list of action codes (BR-FR-CDV-CL-10).  These codes indicate the requested action on the invoice.
+     * @summary List of CDAR action codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getActionCodesApiV1CdarActionCodesGet(options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<ActionCodesResponse, any, {}>>;
+    /**
+     * Returns the complete list of status reason codes (BR-FR-CDV-CL-09).  These codes explain the reason for a particular status.
+     * @summary List of CDAR reason codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getReasonCodesApiV1CdarReasonCodesGet(options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<ReasonCodesResponse, any, {}>>;
+    /**
+     * Returns the complete list of invoice status codes (BR-FR-CDV-CL-06).  These codes indicate the lifecycle state of an invoice.
+     * @summary List of CDAR status codes
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getStatusCodesApiV1CdarStatusCodesGet(options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<StatusCodesResponse, any, {}>>;
+    /**
+     * Generate a CDAR message and submit it to the PA/PDP platform.  **Authentication strategies:** 1. **JWT with client_uid** (recommended): PDP credentials retrieved from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in the request  **Flow types (flowType):** - `CustomerInvoiceLC`: Client-side lifecycle (buyer) - `SupplierInvoiceLC`: Supplier-side lifecycle (seller)
+     * @summary Generate and submit a CDAR message
+     * @param {SubmitCDARRequest} submitCDARRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitCdarApiV1CdarSubmitPost(submitCDARRequest: SubmitCDARRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SubmitCDARResponse, any, {}>>;
+    /**
+     * Submit a pre-generated CDAR XML message to the PA/PDP platform.  Useful for submitting XML generated by other systems.  **Validation:** The XML is validated against XSD and Schematron BR-FR-CDV rules BEFORE submission. Invalid XML will be rejected with detailed error messages.  **Authentication strategies:** 1. **JWT with client_uid** (recommended): PDP credentials retrieved from backend 2. **Zero-storage**: Provide pdpFlowServiceUrl, pdpClientId, pdpClientSecret in the request
+     * @summary Submit a pre-generated CDAR XML
+     * @param {SubmitCDARXMLRequest} submitCDARXMLRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitCdarXmlApiV1CdarSubmitXmlPost(submitCDARXMLRequest: SubmitCDARXMLRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SubmitCDARResponse, any, {}>>;
+    /**
+     * **Simplified endpoint for OD** - Submit a PAID status (212) for an **ISSUED** invoice.  This status is **mandatory for PPF** (BR-FR-CDV-14 requires the paid amount).  **Use case:** The **seller** confirms payment receipt for an invoice they issued.  **Who issues this status?** - **Issuer (IssuerTradeParty):** The seller (SE = Seller) who received payment - **Recipient (RecipientTradeParty):** The buyer (BY = Buyer) who paid  **Reference:** XP Z12-014 Annex B, example UC1_F202500003_07-CDV-212_Encaissee.xml  **Authentication:** JWT Bearer (recommended) or PDP credentials in request.
+     * @summary [Simplified] Submit PAID status (212) - Issued invoice
+     * @param {EncaisseeRequest} encaisseeRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitEncaisseeApiV1CdarEncaisseePost(encaisseeRequest: EncaisseeRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SimplifiedCDARResponse, any, {}>>;
+    /**
+     * **Simplified endpoint for OD** - Submit a REFUSED status (210) for a **RECEIVED** invoice.  This status is **mandatory for PPF** (BR-FR-CDV-15 requires a reason code).  **Use case:** The **buyer** refuses an invoice they received.  **Who issues this status?** - **Issuer (IssuerTradeParty):** The buyer (BY = Buyer) refusing the invoice - **Recipient (RecipientTradeParty):** The seller (SE = Seller) who issued the invoice  **Reference:** XP Z12-014 Annex B, example UC3_F202500005_04-CDV-210_Refusee.xml  **Allowed reason codes (BR-FR-CDV-CL-09):** - `TX_TVA_ERR`: Incorrect VAT rate - `MONTANTTOTAL_ERR`: Incorrect total amount - `CALCUL_ERR`: Calculation error - `NON_CONFORME`: Non-compliant - `DOUBLON`: Duplicate - `DEST_ERR`: Wrong recipient - `TRANSAC_INC`: Incomplete transaction - `EMMET_INC`: Unknown issuer - `CONTRAT_TERM`: Contract terminated - `DOUBLE_FACT`: Double billing - `CMD_ERR`: Order error - `ADR_ERR`: Address error - `REF_CT_ABSENT`: Missing contract reference  **Authentication:** JWT Bearer (recommended) or PDP credentials in request.
+     * @summary [Simplified] Submit REFUSED status (210) - Received invoice
+     * @param {RefuseeRequest} refuseeRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    submitRefuseeApiV1CdarRefuseePost(refuseeRequest: RefuseeRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SimplifiedCDARResponse, any, {}>>;
+    /**
+     * Validate CDAR structured data without generating XML.  **Note:** This endpoint validates structured data fields only. Use `/validate-xml` to validate a pre-generated CDAR XML file against XSD and Schematron.  Checks: - Field formats (SIREN, dates, etc.) - Enum codes (status, reason, action) - Business rules BR-FR-CDV-*
+     * @summary Validate CDAR structured data
+     * @param {ValidateCDARRequest} validateCDARRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateCdarApiV1CdarValidatePost(validateCDARRequest: ValidateCDARRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<ValidateCDARResponse, any, {}>>;
+    /**
+     * Validates a CDAR XML file against:  1. **XSD schema**: UN/CEFACT D22B CrossDomainAcknowledgementAndResponse 2. **Schematron BR-FR-CDV**: French business rules for invoice lifecycle  Returns validation status and detailed error messages if invalid.  **Note:** Use `/validate` to validate structured data fields (JSON).
+     * @summary Validate CDAR XML against XSD and Schematron BR-FR-CDV
+     * @param {File} xmlFile CDAR XML file to validate
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    validateXmlCdarApiV1CdarValidateXmlPost(xmlFile: File, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<{
+        [key: string]: any;
+    }, any, {}>>;
+}