factpulse 1.0.9__py3-none-any.whl → 3.0.7__py3-none-any.whl

factpulse/models/__init__.py

@@ -2,9 +2,9 @@
 
 # flake8: noqa
 """
-    API REST FactPulse
+    FactPulse REST API
 
-     API REST pour la facturation électronique en France : Factur-X, AFNOR PDP/PA, signatures électroniques.  ## 🎯 Fonctionnalités principales  ### 📄 Génération de factures Factur-X - **Formats** : XML seul ou PDF/A-3 avec XML embarqué - **Profils** : MINIMUM, BASIC, EN16931, EXTENDED - **Normes** : EN 16931 (directive UE 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT) - **🆕 Format simplifié** : Génération à partir de SIRET + auto-enrichissement (API Chorus Pro + Recherche Entreprises)  ### ✅ Validation et conformité - **Validation XML** : Schematron (45 à 210+ règles selon profil) - **Validation PDF** : PDF/A-3, métadonnées XMP Factur-X, signatures électroniques - **VeraPDF** : Validation stricte PDF/A (146+ règles ISO 19005-3) - **Traitement asynchrone** : Support Celery pour validations lourdes (VeraPDF)  ### 📡 Intégration AFNOR PDP/PA (XP Z12-013) - **Soumission de flux** : Envoi de factures vers Plateformes de Dématérialisation Partenaires - **Recherche de flux** : Consultation des factures soumises - **Téléchargement** : Récupération des PDF/A-3 avec XML - **Directory Service** : Recherche d'entreprises (SIREN/SIRET) - **Multi-client** : Support de plusieurs configs PDP par utilisateur (stored credentials ou zero-storage)  ### ✍️ Signature électronique PDF - **Standards** : PAdES-B-B, PAdES-B-T (horodatage RFC 3161), PAdES-B-LT (archivage long terme) - **Niveaux eIDAS** : SES (auto-signé), AdES (CA commerciale), QES (PSCO) - **Validation** : Vérification intégrité cryptographique et certificats - **Génération de certificats** : Certificats X.509 auto-signés pour tests  ### 🔄 Traitement asynchrone - **Celery** : Génération, validation et signature asynchrones - **Polling** : Suivi d'état via `/taches/{id_tache}/statut` - **Pas de timeout** : Idéal pour gros fichiers ou validations lourdes  ## 🔒 Authentification  Toutes les requêtes nécessitent un **token JWT** dans le header Authorization : ``` Authorization: Bearer YOUR_JWT_TOKEN ```  ### Comment obtenir un token JWT ?  #### 🔑 Méthode 1 : API `/api/token/` (Recommandée)  **URL :** `https://www.factpulse.fr/api/token/`  Cette méthode est **recommandée** pour l'intégration dans vos applications et workflows CI/CD.  **Prérequis :** Avoir défini un mot de passe sur votre compte  **Pour les utilisateurs inscrits via email/password :** - Vous avez déjà un mot de passe, utilisez-le directement  **Pour les utilisateurs inscrits via OAuth (Google/GitHub) :** - Vous devez d'abord définir un mot de passe sur : https://www.factpulse.fr/accounts/password/set/ - Une fois le mot de passe créé, vous pourrez utiliser l'API  **Exemple de requête :** ```bash curl -X POST https://www.factpulse.fr/api/token/ \\   -H \"Content-Type: application/json\" \\   -d '{     \"username\": \"votre_email@example.com\",     \"password\": \"votre_mot_de_passe\"   }' ```  **Réponse :** ```json {   \"access\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\",  // Token d'accès (validité: 30 min)   \"refresh\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\"  // Token de rafraîchissement (validité: 7 jours) } ```  **Avantages :** - ✅ Automatisation complète (CI/CD, scripts) - ✅ Gestion programmatique des tokens - ✅ Support du refresh token pour renouveler automatiquement l'accès - ✅ Intégration facile dans n'importe quel langage/outil  #### 🖥️ Méthode 2 : Génération via Dashboard (Alternative)  **URL :** https://www.factpulse.fr/dashboard/  Cette méthode convient pour des tests rapides ou une utilisation occasionnelle via l'interface graphique.  **Fonctionnement :** - Connectez-vous au dashboard - Utilisez les boutons \"Generate Test Token\" ou \"Generate Production Token\" - Fonctionne pour **tous** les utilisateurs (OAuth et email/password), sans nécessiter de mot de passe  **Types de tokens :** - **Token Test** : Validité 24h, quota 1000 appels/jour (gratuit) - **Token Production** : Validité 7 jours, quota selon votre forfait  **Avantages :** - ✅ Rapide pour tester l'API - ✅ Aucun mot de passe requis - ✅ Interface visuelle simple  **Inconvénients :** - ❌ Nécessite une action manuelle - ❌ Pas de refresh token - ❌ Moins adapté pour l'automatisation  ### 📚 Documentation complète  Pour plus d'informations sur l'authentification et l'utilisation de l'API : https://www.factpulse.fr/documentation-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://www.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://www.factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API  **Request example:** ```bash curl -X POST https://www.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://www.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://www.factpulse.fr/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://www.factpulse.fr/documentation-api/     
 
     The version of the OpenAPI document: 1.0.0
     Generated by OpenAPI Generator (https://openapi-generator.tech)
@@ -13,112 +13,146 @@
 """  # noqa: E501
 
 # import models into model package
-from factpulse.models.adresse_electronique import AdresseElectronique
-from factpulse.models.adresse_postale import AdressePostale
-from factpulse.models.body_ajouter_fichier_api_v1_chorus_pro_transverses_ajouter_fichier_post import BodyAjouterFichierApiV1ChorusProTransversesAjouterFichierPost
-from factpulse.models.body_completer_facture_api_v1_chorus_pro_factures_completer_post import BodyCompleterFactureApiV1ChorusProFacturesCompleterPost
-from factpulse.models.body_lister_services_structure_api_v1_chorus_pro_structures_id_structure_cpp_services_get import BodyListerServicesStructureApiV1ChorusProStructuresIdStructureCppServicesGet
-from factpulse.models.body_rechercher_factures_destinataire_api_v1_chorus_pro_factures_rechercher_destinataire_post import BodyRechercherFacturesDestinataireApiV1ChorusProFacturesRechercherDestinatairePost
-from factpulse.models.body_rechercher_factures_fournisseur_api_v1_chorus_pro_factures_rechercher_fournisseur_post import BodyRechercherFacturesFournisseurApiV1ChorusProFacturesRechercherFournisseurPost
-from factpulse.models.body_recycler_facture_api_v1_chorus_pro_factures_recycler_post import BodyRecyclerFactureApiV1ChorusProFacturesRecyclerPost
-from factpulse.models.body_telecharger_groupe_factures_api_v1_chorus_pro_factures_telecharger_groupe_post import BodyTelechargerGroupeFacturesApiV1ChorusProFacturesTelechargerGroupePost
-from factpulse.models.body_traiter_facture_recue_api_v1_chorus_pro_factures_traiter_facture_recue_post import BodyTraiterFactureRecueApiV1ChorusProFacturesTraiterFactureRecuePost
-from factpulse.models.body_valideur_consulter_facture_api_v1_chorus_pro_factures_valideur_consulter_post import BodyValideurConsulterFactureApiV1ChorusProFacturesValideurConsulterPost
-from factpulse.models.body_valideur_rechercher_factures_api_v1_chorus_pro_factures_valideur_rechercher_post import BodyValideurRechercherFacturesApiV1ChorusProFacturesValideurRechercherPost
-from factpulse.models.body_valideur_traiter_facture_api_v1_chorus_pro_factures_valideur_traiter_post import BodyValideurTraiterFactureApiV1ChorusProFacturesValideurTraiterPost
-from factpulse.models.cadre_de_facturation import CadreDeFacturation
-from factpulse.models.categorie_tva import CategorieTVA
+from factpulse.models.afnor_credentials import AFNORCredentials
+from factpulse.models.afnor_destination import AFNORDestination
+from factpulse.models.afnor_health_check_response import AFNORHealthCheckResponse
+from factpulse.models.afnor_result import AFNORResult
+from factpulse.models.api_error import APIError
+from factpulse.models.acknowledgment_status import AcknowledgmentStatus
+from factpulse.models.additional_document import AdditionalDocument
+from factpulse.models.allowance_charge import AllowanceCharge
+from factpulse.models.allowance_reason_code import AllowanceReasonCode
+from factpulse.models.allowance_total_amount import AllowanceTotalAmount
+from factpulse.models.amount import Amount
+from factpulse.models.amount_due import AmountDue
+from factpulse.models.async_task_status import AsyncTaskStatus
+from factpulse.models.base_amount import BaseAmount
+from factpulse.models.bounding_box_schema import BoundingBoxSchema
+from factpulse.models.celery_status import CeleryStatus
 from factpulse.models.certificate_info_response import CertificateInfoResponse
-from factpulse.models.chorus_pro_credentials import ChorusProCredentials
-from factpulse.models.code_cadre_facturation import CodeCadreFacturation
-from factpulse.models.code_raison_reduction import CodeRaisonReduction
-from factpulse.models.consulter_facture_request import ConsulterFactureRequest
-from factpulse.models.consulter_facture_response import ConsulterFactureResponse
-from factpulse.models.consulter_structure_request import ConsulterStructureRequest
-from factpulse.models.consulter_structure_response import ConsulterStructureResponse
-from factpulse.models.credentials_afnor import CredentialsAFNOR
-from factpulse.models.credentials_chorus_pro import CredentialsChorusPro
-from factpulse.models.destinataire import Destinataire
+from factpulse.models.charge_total_amount import ChargeTotalAmount
+from factpulse.models.chorus_pro_destination import ChorusProDestination
+from factpulse.models.chorus_pro_result import ChorusProResult
+from factpulse.models.contact import Contact
+from factpulse.models.convert_error_response import ConvertErrorResponse
+from factpulse.models.convert_pending_input_response import ConvertPendingInputResponse
+from factpulse.models.convert_resume_request import ConvertResumeRequest
+from factpulse.models.convert_success_response import ConvertSuccessResponse
+from factpulse.models.convert_validation_failed_response import ConvertValidationFailedResponse
+from factpulse.models.delivery_party import DeliveryParty
 from factpulse.models.destination import Destination
-from factpulse.models.destination_afnor import DestinationAFNOR
-from factpulse.models.destination_chorus_pro import DestinationChorusPro
-from factpulse.models.direction_flux import DirectionFlux
-from factpulse.models.donnees_facture_simplifiees import DonneesFactureSimplifiees
-from factpulse.models.facture_enrichie_info_input import FactureEnrichieInfoInput
-from factpulse.models.facture_enrichie_info_output import FactureEnrichieInfoOutput
-from factpulse.models.facture_factur_x import FactureFacturX
-from factpulse.models.flux_resume import FluxResume
-from factpulse.models.format_sortie import FormatSortie
-from factpulse.models.fournisseur import Fournisseur
+from factpulse.models.document_type_info import DocumentTypeInfo
+from factpulse.models.electronic_address import ElectronicAddress
+from factpulse.models.enriched_invoice_info import EnrichedInvoiceInfo
+from factpulse.models.error_level import ErrorLevel
+from factpulse.models.error_source import ErrorSource
+from factpulse.models.extraction_info import ExtractionInfo
+from factpulse.models.factur_x_invoice import FacturXInvoice
+from factpulse.models.factur_xpdf_info import FacturXPDFInfo
+from factpulse.models.factur_x_profile import FacturXProfile
+from factpulse.models.facture_electronique_rest_api_schemas_chorus_pro_chorus_pro_credentials import FactureElectroniqueRestApiSchemasChorusProChorusProCredentials
+from factpulse.models.facture_electronique_rest_api_schemas_processing_chorus_pro_credentials import FactureElectroniqueRestApiSchemasProcessingChorusProCredentials
+from factpulse.models.field_status import FieldStatus
+from factpulse.models.file_info import FileInfo
+from factpulse.models.files_info import FilesInfo
+from factpulse.models.flow_direction import FlowDirection
+from factpulse.models.flow_profile import FlowProfile
+from factpulse.models.flow_summary import FlowSummary
+from factpulse.models.flow_syntax import FlowSyntax
+from factpulse.models.flow_type import FlowType
 from factpulse.models.generate_certificate_request import GenerateCertificateRequest
 from factpulse.models.generate_certificate_response import GenerateCertificateResponse
+from factpulse.models.get_chorus_pro_id_request import GetChorusProIdRequest
+from factpulse.models.get_chorus_pro_id_response import GetChorusProIdResponse
+from factpulse.models.get_invoice_request import GetInvoiceRequest
+from factpulse.models.get_invoice_response import GetInvoiceResponse
+from factpulse.models.get_structure_request import GetStructureRequest
+from factpulse.models.get_structure_response import GetStructureResponse
+from factpulse.models.global_allowance_amount import GlobalAllowanceAmount
+from factpulse.models.gross_unit_price import GrossUnitPrice
 from factpulse.models.http_validation_error import HTTPValidationError
-from factpulse.models.information_signature_api import InformationSignatureAPI
-from factpulse.models.ligne_de_poste import LigneDePoste
-from factpulse.models.ligne_de_poste_montant_remise_ht import LigneDePosteMontantRemiseHt
-from factpulse.models.ligne_de_poste_montant_total_ligne_ht import LigneDePosteMontantTotalLigneHt
-from factpulse.models.ligne_de_poste_taux_tva_manuel import LigneDePosteTauxTvaManuel
-from factpulse.models.ligne_de_tva import LigneDeTVA
-from factpulse.models.mode_depot import ModeDepot
-from factpulse.models.mode_paiement import ModePaiement
-from factpulse.models.montant_ht_total import MontantHtTotal
-from factpulse.models.montant_total import MontantTotal
-from factpulse.models.montant_total_acompte import MontantTotalAcompte
-from factpulse.models.montant_total_montant_remise_globale_ttc import MontantTotalMontantRemiseGlobaleTtc
-from factpulse.models.montant_ttc_total import MontantTtcTotal
-from factpulse.models.montant_tva import MontantTva
-from factpulse.models.montantapayer import Montantapayer
-from factpulse.models.montantbaseht import Montantbaseht
-from factpulse.models.montanthttotal import Montanthttotal
-from factpulse.models.montantttctotal import Montantttctotal
-from factpulse.models.montanttva import Montanttva
-from factpulse.models.montanttva1 import Montanttva1
-from factpulse.models.montantunitaireht import Montantunitaireht
-from factpulse.models.obtenir_id_chorus_pro_request import ObtenirIdChorusProRequest
-from factpulse.models.obtenir_id_chorus_pro_response import ObtenirIdChorusProResponse
-from factpulse.models.options_processing import OptionsProcessing
-from factpulse.models.pdf_factur_x_info import PDFFacturXInfo
+from factpulse.models.incoming_invoice import IncomingInvoice
+from factpulse.models.incoming_supplier import IncomingSupplier
+from factpulse.models.invoice_format import InvoiceFormat
+from factpulse.models.invoice_line import InvoiceLine
+from factpulse.models.invoice_line_allowance_amount import InvoiceLineAllowanceAmount
+from factpulse.models.invoice_note import InvoiceNote
+from factpulse.models.invoice_references import InvoiceReferences
+from factpulse.models.invoice_status import InvoiceStatus
+from factpulse.models.invoice_totals import InvoiceTotals
+from factpulse.models.invoice_totals_prepayment import InvoiceTotalsPrepayment
+from factpulse.models.invoice_type_code import InvoiceTypeCode
+from factpulse.models.invoicing_framework import InvoicingFramework
+from factpulse.models.invoicing_framework_code import InvoicingFrameworkCode
+from factpulse.models.line_net_amount import LineNetAmount
+from factpulse.models.line_total_amount import LineTotalAmount
+from factpulse.models.mandatory_note_schema import MandatoryNoteSchema
+from factpulse.models.manual_rate import ManualRate
+from factpulse.models.manual_vat_rate import ManualVatRate
+from factpulse.models.missing_field import MissingField
+from factpulse.models.operation_nature import OperationNature
+from factpulse.models.output_format import OutputFormat
+from factpulse.models.pdf_validation_result_api import PDFValidationResultAPI
 from factpulse.models.pdp_credentials import PDPCredentials
-from factpulse.models.parametres_signature import ParametresSignature
-from factpulse.models.parametres_structure import ParametresStructure
-from factpulse.models.piece_jointe_complementaire import PieceJointeComplementaire
-from factpulse.models.profil_api import ProfilAPI
-from factpulse.models.profil_flux import ProfilFlux
-from factpulse.models.quantite import Quantite
-from factpulse.models.quota_info import QuotaInfo
-from factpulse.models.rechercher_services_response import RechercherServicesResponse
-from factpulse.models.rechercher_structure_request import RechercherStructureRequest
-from factpulse.models.rechercher_structure_response import RechercherStructureResponse
-from factpulse.models.references import References
-from factpulse.models.reponse_healthcheck_afnor import ReponseHealthcheckAFNOR
-from factpulse.models.reponse_recherche_flux import ReponseRechercheFlux
-from factpulse.models.reponse_soumission_flux import ReponseSoumissionFlux
-from factpulse.models.reponse_tache import ReponseTache
-from factpulse.models.reponse_validation_erreur import ReponseValidationErreur
-from factpulse.models.reponse_validation_succes import ReponseValidationSucces
-from factpulse.models.requete_recherche_flux import RequeteRechercheFlux
-from factpulse.models.requete_soumission_flux import RequeteSoumissionFlux
-from factpulse.models.resultat_afnor import ResultatAFNOR
-from factpulse.models.resultat_chorus_pro import ResultatChorusPro
-from factpulse.models.resultat_validation_pdfapi import ResultatValidationPDFAPI
+from factpulse.models.page_dimensions_schema import PageDimensionsSchema
+from factpulse.models.payee import Payee
+from factpulse.models.payment_card import PaymentCard
+from factpulse.models.payment_means import PaymentMeans
+from factpulse.models.percentage import Percentage
+from factpulse.models.postal_address import PostalAddress
+from factpulse.models.price_allowance_amount import PriceAllowanceAmount
+from factpulse.models.price_basis_quantity import PriceBasisQuantity
+from factpulse.models.processing_options import ProcessingOptions
+from factpulse.models.product_characteristic import ProductCharacteristic
+from factpulse.models.product_classification import ProductClassification
+from factpulse.models.quantity import Quantity
+from factpulse.models.recipient import Recipient
+from factpulse.models.rounding_amount import RoundingAmount
 from factpulse.models.scheme_id import SchemeID
-from factpulse.models.service_structure import ServiceStructure
+from factpulse.models.search_flow_request import SearchFlowRequest
+from factpulse.models.search_flow_response import SearchFlowResponse
+from factpulse.models.search_services_response import SearchServicesResponse
+from factpulse.models.search_structure_request import SearchStructureRequest
+from factpulse.models.search_structure_response import SearchStructureResponse
 from factpulse.models.signature_info import SignatureInfo
-from factpulse.models.soumettre_facture_complete_request import SoumettreFactureCompleteRequest
-from factpulse.models.soumettre_facture_complete_response import SoumettreFactureCompleteResponse
-from factpulse.models.soumettre_facture_request import SoumettreFactureRequest
-from factpulse.models.soumettre_facture_response import SoumettreFactureResponse
-from factpulse.models.statut_acquittement import StatutAcquittement
-from factpulse.models.statut_facture import StatutFacture
-from factpulse.models.statut_tache import StatutTache
+from factpulse.models.signature_info_api import SignatureInfoAPI
+from factpulse.models.signature_parameters import SignatureParameters
+from factpulse.models.simplified_invoice_data import SimplifiedInvoiceData
 from factpulse.models.structure_info import StructureInfo
-from factpulse.models.syntaxe_flux import SyntaxeFlux
-from factpulse.models.tauxmanuel import Tauxmanuel
-from factpulse.models.type_facture import TypeFacture
-from factpulse.models.type_flux import TypeFlux
-from factpulse.models.type_tva import TypeTVA
-from factpulse.models.unite import Unite
-from factpulse.models.utilisateur import Utilisateur
+from factpulse.models.structure_parameters import StructureParameters
+from factpulse.models.structure_service import StructureService
+from factpulse.models.submission_mode import SubmissionMode
+from factpulse.models.submit_complete_invoice_request import SubmitCompleteInvoiceRequest
+from factpulse.models.submit_complete_invoice_response import SubmitCompleteInvoiceResponse
+from factpulse.models.submit_flow_request import SubmitFlowRequest
+from factpulse.models.submit_flow_response import SubmitFlowResponse
+from factpulse.models.submit_gross_amount import SubmitGrossAmount
+from factpulse.models.submit_invoice_request import SubmitInvoiceRequest
+from factpulse.models.submit_invoice_response import SubmitInvoiceResponse
+from factpulse.models.submit_net_amount import SubmitNetAmount
+from factpulse.models.submit_vat_amount import SubmitVatAmount
+from factpulse.models.supplementary_attachment import SupplementaryAttachment
+from factpulse.models.supplier import Supplier
+from factpulse.models.task_response import TaskResponse
+from factpulse.models.tax_representative import TaxRepresentative
+from factpulse.models.taxable_amount import TaxableAmount
+from factpulse.models.total_gross_amount import TotalGrossAmount
+from factpulse.models.total_net_amount import TotalNetAmount
+from factpulse.models.total_vat_amount import TotalVATAmount
+from factpulse.models.unit_net_price import UnitNetPrice
+from factpulse.models.unit_of_measure import UnitOfMeasure
+from factpulse.models.vat_accounting_code import VATAccountingCode
+from factpulse.models.vat_amount import VATAmount
+from factpulse.models.vat_category import VATCategory
+from factpulse.models.vat_line import VATLine
+from factpulse.models.vat_point_date_code import VATPointDateCode
 from factpulse.models.validation_error import ValidationError
+from factpulse.models.validation_error_detail import ValidationErrorDetail
 from factpulse.models.validation_error_loc_inner import ValidationErrorLocInner
+from factpulse.models.validation_error_response import ValidationErrorResponse
+from factpulse.models.validation_info import ValidationInfo
+from factpulse.models.validation_success_response import ValidationSuccessResponse
+from factpulse.models.vat_rate import VatRate
+from factpulse.models.verification_success_response import VerificationSuccessResponse
+from factpulse.models.verified_field_schema import VerifiedFieldSchema
 

factpulse/models/acknowledgment_status.py

@@ -0,0 +1,38 @@
+# coding: utf-8
+
+"""
+    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://www.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://www.factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API  **Request example:** ```bash curl -X POST https://www.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://www.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://www.factpulse.fr/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://www.factpulse.fr/documentation-api/     
+
+    The version of the OpenAPI document: 1.0.0
+    Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+    Do not edit the class manually.
+"""  # noqa: E501
+
+
+from __future__ import annotations
+import json
+from enum import Enum
+from typing_extensions import Self
+
+
+class AcknowledgmentStatus(str, Enum):
+    """
+    Flow acknowledgment status.
+    """
+
+    """
+    allowed enum values
+    """
+    PENDING = 'Pending'
+    OK = 'Ok'
+    ERROR = 'Error'
+
+    @classmethod
+    def from_json(cls, json_str: str) -> Self:
+        """Create an instance of AcknowledgmentStatus from a JSON string"""
+        return cls(json.loads(json_str))
+
+

factpulse/models/additional_document.py

@@ -0,0 +1,115 @@
+# coding: utf-8
+
+"""
+    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://www.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://www.factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API  **Request example:** ```bash curl -X POST https://www.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://www.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://www.factpulse.fr/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://www.factpulse.fr/documentation-api/     
+
+    The version of the OpenAPI document: 1.0.0
+    Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+    Do not edit the class manually.
+"""  # noqa: E501
+
+
+from __future__ import annotations
+import pprint
+import re  # noqa: F401
+import json
+
+from pydantic import BaseModel, ConfigDict, Field, StrictStr
+from typing import Any, ClassVar, Dict, List, Optional
+from typing import Optional, Set
+from typing_extensions import Self
+
+class AdditionalDocument(BaseModel):
+    """
+    Additional supporting document (BG-24).  References to external documents or embedded attachments.
+    """ # noqa: E501
+    id: StrictStr = Field(description="Document reference identifier (BT-122).")
+    type_code: Optional[StrictStr] = None
+    name: Optional[StrictStr] = None
+    uri: Optional[StrictStr] = None
+    reference_type_code: Optional[StrictStr] = None
+    __properties: ClassVar[List[str]] = ["id", "type_code", "name", "uri", "reference_type_code"]
+
+    model_config = ConfigDict(
+        populate_by_name=True,
+        validate_assignment=True,
+        protected_namespaces=(),
+    )
+
+
+    def to_str(self) -> str:
+        """Returns the string representation of the model using alias"""
+        return pprint.pformat(self.model_dump(by_alias=True))
+
+    def to_json(self) -> str:
+        """Returns the JSON representation of the model using alias"""
+        # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
+        return json.dumps(self.to_dict())
+
+    @classmethod
+    def from_json(cls, json_str: str) -> Optional[Self]:
+        """Create an instance of AdditionalDocument from a JSON string"""
+        return cls.from_dict(json.loads(json_str))
+
+    def to_dict(self) -> Dict[str, Any]:
+        """Return the dictionary representation of the model using alias.
+
+        This has the following differences from calling pydantic's
+        `self.model_dump(by_alias=True)`:
+
+        * `None` is only added to the output dict for nullable fields that
+          were set at model initialization. Other fields with value `None`
+          are ignored.
+        """
+        excluded_fields: Set[str] = set([
+        ])
+
+        _dict = self.model_dump(
+            by_alias=True,
+            exclude=excluded_fields,
+            exclude_none=True,
+        )
+        # set to None if type_code (nullable) is None
+        # and model_fields_set contains the field
+        if self.type_code is None and "type_code" in self.model_fields_set:
+            _dict['type_code'] = None
+
+        # set to None if name (nullable) is None
+        # and model_fields_set contains the field
+        if self.name is None and "name" in self.model_fields_set:
+            _dict['name'] = None
+
+        # set to None if uri (nullable) is None
+        # and model_fields_set contains the field
+        if self.uri is None and "uri" in self.model_fields_set:
+            _dict['uri'] = None
+
+        # set to None if reference_type_code (nullable) is None
+        # and model_fields_set contains the field
+        if self.reference_type_code is None and "reference_type_code" in self.model_fields_set:
+            _dict['reference_type_code'] = None
+
+        return _dict
+
+    @classmethod
+    def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
+        """Create an instance of AdditionalDocument from a dict"""
+        if obj is None:
+            return None
+
+        if not isinstance(obj, dict):
+            return cls.model_validate(obj)
+
+        _obj = cls.model_validate({
+            "id": obj.get("id"),
+            "type_code": obj.get("type_code"),
+            "name": obj.get("name"),
+            "uri": obj.get("uri"),
+            "reference_type_code": obj.get("reference_type_code")
+        })
+        return _obj
+
+

factpulse/models/afnor_credentials.py

@@ -0,0 +1,106 @@
+# coding: utf-8
+
+"""
+    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://www.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://www.factpulse.fr/accounts/password/set/ - Once the password is created, you can use the API  **Request example:** ```bash curl -X POST https://www.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://www.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://www.factpulse.fr/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://www.factpulse.fr/documentation-api/     
+
+    The version of the OpenAPI document: 1.0.0
+    Generated by OpenAPI Generator (https://openapi-generator.tech)
+
+    Do not edit the class manually.
+"""  # noqa: E501
+
+
+from __future__ import annotations
+import pprint
+import re  # noqa: F401
+import json
+
+from pydantic import BaseModel, ConfigDict, Field, StrictStr
+from typing import Any, ClassVar, Dict, List, Optional
+from typing import Optional, Set
+from typing_extensions import Self
+
+class AFNORCredentials(BaseModel):
+    """
+    Optional AFNOR PDP credentials.  **MODE 1 - JWT retrieval (recommended):** Do not provide this `credentials` field in the payload. PDP credentials will be automatically retrieved via client_uid from JWT (0-trust).  **MODE 2 - Credentials in payload (zero-storage):** Provide all required fields below. Useful for tests or third-party integrations.
+    """ # noqa: E501
+    client_id: Optional[StrictStr] = Field(default=None, alias="clientId")
+    client_secret: Optional[StrictStr] = Field(default=None, alias="clientSecret")
+    flow_service_url: Optional[StrictStr] = Field(default=None, alias="flowServiceUrl")
+    __properties: ClassVar[List[str]] = ["clientId", "clientSecret", "flowServiceUrl"]
+
+    model_config = ConfigDict(
+        populate_by_name=True,
+        validate_assignment=True,
+        protected_namespaces=(),
+    )
+
+
+    def to_str(self) -> str:
+        """Returns the string representation of the model using alias"""
+        return pprint.pformat(self.model_dump(by_alias=True))
+
+    def to_json(self) -> str:
+        """Returns the JSON representation of the model using alias"""
+        # TODO: pydantic v2: use .model_dump_json(by_alias=True, exclude_unset=True) instead
+        return json.dumps(self.to_dict())
+
+    @classmethod
+    def from_json(cls, json_str: str) -> Optional[Self]:
+        """Create an instance of AFNORCredentials from a JSON string"""
+        return cls.from_dict(json.loads(json_str))
+
+    def to_dict(self) -> Dict[str, Any]:
+        """Return the dictionary representation of the model using alias.
+
+        This has the following differences from calling pydantic's
+        `self.model_dump(by_alias=True)`:
+
+        * `None` is only added to the output dict for nullable fields that
+          were set at model initialization. Other fields with value `None`
+          are ignored.
+        """
+        excluded_fields: Set[str] = set([
+        ])
+
+        _dict = self.model_dump(
+            by_alias=True,
+            exclude=excluded_fields,
+            exclude_none=True,
+        )
+        # set to None if client_id (nullable) is None
+        # and model_fields_set contains the field
+        if self.client_id is None and "client_id" in self.model_fields_set:
+            _dict['clientId'] = None
+
+        # set to None if client_secret (nullable) is None
+        # and model_fields_set contains the field
+        if self.client_secret is None and "client_secret" in self.model_fields_set:
+            _dict['clientSecret'] = None
+
+        # set to None if flow_service_url (nullable) is None
+        # and model_fields_set contains the field
+        if self.flow_service_url is None and "flow_service_url" in self.model_fields_set:
+            _dict['flowServiceUrl'] = None
+
+        return _dict
+
+    @classmethod
+    def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]:
+        """Create an instance of AFNORCredentials from a dict"""
+        if obj is None:
+            return None
+
+        if not isinstance(obj, dict):
+            return cls.model_validate(obj)
+
+        _obj = cls.model_validate({
+            "clientId": obj.get("clientId"),
+            "clientSecret": obj.get("clientSecret"),
+            "flowServiceUrl": obj.get("flowServiceUrl")
+        })
+        return _obj
+
+