factpulse 4.0.3 → 4.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (415) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +4 -4
  3. data/Gemfile.lock +2 -2
  4. data/docs/AFNORErrorDetail.md +26 -0
  5. data/docs/AsyncTasksApi.md +225 -0
  6. data/docs/ClientManagementApi.md +20 -20
  7. data/docs/ConversionErrorResult.md +30 -0
  8. data/docs/ConversionExtractionInfo.md +20 -0
  9. data/docs/ConversionPendingInputResult.md +30 -0
  10. data/docs/ConversionSuccessTaskResult.md +36 -0
  11. data/docs/ConversionTaskStatus.md +22 -0
  12. data/docs/ConversionTaskStatusResult.md +85 -0
  13. data/docs/ConversionValidationFailedResult.md +34 -0
  14. data/docs/DownloadsApi.md +4 -4
  15. data/docs/FacturXConversionApi.md +75 -0
  16. data/docs/FacturXInvoice.md +1 -1
  17. data/docs/FacturXPDFXMLVerificationApi.md +75 -0
  18. data/docs/FacturXValidationApi.md +0 -81
  19. data/docs/FactureElectroniqueModelsInvoiceTypeCode.md +15 -0
  20. data/docs/Flux6InvoiceLifecycleCDARApi.md +82 -0
  21. data/docs/GenerationSuccessResult.md +24 -0
  22. data/docs/GenerationTaskStatus.md +22 -0
  23. data/docs/GenerationTaskStatusResult.md +79 -0
  24. data/docs/HealthApi.md +0 -124
  25. data/docs/{FacturXGenerationApi.md → InvoiceGenerationApi.md} +21 -21
  26. data/docs/InvoiceInput.md +1 -1
  27. data/docs/InvoiceLifecycle.md +24 -0
  28. data/docs/InvoicingFramework.md +1 -1
  29. data/docs/LifecycleEvent.md +38 -0
  30. data/docs/LifecycleResponse.md +22 -0
  31. data/docs/ParseApi.md +161 -0
  32. data/docs/ParseFacturXResponse.md +26 -0
  33. data/docs/ReferencesApi.md +74 -0
  34. data/docs/SignatureSuccessResult.md +34 -0
  35. data/docs/SignatureTaskStatus.md +22 -0
  36. data/docs/SignatureTaskStatusResult.md +79 -0
  37. data/docs/SimplifiedInvoiceData.md +1 -1
  38. data/docs/SubmitCompleteInvoiceResponse.md +3 -1
  39. data/docs/Supplier.md +1 -1
  40. data/docs/TaskErrorResult.md +26 -0
  41. data/docs/VATEXCodeInfo.md +24 -0
  42. data/docs/VATEXCodesResponse.md +22 -0
  43. data/docs/ValidationApi.md +88 -0
  44. data/docs/ValidationSuccessTaskResult.md +20 -0
  45. data/docs/ValidationTaskStatus.md +22 -0
  46. data/docs/ValidationTaskStatusResult.md +79 -0
  47. data/docs/VerificationSuccessTaskResult.md +20 -0
  48. data/docs/VerificationTypedTaskStatus.md +22 -0
  49. data/docs/VerificationTypedTaskStatusResult.md +79 -0
  50. data/factpulse.gemspec +3 -3
  51. data/lib/factpulse/api/afnorpdppa_api.rb +2 -2
  52. data/lib/factpulse/api/afnorpdppa_directory_service_api.rb +2 -2
  53. data/lib/factpulse/api/afnorpdppa_flow_service_api.rb +2 -2
  54. data/lib/factpulse/api/async_tasks_api.rb +191 -2
  55. data/lib/factpulse/api/chorus_pro_api.rb +2 -2
  56. data/lib/factpulse/api/client_management_api.rb +22 -22
  57. data/lib/factpulse/api/downloads_api.rb +6 -6
  58. data/lib/factpulse/api/electronic_signature_api.rb +2 -2
  59. data/lib/factpulse/api/factur_x_conversion_api.rb +65 -2
  60. data/lib/factpulse/api/factur_x_validation_api.rb +2 -77
  61. data/lib/factpulse/api/factur_xpdfxml_verification_api.rb +65 -2
  62. data/lib/factpulse/api/flux10_e_reporting_api.rb +2 -2
  63. data/lib/factpulse/api/flux6_invoice_lifecycle_cdar_api.rb +85 -2
  64. data/lib/factpulse/api/health_api.rb +2 -116
  65. data/lib/factpulse/api/{factur_x_generation_api.rb → invoice_generation_api.rb} +23 -23
  66. data/lib/factpulse/api/parse_api.rb +163 -0
  67. data/lib/factpulse/api/references_api.rb +82 -0
  68. data/lib/factpulse/api/validation_api.rb +97 -0
  69. data/lib/factpulse/api_client.rb +2 -2
  70. data/lib/factpulse/api_error.rb +2 -2
  71. data/lib/factpulse/api_model_base.rb +2 -2
  72. data/lib/factpulse/configuration.rb +2 -2
  73. data/lib/factpulse/models/acknowledgment_status.rb +2 -2
  74. data/lib/factpulse/models/action_code_info.rb +2 -2
  75. data/lib/factpulse/models/action_codes_response.rb +2 -2
  76. data/lib/factpulse/models/additional_document.rb +2 -2
  77. data/lib/factpulse/models/afnor_acknowledgement.rb +2 -2
  78. data/lib/factpulse/models/afnor_acknowledgement_detail.rb +2 -2
  79. data/lib/factpulse/models/afnor_address_edit.rb +2 -2
  80. data/lib/factpulse/models/afnor_address_patch.rb +2 -2
  81. data/lib/factpulse/models/afnor_address_put.rb +2 -2
  82. data/lib/factpulse/models/afnor_address_read.rb +2 -2
  83. data/lib/factpulse/models/afnor_algorithm.rb +2 -2
  84. data/lib/factpulse/models/afnor_contains_operator.rb +2 -2
  85. data/lib/factpulse/models/afnor_create_directory_line_body.rb +2 -2
  86. data/lib/factpulse/models/afnor_create_directory_line_body_addressing_information.rb +2 -2
  87. data/lib/factpulse/models/afnor_create_directory_line_body_period.rb +2 -2
  88. data/lib/factpulse/models/afnor_create_routing_code_body.rb +2 -2
  89. data/lib/factpulse/models/afnor_credentials.rb +2 -2
  90. data/lib/factpulse/models/afnor_destination.rb +2 -2
  91. data/lib/factpulse/models/afnor_diffusion_status.rb +2 -2
  92. data/lib/factpulse/models/afnor_directory_line_field.rb +2 -2
  93. data/lib/factpulse/models/afnor_directory_line_payload_history_legal_unit_facility_routing_code.rb +2 -2
  94. data/lib/factpulse/models/afnor_directory_line_payload_history_legal_unit_facility_routing_code_platform.rb +2 -2
  95. data/lib/factpulse/models/afnor_directory_line_payload_history_legal_unit_facility_routing_code_routing_code.rb +2 -2
  96. data/lib/factpulse/models/afnor_directory_line_post201_response.rb +2 -2
  97. data/lib/factpulse/models/afnor_directory_line_search_post200_response.rb +2 -2
  98. data/lib/factpulse/models/afnor_entity_type.rb +2 -2
  99. data/lib/factpulse/models/afnor_error.rb +2 -2
  100. data/lib/factpulse/models/afnor_error_detail.rb +237 -0
  101. data/lib/factpulse/models/afnor_facility_administrative_status.rb +2 -2
  102. data/lib/factpulse/models/afnor_facility_nature.rb +2 -2
  103. data/lib/factpulse/models/afnor_facility_payload_history.rb +2 -2
  104. data/lib/factpulse/models/afnor_facility_payload_history_ule_b2g_additional_data.rb +2 -2
  105. data/lib/factpulse/models/afnor_facility_payload_included.rb +2 -2
  106. data/lib/factpulse/models/afnor_facility_type.rb +2 -2
  107. data/lib/factpulse/models/afnor_flow.rb +2 -2
  108. data/lib/factpulse/models/afnor_flow_ack_status.rb +2 -2
  109. data/lib/factpulse/models/afnor_flow_direction.rb +2 -2
  110. data/lib/factpulse/models/afnor_flow_info.rb +2 -2
  111. data/lib/factpulse/models/afnor_flow_profile.rb +2 -2
  112. data/lib/factpulse/models/afnor_flow_syntax.rb +2 -2
  113. data/lib/factpulse/models/afnor_flow_type.rb +2 -2
  114. data/lib/factpulse/models/afnor_full_flow_info.rb +2 -2
  115. data/lib/factpulse/models/afnor_health_check_response.rb +2 -2
  116. data/lib/factpulse/models/afnor_legal_unit_administrative_status.rb +2 -2
  117. data/lib/factpulse/models/afnor_legal_unit_payload_history.rb +2 -2
  118. data/lib/factpulse/models/afnor_legal_unit_payload_included.rb +2 -2
  119. data/lib/factpulse/models/afnor_legal_unit_payload_included_no_siren.rb +2 -2
  120. data/lib/factpulse/models/afnor_platform_status.rb +2 -2
  121. data/lib/factpulse/models/afnor_processing_rule.rb +2 -2
  122. data/lib/factpulse/models/afnor_reason_code.rb +2 -2
  123. data/lib/factpulse/models/afnor_reason_code_enum.rb +2 -2
  124. data/lib/factpulse/models/afnor_recipient_platform_type.rb +2 -2
  125. data/lib/factpulse/models/afnor_result.rb +2 -2
  126. data/lib/factpulse/models/afnor_routing_code_administrative_status.rb +2 -2
  127. data/lib/factpulse/models/afnor_routing_code_field.rb +2 -2
  128. data/lib/factpulse/models/afnor_routing_code_payload_history_legal_unit_facility.rb +2 -2
  129. data/lib/factpulse/models/afnor_routing_code_post201_response.rb +2 -2
  130. data/lib/factpulse/models/afnor_routing_code_search.rb +2 -2
  131. data/lib/factpulse/models/afnor_routing_code_search_filters.rb +2 -2
  132. data/lib/factpulse/models/afnor_routing_code_search_filters_administrative_status.rb +2 -2
  133. data/lib/factpulse/models/afnor_routing_code_search_filters_routing_code_name.rb +2 -2
  134. data/lib/factpulse/models/afnor_routing_code_search_filters_routing_identifier.rb +2 -2
  135. data/lib/factpulse/models/afnor_routing_code_search_post200_response.rb +2 -2
  136. data/lib/factpulse/models/afnor_routing_code_search_sorting_inner.rb +2 -2
  137. data/lib/factpulse/models/afnor_search_directory_line.rb +2 -2
  138. data/lib/factpulse/models/afnor_search_directory_line_filters.rb +2 -2
  139. data/lib/factpulse/models/afnor_search_directory_line_filters_addressing_identifier.rb +2 -2
  140. data/lib/factpulse/models/afnor_search_directory_line_filters_addressing_suffix.rb +2 -2
  141. data/lib/factpulse/models/afnor_search_directory_line_sorting_inner.rb +2 -2
  142. data/lib/factpulse/models/afnor_search_flow_content.rb +2 -2
  143. data/lib/factpulse/models/afnor_search_flow_filters.rb +2 -2
  144. data/lib/factpulse/models/afnor_search_flow_params.rb +2 -2
  145. data/lib/factpulse/models/afnor_search_siren.rb +2 -2
  146. data/lib/factpulse/models/afnor_search_siren_filters.rb +2 -2
  147. data/lib/factpulse/models/afnor_search_siren_filters_administrative_status.rb +2 -2
  148. data/lib/factpulse/models/afnor_search_siren_filters_business_name.rb +2 -2
  149. data/lib/factpulse/models/afnor_search_siren_filters_entity_type.rb +2 -2
  150. data/lib/factpulse/models/afnor_search_siren_filters_siren.rb +2 -2
  151. data/lib/factpulse/models/afnor_search_siren_sorting_inner.rb +2 -2
  152. data/lib/factpulse/models/afnor_search_siret.rb +2 -2
  153. data/lib/factpulse/models/afnor_search_siret_filters.rb +2 -2
  154. data/lib/factpulse/models/afnor_search_siret_filters_address_lines.rb +2 -2
  155. data/lib/factpulse/models/afnor_search_siret_filters_administrative_status.rb +2 -2
  156. data/lib/factpulse/models/afnor_search_siret_filters_country_subdivision.rb +2 -2
  157. data/lib/factpulse/models/afnor_search_siret_filters_facility_type.rb +2 -2
  158. data/lib/factpulse/models/afnor_search_siret_filters_locality.rb +2 -2
  159. data/lib/factpulse/models/afnor_search_siret_filters_name.rb +2 -2
  160. data/lib/factpulse/models/afnor_search_siret_filters_postal_code.rb +2 -2
  161. data/lib/factpulse/models/afnor_search_siret_filters_siret.rb +2 -2
  162. data/lib/factpulse/models/afnor_search_siret_sorting_inner.rb +2 -2
  163. data/lib/factpulse/models/afnor_siren_field.rb +2 -2
  164. data/lib/factpulse/models/afnor_siren_search_post200_response.rb +2 -2
  165. data/lib/factpulse/models/afnor_siret_field.rb +2 -2
  166. data/lib/factpulse/models/afnor_siret_search_post200_response.rb +2 -2
  167. data/lib/factpulse/models/afnor_sorting_order.rb +2 -2
  168. data/lib/factpulse/models/afnor_strict_operator.rb +2 -2
  169. data/lib/factpulse/models/afnor_update_patch_directory_line_body.rb +2 -2
  170. data/lib/factpulse/models/afnor_update_patch_routing_code_body.rb +2 -2
  171. data/lib/factpulse/models/afnor_update_put_routing_code_body.rb +2 -2
  172. data/lib/factpulse/models/afnor_webhook_callback_content.rb +2 -2
  173. data/lib/factpulse/models/aggregated_payment_input.rb +2 -2
  174. data/lib/factpulse/models/aggregated_transaction_input.rb +2 -2
  175. data/lib/factpulse/models/allowance_charge.rb +2 -2
  176. data/lib/factpulse/models/allowance_charge_reason_code.rb +2 -2
  177. data/lib/factpulse/models/allowance_reason_code.rb +2 -2
  178. data/lib/factpulse/models/allowance_total_amount.rb +2 -2
  179. data/lib/factpulse/models/amount.rb +2 -2
  180. data/lib/factpulse/models/amount1.rb +2 -2
  181. data/lib/factpulse/models/amount2.rb +2 -2
  182. data/lib/factpulse/models/amount_due.rb +2 -2
  183. data/lib/factpulse/models/api_error.rb +2 -2
  184. data/lib/factpulse/models/api_profile.rb +2 -2
  185. data/lib/factpulse/models/async_task_status.rb +2 -2
  186. data/lib/factpulse/models/base_amount.rb +2 -2
  187. data/lib/factpulse/models/bounding_box_schema.rb +2 -2
  188. data/lib/factpulse/models/buyercountry.rb +2 -2
  189. data/lib/factpulse/models/celery_status.rb +2 -2
  190. data/lib/factpulse/models/certificate_info_response.rb +2 -2
  191. data/lib/factpulse/models/charge_total_amount.rb +2 -2
  192. data/lib/factpulse/models/chorus_pro_credentials.rb +2 -2
  193. data/lib/factpulse/models/chorus_pro_destination.rb +2 -2
  194. data/lib/factpulse/models/chorus_pro_result.rb +2 -2
  195. data/lib/factpulse/models/client_activate_response.rb +2 -2
  196. data/lib/factpulse/models/client_create_request.rb +2 -2
  197. data/lib/factpulse/models/client_detail.rb +2 -2
  198. data/lib/factpulse/models/client_list_response.rb +2 -2
  199. data/lib/factpulse/models/client_summary.rb +2 -2
  200. data/lib/factpulse/models/client_update_request.rb +2 -2
  201. data/lib/factpulse/models/contact.rb +2 -2
  202. data/lib/factpulse/models/conversion_error_result.rb +277 -0
  203. data/lib/factpulse/models/conversion_extraction_info.rb +176 -0
  204. data/lib/factpulse/models/conversion_pending_input_result.rb +344 -0
  205. data/lib/factpulse/models/conversion_success_task_result.rb +355 -0
  206. data/lib/factpulse/models/conversion_task_status.rb +223 -0
  207. data/lib/factpulse/models/conversion_task_status_result.rb +59 -0
  208. data/lib/factpulse/models/conversion_validation_failed_result.rb +348 -0
  209. data/lib/factpulse/models/convert_resume_request.rb +2 -2
  210. data/lib/factpulse/models/convert_success_response.rb +2 -2
  211. data/lib/factpulse/models/convert_validation_failed_response.rb +2 -2
  212. data/lib/factpulse/models/country_code.rb +2 -2
  213. data/lib/factpulse/models/create_aggregated_report_request.rb +2 -2
  214. data/lib/factpulse/models/create_cdar_request.rb +2 -2
  215. data/lib/factpulse/models/create_e_reporting_request.rb +2 -2
  216. data/lib/factpulse/models/currency.rb +2 -2
  217. data/lib/factpulse/models/currency_code.rb +2 -2
  218. data/lib/factpulse/models/delivery_party.rb +2 -2
  219. data/lib/factpulse/models/destination.rb +2 -2
  220. data/lib/factpulse/models/doc_type.rb +2 -2
  221. data/lib/factpulse/models/document_type_info.rb +2 -2
  222. data/lib/factpulse/models/e_reporting_flow_type.rb +2 -2
  223. data/lib/factpulse/models/e_reporting_validation_error.rb +2 -2
  224. data/lib/factpulse/models/electronic_address.rb +2 -2
  225. data/lib/factpulse/models/encaisseamount.rb +2 -2
  226. data/lib/factpulse/models/encaisseamount1.rb +2 -2
  227. data/lib/factpulse/models/encaissee_request.rb +2 -2
  228. data/lib/factpulse/models/enriched_invoice_info.rb +2 -2
  229. data/lib/factpulse/models/error_level.rb +2 -2
  230. data/lib/factpulse/models/error_source.rb +2 -2
  231. data/lib/factpulse/models/extraction_info.rb +2 -2
  232. data/lib/factpulse/models/factur_x_invoice.rb +3 -19
  233. data/lib/factpulse/models/factur_xpdf_info.rb +2 -2
  234. data/lib/factpulse/models/facture_electronique_models_invoice_type_code.rb +54 -0
  235. data/lib/factpulse/models/facture_electronique_rest_api_schemas_chorus_pro_chorus_pro_credentials.rb +2 -2
  236. data/lib/factpulse/models/facture_electronique_rest_api_schemas_validation_validation_error_response.rb +2 -2
  237. data/lib/factpulse/models/field_status.rb +2 -2
  238. data/lib/factpulse/models/file_info.rb +2 -2
  239. data/lib/factpulse/models/files_info.rb +2 -2
  240. data/lib/factpulse/models/flow_direction.rb +2 -2
  241. data/lib/factpulse/models/flow_profile.rb +2 -2
  242. data/lib/factpulse/models/flow_summary.rb +2 -2
  243. data/lib/factpulse/models/flow_syntax.rb +2 -2
  244. data/lib/factpulse/models/flow_type.rb +2 -2
  245. data/lib/factpulse/models/generate_aggregated_report_response.rb +2 -2
  246. data/lib/factpulse/models/generate_cdar_response.rb +2 -2
  247. data/lib/factpulse/models/generate_certificate_request.rb +2 -2
  248. data/lib/factpulse/models/generate_certificate_response.rb +2 -2
  249. data/lib/factpulse/models/generate_e_reporting_response.rb +2 -2
  250. data/lib/factpulse/models/generation_success_result.rb +230 -0
  251. data/lib/factpulse/models/generation_task_status.rb +223 -0
  252. data/lib/factpulse/models/generation_task_status_result.rb +55 -0
  253. data/lib/factpulse/models/get_chorus_pro_id_request.rb +2 -2
  254. data/lib/factpulse/models/get_chorus_pro_id_response.rb +2 -2
  255. data/lib/factpulse/models/get_invoice_request.rb +2 -2
  256. data/lib/factpulse/models/get_invoice_response.rb +2 -2
  257. data/lib/factpulse/models/get_structure_request.rb +2 -2
  258. data/lib/factpulse/models/get_structure_response.rb +2 -2
  259. data/lib/factpulse/models/global_allowance_amount.rb +2 -2
  260. data/lib/factpulse/models/gross_unit_price.rb +2 -2
  261. data/lib/factpulse/models/http_validation_error.rb +2 -2
  262. data/lib/factpulse/models/incoming_invoice.rb +2 -2
  263. data/lib/factpulse/models/incoming_supplier.rb +2 -2
  264. data/lib/factpulse/models/invoice_format.rb +2 -2
  265. data/lib/factpulse/models/invoice_input.rb +3 -3
  266. data/lib/factpulse/models/invoice_lifecycle.rb +215 -0
  267. data/lib/factpulse/models/invoice_line.rb +2 -2
  268. data/lib/factpulse/models/invoice_line_allowance_amount.rb +2 -2
  269. data/lib/factpulse/models/invoice_note.rb +2 -2
  270. data/lib/factpulse/models/invoice_payment_input.rb +2 -2
  271. data/lib/factpulse/models/invoice_references.rb +2 -2
  272. data/lib/factpulse/models/invoice_status.rb +2 -2
  273. data/lib/factpulse/models/invoice_totals.rb +2 -2
  274. data/lib/factpulse/models/invoice_totals_prepayment.rb +2 -2
  275. data/lib/factpulse/models/invoice_type_code.rb +8 -19
  276. data/lib/factpulse/models/invoice_type_code_output.rb +2 -2
  277. data/lib/factpulse/models/invoicing_framework.rb +3 -20
  278. data/lib/factpulse/models/invoicing_framework_code.rb +2 -2
  279. data/lib/factpulse/models/issuer_role_code.rb +2 -2
  280. data/lib/factpulse/models/key_rotation_request.rb +2 -2
  281. data/lib/factpulse/models/key_rotation_response.rb +2 -2
  282. data/lib/factpulse/models/lifecycle_event.rb +300 -0
  283. data/lib/factpulse/models/lifecycle_response.rb +205 -0
  284. data/lib/factpulse/models/line_net_amount.rb +2 -2
  285. data/lib/factpulse/models/line_sub_type.rb +2 -2
  286. data/lib/factpulse/models/line_total_amount.rb +2 -2
  287. data/lib/factpulse/models/location_inner.rb +2 -2
  288. data/lib/factpulse/models/mandatory_note_schema.rb +2 -2
  289. data/lib/factpulse/models/manual_rate.rb +2 -2
  290. data/lib/factpulse/models/manual_vat_rate.rb +2 -2
  291. data/lib/factpulse/models/missing_field.rb +2 -2
  292. data/lib/factpulse/models/operation_nature.rb +2 -2
  293. data/lib/factpulse/models/output_format.rb +5 -3
  294. data/lib/factpulse/models/page_dimensions_schema.rb +2 -2
  295. data/lib/factpulse/models/parse_factur_x_response.rb +249 -0
  296. data/lib/factpulse/models/payee.rb +2 -2
  297. data/lib/factpulse/models/payment_amount_by_rate.rb +2 -2
  298. data/lib/factpulse/models/payment_card.rb +2 -2
  299. data/lib/factpulse/models/payment_means.rb +2 -2
  300. data/lib/factpulse/models/pdf_validation_result_api.rb +2 -2
  301. data/lib/factpulse/models/pdp_config_response.rb +2 -2
  302. data/lib/factpulse/models/pdp_config_update_request.rb +2 -2
  303. data/lib/factpulse/models/pdp_credentials.rb +2 -2
  304. data/lib/factpulse/models/percentage.rb +2 -2
  305. data/lib/factpulse/models/postal_address.rb +2 -2
  306. data/lib/factpulse/models/price_allowance_amount.rb +2 -2
  307. data/lib/factpulse/models/price_basis_quantity.rb +2 -2
  308. data/lib/factpulse/models/processing_options.rb +2 -2
  309. data/lib/factpulse/models/processing_rule.rb +2 -2
  310. data/lib/factpulse/models/product_characteristic.rb +2 -2
  311. data/lib/factpulse/models/product_classification.rb +2 -2
  312. data/lib/factpulse/models/quantity.rb +2 -2
  313. data/lib/factpulse/models/rate.rb +2 -2
  314. data/lib/factpulse/models/rate1.rb +2 -2
  315. data/lib/factpulse/models/reason_code_info.rb +2 -2
  316. data/lib/factpulse/models/reason_codes_response.rb +2 -2
  317. data/lib/factpulse/models/recipient.rb +2 -2
  318. data/lib/factpulse/models/recipient_input.rb +2 -2
  319. data/lib/factpulse/models/refusee_request.rb +2 -2
  320. data/lib/factpulse/models/report_issuer.rb +2 -2
  321. data/lib/factpulse/models/report_period.rb +2 -2
  322. data/lib/factpulse/models/report_sender.rb +2 -2
  323. data/lib/factpulse/models/rounding_amount.rb +2 -2
  324. data/lib/factpulse/models/schematron_validation_error.rb +2 -2
  325. data/lib/factpulse/models/scheme_id.rb +2 -2
  326. data/lib/factpulse/models/search_flow_request.rb +2 -2
  327. data/lib/factpulse/models/search_flow_response.rb +2 -2
  328. data/lib/factpulse/models/search_services_response.rb +2 -2
  329. data/lib/factpulse/models/search_structure_request.rb +2 -2
  330. data/lib/factpulse/models/search_structure_response.rb +2 -2
  331. data/lib/factpulse/models/secret_status.rb +2 -2
  332. data/lib/factpulse/models/sellercountry.rb +2 -2
  333. data/lib/factpulse/models/signature_info.rb +2 -2
  334. data/lib/factpulse/models/signature_info_api.rb +2 -2
  335. data/lib/factpulse/models/signature_parameters.rb +2 -2
  336. data/lib/factpulse/models/signature_success_result.rb +394 -0
  337. data/lib/factpulse/models/signature_task_status.rb +223 -0
  338. data/lib/factpulse/models/signature_task_status_result.rb +55 -0
  339. data/lib/factpulse/models/simplified_cdar_response.rb +2 -2
  340. data/lib/factpulse/models/simplified_invoice_data.rb +3 -3
  341. data/lib/factpulse/models/status_code_info.rb +2 -2
  342. data/lib/factpulse/models/status_codes_response.rb +2 -2
  343. data/lib/factpulse/models/structure_info.rb +2 -2
  344. data/lib/factpulse/models/structure_parameters.rb +2 -2
  345. data/lib/factpulse/models/structure_service.rb +2 -2
  346. data/lib/factpulse/models/submission_mode.rb +2 -2
  347. data/lib/factpulse/models/submit_aggregated_report_request.rb +2 -2
  348. data/lib/factpulse/models/submit_cdar_request.rb +2 -2
  349. data/lib/factpulse/models/submit_cdar_response.rb +2 -2
  350. data/lib/factpulse/models/submit_cdarxml_request.rb +2 -2
  351. data/lib/factpulse/models/submit_complete_invoice_request.rb +2 -2
  352. data/lib/factpulse/models/submit_complete_invoice_response.rb +33 -4
  353. data/lib/factpulse/models/submit_e_reporting_request.rb +2 -2
  354. data/lib/factpulse/models/submit_e_reporting_response.rb +2 -2
  355. data/lib/factpulse/models/submit_flow_request.rb +2 -2
  356. data/lib/factpulse/models/submit_flow_response.rb +2 -2
  357. data/lib/factpulse/models/submit_gross_amount.rb +2 -2
  358. data/lib/factpulse/models/submit_invoice_request.rb +2 -2
  359. data/lib/factpulse/models/submit_invoice_response.rb +2 -2
  360. data/lib/factpulse/models/submit_net_amount.rb +2 -2
  361. data/lib/factpulse/models/submit_vat_amount.rb +2 -2
  362. data/lib/factpulse/models/supplementary_attachment.rb +2 -2
  363. data/lib/factpulse/models/supplier.rb +4 -18
  364. data/lib/factpulse/models/task_error_result.rb +257 -0
  365. data/lib/factpulse/models/task_response.rb +2 -2
  366. data/lib/factpulse/models/tax_breakdown_input.rb +2 -2
  367. data/lib/factpulse/models/tax_due_date_type.rb +2 -2
  368. data/lib/factpulse/models/tax_representative.rb +2 -2
  369. data/lib/factpulse/models/taxable_amount.rb +2 -2
  370. data/lib/factpulse/models/taxableamount.rb +2 -2
  371. data/lib/factpulse/models/taxamount.rb +2 -2
  372. data/lib/factpulse/models/taxamount1.rb +2 -2
  373. data/lib/factpulse/models/taxamount2.rb +2 -2
  374. data/lib/factpulse/models/taxexclusiveamount.rb +2 -2
  375. data/lib/factpulse/models/taxexclusiveamount1.rb +2 -2
  376. data/lib/factpulse/models/total_gross_amount.rb +2 -2
  377. data/lib/factpulse/models/total_net_amount.rb +2 -2
  378. data/lib/factpulse/models/total_vat_amount.rb +2 -2
  379. data/lib/factpulse/models/transaction_category.rb +2 -2
  380. data/lib/factpulse/models/transmission_type_code.rb +2 -2
  381. data/lib/factpulse/models/unit_net_price.rb +2 -2
  382. data/lib/factpulse/models/unit_of_measure.rb +17 -3
  383. data/lib/factpulse/models/validate_cdar_request.rb +2 -2
  384. data/lib/factpulse/models/validate_cdar_response.rb +2 -2
  385. data/lib/factpulse/models/validate_e_reporting_request.rb +2 -2
  386. data/lib/factpulse/models/validate_e_reporting_response.rb +2 -2
  387. data/lib/factpulse/models/validation_error.rb +2 -2
  388. data/lib/factpulse/models/validation_error_detail.rb +2 -2
  389. data/lib/factpulse/models/validation_error_response.rb +2 -2
  390. data/lib/factpulse/models/validation_info.rb +2 -2
  391. data/lib/factpulse/models/validation_success_response.rb +2 -2
  392. data/lib/factpulse/models/validation_success_task_result.rb +210 -0
  393. data/lib/factpulse/models/validation_task_status.rb +223 -0
  394. data/lib/factpulse/models/validation_task_status_result.rb +55 -0
  395. data/lib/factpulse/models/vat_accounting_code.rb +2 -2
  396. data/lib/factpulse/models/vat_amount.rb +2 -2
  397. data/lib/factpulse/models/vat_category.rb +2 -2
  398. data/lib/factpulse/models/vat_line.rb +2 -2
  399. data/lib/factpulse/models/vat_point_date_code.rb +2 -2
  400. data/lib/factpulse/models/vat_rate.rb +2 -2
  401. data/lib/factpulse/models/vatex_code_info.rb +247 -0
  402. data/lib/factpulse/models/vatex_codes_response.rb +204 -0
  403. data/lib/factpulse/models/verification_success_response.rb +2 -2
  404. data/lib/factpulse/models/verification_success_task_result.rb +210 -0
  405. data/lib/factpulse/models/verification_typed_task_status.rb +223 -0
  406. data/lib/factpulse/models/verification_typed_task_status_result.rb +55 -0
  407. data/lib/factpulse/models/verified_field_schema.rb +2 -2
  408. data/lib/factpulse/models/webhook_secret_delete_response.rb +2 -2
  409. data/lib/factpulse/models/webhook_secret_generate_response.rb +2 -2
  410. data/lib/factpulse/models/webhook_secret_status_response.rb +2 -2
  411. data/lib/factpulse/version.rb +3 -3
  412. data/lib/factpulse.rb +34 -4
  413. metadata +121 -61
  414. data/docs/FactureElectroniqueRestApiSchemasEreportingInvoiceTypeCode.md +0 -15
  415. data/lib/factpulse/models/facture_electronique_rest_api_schemas_ereporting_invoice_type_code.rb +0 -43
@@ -1,15 +1,15 @@
1
1
  =begin
2
2
  #FactPulse REST API
3
3
 
4
- # 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/
4
+ # REST API for electronic invoicing in France: Factur-X (CII), UBL 2.1, AFNOR PDP/PA, electronic signatures. ## 🎯 Main Features ### 📄 Invoice Generation - **Formats**: CII XML, UBL 2.1 XML, or Factur-X PDF/A-3 - **Profiles** (CII/PDF): MINIMUM, BASIC, EN16931, EXTENDED - **UBL**: Always EN16931 compliant - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT), UBL 2.1 (OASIS) - **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/
5
5
 
6
6
  The version of the OpenAPI document: 1.0.0
7
7
  Contact: contact@factpulse.fr
8
8
  Generated by: https://openapi-generator.tech
9
- Generator version: 7.20.0-SNAPSHOT
9
+ Generator version: 7.21.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
13
13
  module FactPulse
14
- VERSION = '4.0.3'
14
+ VERSION = '4.1.2'
15
15
  end
data/lib/factpulse.rb CHANGED
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #FactPulse REST API
3
3
 
4
- # 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/
4
+ # REST API for electronic invoicing in France: Factur-X (CII), UBL 2.1, AFNOR PDP/PA, electronic signatures. ## 🎯 Main Features ### 📄 Invoice Generation - **Formats**: CII XML, UBL 2.1 XML, or Factur-X PDF/A-3 - **Profiles** (CII/PDF): MINIMUM, BASIC, EN16931, EXTENDED - **UBL**: Always EN16931 compliant - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT), UBL 2.1 (OASIS) - **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/
5
5
 
6
6
  The version of the OpenAPI document: 1.0.0
7
7
  Contact: contact@factpulse.fr
8
8
  Generated by: https://openapi-generator.tech
9
- Generator version: 7.20.0-SNAPSHOT
9
+ Generator version: 7.21.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -41,6 +41,7 @@ require 'factpulse/models/afnor_directory_line_post201_response'
41
41
  require 'factpulse/models/afnor_directory_line_search_post200_response'
42
42
  require 'factpulse/models/afnor_entity_type'
43
43
  require 'factpulse/models/afnor_error'
44
+ require 'factpulse/models/afnor_error_detail'
44
45
  require 'factpulse/models/afnor_facility_administrative_status'
45
46
  require 'factpulse/models/afnor_facility_nature'
46
47
  require 'factpulse/models/afnor_facility_payload_history'
@@ -146,6 +147,13 @@ require 'factpulse/models/client_list_response'
146
147
  require 'factpulse/models/client_summary'
147
148
  require 'factpulse/models/client_update_request'
148
149
  require 'factpulse/models/contact'
150
+ require 'factpulse/models/conversion_error_result'
151
+ require 'factpulse/models/conversion_extraction_info'
152
+ require 'factpulse/models/conversion_pending_input_result'
153
+ require 'factpulse/models/conversion_success_task_result'
154
+ require 'factpulse/models/conversion_task_status'
155
+ require 'factpulse/models/conversion_task_status_result'
156
+ require 'factpulse/models/conversion_validation_failed_result'
149
157
  require 'factpulse/models/convert_resume_request'
150
158
  require 'factpulse/models/convert_success_response'
151
159
  require 'factpulse/models/convert_validation_failed_response'
@@ -171,8 +179,8 @@ require 'factpulse/models/error_source'
171
179
  require 'factpulse/models/extraction_info'
172
180
  require 'factpulse/models/factur_x_invoice'
173
181
  require 'factpulse/models/factur_xpdf_info'
182
+ require 'factpulse/models/facture_electronique_models_invoice_type_code'
174
183
  require 'factpulse/models/facture_electronique_rest_api_schemas_chorus_pro_chorus_pro_credentials'
175
- require 'factpulse/models/facture_electronique_rest_api_schemas_ereporting_invoice_type_code'
176
184
  require 'factpulse/models/facture_electronique_rest_api_schemas_validation_validation_error_response'
177
185
  require 'factpulse/models/field_status'
178
186
  require 'factpulse/models/file_info'
@@ -187,6 +195,9 @@ require 'factpulse/models/generate_cdar_response'
187
195
  require 'factpulse/models/generate_certificate_request'
188
196
  require 'factpulse/models/generate_certificate_response'
189
197
  require 'factpulse/models/generate_e_reporting_response'
198
+ require 'factpulse/models/generation_success_result'
199
+ require 'factpulse/models/generation_task_status'
200
+ require 'factpulse/models/generation_task_status_result'
190
201
  require 'factpulse/models/get_chorus_pro_id_request'
191
202
  require 'factpulse/models/get_chorus_pro_id_response'
192
203
  require 'factpulse/models/get_invoice_request'
@@ -200,6 +211,7 @@ require 'factpulse/models/incoming_invoice'
200
211
  require 'factpulse/models/incoming_supplier'
201
212
  require 'factpulse/models/invoice_format'
202
213
  require 'factpulse/models/invoice_input'
214
+ require 'factpulse/models/invoice_lifecycle'
203
215
  require 'factpulse/models/invoice_line'
204
216
  require 'factpulse/models/invoice_line_allowance_amount'
205
217
  require 'factpulse/models/invoice_note'
@@ -215,6 +227,8 @@ require 'factpulse/models/invoicing_framework_code'
215
227
  require 'factpulse/models/issuer_role_code'
216
228
  require 'factpulse/models/key_rotation_request'
217
229
  require 'factpulse/models/key_rotation_response'
230
+ require 'factpulse/models/lifecycle_event'
231
+ require 'factpulse/models/lifecycle_response'
218
232
  require 'factpulse/models/line_net_amount'
219
233
  require 'factpulse/models/line_sub_type'
220
234
  require 'factpulse/models/line_total_amount'
@@ -230,6 +244,7 @@ require 'factpulse/models/pdp_config_response'
230
244
  require 'factpulse/models/pdp_config_update_request'
231
245
  require 'factpulse/models/pdp_credentials'
232
246
  require 'factpulse/models/page_dimensions_schema'
247
+ require 'factpulse/models/parse_factur_x_response'
233
248
  require 'factpulse/models/payee'
234
249
  require 'factpulse/models/payment_amount_by_rate'
235
250
  require 'factpulse/models/payment_card'
@@ -266,6 +281,9 @@ require 'factpulse/models/sellercountry'
266
281
  require 'factpulse/models/signature_info'
267
282
  require 'factpulse/models/signature_info_api'
268
283
  require 'factpulse/models/signature_parameters'
284
+ require 'factpulse/models/signature_success_result'
285
+ require 'factpulse/models/signature_task_status'
286
+ require 'factpulse/models/signature_task_status_result'
269
287
  require 'factpulse/models/simplified_cdar_response'
270
288
  require 'factpulse/models/simplified_invoice_data'
271
289
  require 'factpulse/models/status_code_info'
@@ -291,6 +309,7 @@ require 'factpulse/models/submit_net_amount'
291
309
  require 'factpulse/models/submit_vat_amount'
292
310
  require 'factpulse/models/supplementary_attachment'
293
311
  require 'factpulse/models/supplier'
312
+ require 'factpulse/models/task_error_result'
294
313
  require 'factpulse/models/task_response'
295
314
  require 'factpulse/models/tax_breakdown_input'
296
315
  require 'factpulse/models/tax_due_date_type'
@@ -312,6 +331,8 @@ require 'factpulse/models/unit_of_measure'
312
331
  require 'factpulse/models/vat_accounting_code'
313
332
  require 'factpulse/models/vat_amount'
314
333
  require 'factpulse/models/vat_category'
334
+ require 'factpulse/models/vatex_code_info'
335
+ require 'factpulse/models/vatex_codes_response'
315
336
  require 'factpulse/models/vat_line'
316
337
  require 'factpulse/models/vat_point_date_code'
317
338
  require 'factpulse/models/validate_cdar_request'
@@ -323,8 +344,14 @@ require 'factpulse/models/validation_error_detail'
323
344
  require 'factpulse/models/validation_error_response'
324
345
  require 'factpulse/models/validation_info'
325
346
  require 'factpulse/models/validation_success_response'
347
+ require 'factpulse/models/validation_success_task_result'
348
+ require 'factpulse/models/validation_task_status'
349
+ require 'factpulse/models/validation_task_status_result'
326
350
  require 'factpulse/models/vat_rate'
327
351
  require 'factpulse/models/verification_success_response'
352
+ require 'factpulse/models/verification_success_task_result'
353
+ require 'factpulse/models/verification_typed_task_status'
354
+ require 'factpulse/models/verification_typed_task_status_result'
328
355
  require 'factpulse/models/verified_field_schema'
329
356
  require 'factpulse/models/webhook_secret_delete_response'
330
357
  require 'factpulse/models/webhook_secret_generate_response'
@@ -340,12 +367,15 @@ require 'factpulse/api/client_management_api'
340
367
  require 'factpulse/api/downloads_api'
341
368
  require 'factpulse/api/electronic_signature_api'
342
369
  require 'factpulse/api/factur_x_conversion_api'
343
- require 'factpulse/api/factur_x_generation_api'
344
370
  require 'factpulse/api/factur_xpdfxml_verification_api'
345
371
  require 'factpulse/api/factur_x_validation_api'
346
372
  require 'factpulse/api/flux10_e_reporting_api'
347
373
  require 'factpulse/api/flux6_invoice_lifecycle_cdar_api'
348
374
  require 'factpulse/api/health_api'
375
+ require 'factpulse/api/invoice_generation_api'
376
+ require 'factpulse/api/parse_api'
377
+ require 'factpulse/api/references_api'
378
+ require 'factpulse/api/validation_api'
349
379
 
350
380
  module FactPulse
351
381
  class << self
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: factpulse
3
3
  version: !ruby/object:Gem::Version
4
- version: 4.0.3
4
+ version: 4.1.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - OpenAPI-Generator
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2026-02-06 00:00:00.000000000 Z
11
+ date: 2026-02-24 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: typhoeus
@@ -50,61 +50,61 @@ dependencies:
50
50
  - - ">="
51
51
  - !ruby/object:Gem::Version
52
52
  version: 3.6.0
53
- description: " REST API for electronic invoicing in France: Factur-X, AFNOR PDP/PA,
54
- electronic signatures. ## \U0001F3AF Main Features ### \U0001F4C4 Factur-X - Generation
55
- - **Formats**: XML only or PDF/A-3 with embedded XML - **Profiles**: MINIMUM, BASIC,
56
- EN16931, EXTENDED - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3
57
- (PDF/A-3), CII (UN/CEFACT) - **\U0001F195 Simplified Format**: Generation from SIRET
58
- + auto-enrichment (Chorus Pro API + Business Search) ### Factur-X - Validation
59
- - **XML Validation**: Schematron (45 to 210+ rules depending on profile) - **PDF
60
- Validation**: PDF/A-3, Factur-X XMP metadata - **VeraPDF**: Strict PDF/A validation
61
- (146+ ISO 19005-3 rules) ### ✍️ Electronic Signature - **Standards**: PAdES-B-B,
62
- PAdES-B-T (RFC 3161 timestamping), PAdES-B-LT (long-term archival) - **eIDAS Levels**:
63
- SES (self-signed), AdES (commercial CA), QES (QTSP) - **Validation**: Cryptographic
64
- integrity and certificate verification ### \U0001F4CB Flux 6 - Invoice Lifecycle
65
- (CDAR) - **CDAR Messages**: Acknowledgements, invoice statuses - **PPF Statuses**:
66
- REFUSED (210), PAID (212) ### \U0001F4CA Flux 10 - E-Reporting - **Tax Declarations**:
67
- International B2B, B2C - **Flow Types**: 10.1 (B2B transactions), 10.2 (B2B payments),
68
- 10.3 (B2C transactions), 10.4 (B2C payments) ### \U0001F4E1 AFNOR PDP/PA (XP Z12-013)
69
- - **Flow Service**: Submit and search flows to PDPs - **Directory Service**: Company
70
- search (SIREN/SIRET) - **Multi-client**: Support for multiple PDP configs per user
71
- \ ### \U0001F3DB️ Chorus Pro - **Public Sector Invoicing**: Complete API for Chorus
72
- Pro ### ⏳ Async Tasks - **Celery**: Asynchronous generation, validation and signing
73
- - **Polling**: Status tracking via `/tasks/{task_id}/status` - **Webhooks**: Automatic
74
- notifications when tasks complete ## \U0001F512 Authentication All requests require
75
- a **JWT token** in the Authorization header: ``` Authorization: Bearer YOUR_JWT_TOKEN
76
- ``` ### How to obtain a JWT token? #### \U0001F511 Method 1: `/api/token/` API
77
- (Recommended) **URL:** `https://factpulse.fr/api/token/` This method is **recommended**
78
- for integration in your applications and CI/CD workflows. **Prerequisites:** Having
79
- set a password on your account **For users registered via email/password:** - You
80
- already have a password, use it directly **For users registered via OAuth (Google/GitHub):**
81
- - You must first set a password at: https://factpulse.fr/accounts/password/set/
82
- - Once the password is created, you can use the API **Request example:** ```bash
83
- curl -X POST https://factpulse.fr/api/token/ \\ -H \"Content-Type: application/json\"
84
- \\ -d '{ \"username\": \"your_email@example.com\", \"password\": \"your_password\"
85
- \ }' ``` **Optional `client_uid` parameter:** To select credentials for a specific
86
- client (PA/PDP, Chorus Pro, signing certificates), add `client_uid`: ```bash curl
87
- -X POST https://factpulse.fr/api/token/ \\ -H \"Content-Type: application/json\"
88
- \\ -d '{ \"username\": \"your_email@example.com\", \"password\": \"your_password\",
89
- \ \"client_uid\": \"550e8400-e29b-41d4-a716-446655440000\" }' ``` The `client_uid`
90
- will be included in the JWT and allow the API to automatically use: - AFNOR/PDP
91
- credentials configured for this client - Chorus Pro credentials configured for this
92
- client - Electronic signature certificates configured for this client **Response:**
93
- ```json { \"access\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\", // Access token (validity:
94
- 30 min) \"refresh\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\" // Refresh token (validity:
95
- 7 days) } ``` **Advantages:** - ✅ Full automation (CI/CD, scripts) - ✅ Programmatic
96
- token management - ✅ Refresh token support for automatic access renewal - ✅ Easy
97
- integration in any language/tool #### \U0001F5A5️ Method 2: Dashboard Generation
98
- (Alternative) **URL:** https://factpulse.fr/api/dashboard/ This method is suitable
99
- for quick tests or occasional use via the graphical interface. **How it works:**
100
- - Log in to the dashboard - Use the \"Generate Test Token\" or \"Generate Production
101
- Token\" buttons - Works for **all** users (OAuth and email/password), without requiring
102
- a password **Token types:** - **Test Token**: 24h validity, 1000 calls/day quota
103
- (free) - **Production Token**: 7 days validity, quota based on your plan **Advantages:**
104
- - ✅ Quick for API testing - ✅ No password required - ✅ Simple visual interface **Disadvantages:**
105
- - ❌ Requires manual action - ❌ No refresh token - ❌ Less suited for automation ###
106
- \U0001F4DA Full Documentation For more information on authentication and API usage:
107
- https://factpulse.fr/documentation-api/ "
53
+ description: " REST API for electronic invoicing in France: Factur-X (CII), UBL 2.1,
54
+ AFNOR PDP/PA, electronic signatures. ## \U0001F3AF Main Features ### \U0001F4C4
55
+ Invoice Generation - **Formats**: CII XML, UBL 2.1 XML, or Factur-X PDF/A-3 - **Profiles**
56
+ (CII/PDF): MINIMUM, BASIC, EN16931, EXTENDED - **UBL**: Always EN16931 compliant
57
+ - **Standards**: EN 16931 (EU directive 2014/55), ISO 19005-3 (PDF/A-3), CII (UN/CEFACT),
58
+ UBL 2.1 (OASIS) - **Simplified Format**: Generation from SIRET + auto-enrichment
59
+ (Chorus Pro API + Business Search) ### Factur-X - Validation - **XML Validation**:
60
+ Schematron (45 to 210+ rules depending on profile) - **PDF Validation**: PDF/A-3,
61
+ Factur-X XMP metadata - **VeraPDF**: Strict PDF/A validation (146+ ISO 19005-3 rules)
62
+ \ ### ✍️ Electronic Signature - **Standards**: PAdES-B-B, PAdES-B-T (RFC 3161 timestamping),
63
+ PAdES-B-LT (long-term archival) - **eIDAS Levels**: SES (self-signed), AdES (commercial
64
+ CA), QES (QTSP) - **Validation**: Cryptographic integrity and certificate verification
65
+ \ ### \U0001F4CB Flux 6 - Invoice Lifecycle (CDAR) - **CDAR Messages**: Acknowledgements,
66
+ invoice statuses - **PPF Statuses**: REFUSED (210), PAID (212) ### \U0001F4CA Flux
67
+ 10 - E-Reporting - **Tax Declarations**: International B2B, B2C - **Flow Types**:
68
+ 10.1 (B2B transactions), 10.2 (B2B payments), 10.3 (B2C transactions), 10.4 (B2C
69
+ payments) ### \U0001F4E1 AFNOR PDP/PA (XP Z12-013) - **Flow Service**: Submit and
70
+ search flows to PDPs - **Directory Service**: Company search (SIREN/SIRET) - **Multi-client**:
71
+ Support for multiple PDP configs per user ### \U0001F3DB️ Chorus Pro - **Public
72
+ Sector Invoicing**: Complete API for Chorus Pro ### ⏳ Async Tasks - **Celery**:
73
+ Asynchronous generation, validation and signing - **Polling**: Status tracking via
74
+ `/tasks/{task_id}/status` - **Webhooks**: Automatic notifications when tasks complete
75
+ \ ## \U0001F512 Authentication All requests require a **JWT token** in the Authorization
76
+ header: ``` Authorization: Bearer YOUR_JWT_TOKEN ``` ### How to obtain a JWT token?
77
+ \ #### \U0001F511 Method 1: `/api/token/` API (Recommended) **URL:** `https://factpulse.fr/api/token/`
78
+ \ This method is **recommended** for integration in your applications and CI/CD
79
+ workflows. **Prerequisites:** Having set a password on your account **For users
80
+ registered via email/password:** - You already have a password, use it directly
81
+ \ **For users registered via OAuth (Google/GitHub):** - You must first set a password
82
+ at: https://factpulse.fr/accounts/password/set/ - Once the password is created,
83
+ you can use the API **Request example:** ```bash curl -X POST https://factpulse.fr/api/token/
84
+ \\ -H \"Content-Type: application/json\" \\ -d '{ \"username\": \"your_email@example.com\",
85
+ \ \"password\": \"your_password\" }' ``` **Optional `client_uid` parameter:**
86
+ \ To select credentials for a specific client (PA/PDP, Chorus Pro, signing certificates),
87
+ add `client_uid`: ```bash curl -X POST https://factpulse.fr/api/token/ \\ -H
88
+ \"Content-Type: application/json\" \\ -d '{ \"username\": \"your_email@example.com\",
89
+ \ \"password\": \"your_password\", \"client_uid\": \"550e8400-e29b-41d4-a716-446655440000\"
90
+ \ }' ``` The `client_uid` will be included in the JWT and allow the API to automatically
91
+ use: - AFNOR/PDP credentials configured for this client - Chorus Pro credentials
92
+ configured for this client - Electronic signature certificates configured for this
93
+ client **Response:** ```json { \"access\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\", //
94
+ Access token (validity: 30 min) \"refresh\": \"eyJ0eXAiOiJKV1QiLCJhbGc...\" //
95
+ Refresh token (validity: 7 days) } ``` **Advantages:** - ✅ Full automation (CI/CD,
96
+ scripts) - ✅ Programmatic token management - ✅ Refresh token support for automatic
97
+ access renewal - ✅ Easy integration in any language/tool #### \U0001F5A5️ Method
98
+ 2: Dashboard Generation (Alternative) **URL:** https://factpulse.fr/api/dashboard/
99
+ \ This method is suitable for quick tests or occasional use via the graphical interface.
100
+ \ **How it works:** - Log in to the dashboard - Use the \"Generate Test Token\"
101
+ or \"Generate Production Token\" buttons - Works for **all** users (OAuth and email/password),
102
+ without requiring a password **Token types:** - **Test Token**: 24h validity, 1000
103
+ calls/day quota (free) - **Production Token**: 7 days validity, quota based on your
104
+ plan **Advantages:** - ✅ Quick for API testing - ✅ No password required - ✅ Simple
105
+ visual interface **Disadvantages:** - ❌ Requires manual action - ❌ No refresh token
106
+ - ❌ Less suited for automation ### \U0001F4DA Full Documentation For more information
107
+ on authentication and API usage: https://factpulse.fr/documentation-api/ "
108
108
  email:
109
109
  - contact@factpulse.fr
110
110
  executables: []
@@ -140,6 +140,7 @@ files:
140
140
  - docs/AFNORDirectoryLineSearchPost200Response.md
141
141
  - docs/AFNOREntityType.md
142
142
  - docs/AFNORError.md
143
+ - docs/AFNORErrorDetail.md
143
144
  - docs/AFNORFacilityAdministrativeStatus.md
144
145
  - docs/AFNORFacilityNature.md
145
146
  - docs/AFNORFacilityPayloadHistory.md
@@ -251,6 +252,13 @@ files:
251
252
  - docs/ClientSummary.md
252
253
  - docs/ClientUpdateRequest.md
253
254
  - docs/Contact.md
255
+ - docs/ConversionErrorResult.md
256
+ - docs/ConversionExtractionInfo.md
257
+ - docs/ConversionPendingInputResult.md
258
+ - docs/ConversionSuccessTaskResult.md
259
+ - docs/ConversionTaskStatus.md
260
+ - docs/ConversionTaskStatusResult.md
261
+ - docs/ConversionValidationFailedResult.md
254
262
  - docs/ConvertResumeRequest.md
255
263
  - docs/ConvertSuccessResponse.md
256
264
  - docs/ConvertValidationFailedResponse.md
@@ -277,13 +285,12 @@ files:
277
285
  - docs/ErrorSource.md
278
286
  - docs/ExtractionInfo.md
279
287
  - docs/FacturXConversionApi.md
280
- - docs/FacturXGenerationApi.md
281
288
  - docs/FacturXInvoice.md
282
289
  - docs/FacturXPDFInfo.md
283
290
  - docs/FacturXPDFXMLVerificationApi.md
284
291
  - docs/FacturXValidationApi.md
292
+ - docs/FactureElectroniqueModelsInvoiceTypeCode.md
285
293
  - docs/FactureElectroniqueRestApiSchemasChorusProChorusProCredentials.md
286
- - docs/FactureElectroniqueRestApiSchemasEreportingInvoiceTypeCode.md
287
294
  - docs/FactureElectroniqueRestApiSchemasValidationValidationErrorResponse.md
288
295
  - docs/FieldStatus.md
289
296
  - docs/FileInfo.md
@@ -300,6 +307,9 @@ files:
300
307
  - docs/GenerateCertificateRequest.md
301
308
  - docs/GenerateCertificateResponse.md
302
309
  - docs/GenerateEReportingResponse.md
310
+ - docs/GenerationSuccessResult.md
311
+ - docs/GenerationTaskStatus.md
312
+ - docs/GenerationTaskStatusResult.md
303
313
  - docs/GetChorusProIdRequest.md
304
314
  - docs/GetChorusProIdResponse.md
305
315
  - docs/GetInvoiceRequest.md
@@ -313,7 +323,9 @@ files:
313
323
  - docs/IncomingInvoice.md
314
324
  - docs/IncomingSupplier.md
315
325
  - docs/InvoiceFormat.md
326
+ - docs/InvoiceGenerationApi.md
316
327
  - docs/InvoiceInput.md
328
+ - docs/InvoiceLifecycle.md
317
329
  - docs/InvoiceLine.md
318
330
  - docs/InvoiceLineAllowanceAmount.md
319
331
  - docs/InvoiceNote.md
@@ -329,6 +341,8 @@ files:
329
341
  - docs/IssuerRoleCode.md
330
342
  - docs/KeyRotationRequest.md
331
343
  - docs/KeyRotationResponse.md
344
+ - docs/LifecycleEvent.md
345
+ - docs/LifecycleResponse.md
332
346
  - docs/LineNetAmount.md
333
347
  - docs/LineSubType.md
334
348
  - docs/LineTotalAmount.md
@@ -344,6 +358,8 @@ files:
344
358
  - docs/PDPConfigUpdateRequest.md
345
359
  - docs/PDPCredentials.md
346
360
  - docs/PageDimensionsSchema.md
361
+ - docs/ParseApi.md
362
+ - docs/ParseFacturXResponse.md
347
363
  - docs/Payee.md
348
364
  - docs/PaymentAmountByRate.md
349
365
  - docs/PaymentCard.md
@@ -363,6 +379,7 @@ files:
363
379
  - docs/ReasonCodesResponse.md
364
380
  - docs/Recipient.md
365
381
  - docs/RecipientInput.md
382
+ - docs/ReferencesApi.md
366
383
  - docs/RefuseeRequest.md
367
384
  - docs/ReportIssuer.md
368
385
  - docs/ReportPeriod.md
@@ -380,6 +397,9 @@ files:
380
397
  - docs/SignatureInfo.md
381
398
  - docs/SignatureInfoAPI.md
382
399
  - docs/SignatureParameters.md
400
+ - docs/SignatureSuccessResult.md
401
+ - docs/SignatureTaskStatus.md
402
+ - docs/SignatureTaskStatusResult.md
383
403
  - docs/SimplifiedCDARResponse.md
384
404
  - docs/SimplifiedInvoiceData.md
385
405
  - docs/StatusCodeInfo.md
@@ -405,6 +425,7 @@ files:
405
425
  - docs/SubmitVatAmount.md
406
426
  - docs/SupplementaryAttachment.md
407
427
  - docs/Supplier.md
428
+ - docs/TaskErrorResult.md
408
429
  - docs/TaskResponse.md
409
430
  - docs/TaxBreakdownInput.md
410
431
  - docs/TaxDueDateType.md
@@ -426,19 +447,28 @@ files:
426
447
  - docs/VATAccountingCode.md
427
448
  - docs/VATAmount.md
428
449
  - docs/VATCategory.md
450
+ - docs/VATEXCodeInfo.md
451
+ - docs/VATEXCodesResponse.md
429
452
  - docs/VATLine.md
430
453
  - docs/VATPointDateCode.md
431
454
  - docs/ValidateCDARRequest.md
432
455
  - docs/ValidateCDARResponse.md
433
456
  - docs/ValidateEReportingRequest.md
434
457
  - docs/ValidateEReportingResponse.md
458
+ - docs/ValidationApi.md
435
459
  - docs/ValidationError.md
436
460
  - docs/ValidationErrorDetail.md
437
461
  - docs/ValidationErrorResponse.md
438
462
  - docs/ValidationInfo.md
439
463
  - docs/ValidationSuccessResponse.md
464
+ - docs/ValidationSuccessTaskResult.md
465
+ - docs/ValidationTaskStatus.md
466
+ - docs/ValidationTaskStatusResult.md
440
467
  - docs/VatRate.md
441
468
  - docs/VerificationSuccessResponse.md
469
+ - docs/VerificationSuccessTaskResult.md
470
+ - docs/VerificationTypedTaskStatus.md
471
+ - docs/VerificationTypedTaskStatusResult.md
442
472
  - docs/VerifiedFieldSchema.md
443
473
  - docs/WebhookSecretDeleteResponse.md
444
474
  - docs/WebhookSecretGenerateResponse.md
@@ -455,12 +485,15 @@ files:
455
485
  - lib/factpulse/api/downloads_api.rb
456
486
  - lib/factpulse/api/electronic_signature_api.rb
457
487
  - lib/factpulse/api/factur_x_conversion_api.rb
458
- - lib/factpulse/api/factur_x_generation_api.rb
459
488
  - lib/factpulse/api/factur_x_validation_api.rb
460
489
  - lib/factpulse/api/factur_xpdfxml_verification_api.rb
461
490
  - lib/factpulse/api/flux10_e_reporting_api.rb
462
491
  - lib/factpulse/api/flux6_invoice_lifecycle_cdar_api.rb
463
492
  - lib/factpulse/api/health_api.rb
493
+ - lib/factpulse/api/invoice_generation_api.rb
494
+ - lib/factpulse/api/parse_api.rb
495
+ - lib/factpulse/api/references_api.rb
496
+ - lib/factpulse/api/validation_api.rb
464
497
  - lib/factpulse/api_client.rb
465
498
  - lib/factpulse/api_error.rb
466
499
  - lib/factpulse/api_model_base.rb
@@ -495,6 +528,7 @@ files:
495
528
  - lib/factpulse/models/afnor_directory_line_search_post200_response.rb
496
529
  - lib/factpulse/models/afnor_entity_type.rb
497
530
  - lib/factpulse/models/afnor_error.rb
531
+ - lib/factpulse/models/afnor_error_detail.rb
498
532
  - lib/factpulse/models/afnor_facility_administrative_status.rb
499
533
  - lib/factpulse/models/afnor_facility_nature.rb
500
534
  - lib/factpulse/models/afnor_facility_payload_history.rb
@@ -596,6 +630,13 @@ files:
596
630
  - lib/factpulse/models/client_summary.rb
597
631
  - lib/factpulse/models/client_update_request.rb
598
632
  - lib/factpulse/models/contact.rb
633
+ - lib/factpulse/models/conversion_error_result.rb
634
+ - lib/factpulse/models/conversion_extraction_info.rb
635
+ - lib/factpulse/models/conversion_pending_input_result.rb
636
+ - lib/factpulse/models/conversion_success_task_result.rb
637
+ - lib/factpulse/models/conversion_task_status.rb
638
+ - lib/factpulse/models/conversion_task_status_result.rb
639
+ - lib/factpulse/models/conversion_validation_failed_result.rb
599
640
  - lib/factpulse/models/convert_resume_request.rb
600
641
  - lib/factpulse/models/convert_success_response.rb
601
642
  - lib/factpulse/models/convert_validation_failed_response.rb
@@ -621,8 +662,8 @@ files:
621
662
  - lib/factpulse/models/extraction_info.rb
622
663
  - lib/factpulse/models/factur_x_invoice.rb
623
664
  - lib/factpulse/models/factur_xpdf_info.rb
665
+ - lib/factpulse/models/facture_electronique_models_invoice_type_code.rb
624
666
  - lib/factpulse/models/facture_electronique_rest_api_schemas_chorus_pro_chorus_pro_credentials.rb
625
- - lib/factpulse/models/facture_electronique_rest_api_schemas_ereporting_invoice_type_code.rb
626
667
  - lib/factpulse/models/facture_electronique_rest_api_schemas_validation_validation_error_response.rb
627
668
  - lib/factpulse/models/field_status.rb
628
669
  - lib/factpulse/models/file_info.rb
@@ -637,6 +678,9 @@ files:
637
678
  - lib/factpulse/models/generate_certificate_request.rb
638
679
  - lib/factpulse/models/generate_certificate_response.rb
639
680
  - lib/factpulse/models/generate_e_reporting_response.rb
681
+ - lib/factpulse/models/generation_success_result.rb
682
+ - lib/factpulse/models/generation_task_status.rb
683
+ - lib/factpulse/models/generation_task_status_result.rb
640
684
  - lib/factpulse/models/get_chorus_pro_id_request.rb
641
685
  - lib/factpulse/models/get_chorus_pro_id_response.rb
642
686
  - lib/factpulse/models/get_invoice_request.rb
@@ -650,6 +694,7 @@ files:
650
694
  - lib/factpulse/models/incoming_supplier.rb
651
695
  - lib/factpulse/models/invoice_format.rb
652
696
  - lib/factpulse/models/invoice_input.rb
697
+ - lib/factpulse/models/invoice_lifecycle.rb
653
698
  - lib/factpulse/models/invoice_line.rb
654
699
  - lib/factpulse/models/invoice_line_allowance_amount.rb
655
700
  - lib/factpulse/models/invoice_note.rb
@@ -665,6 +710,8 @@ files:
665
710
  - lib/factpulse/models/issuer_role_code.rb
666
711
  - lib/factpulse/models/key_rotation_request.rb
667
712
  - lib/factpulse/models/key_rotation_response.rb
713
+ - lib/factpulse/models/lifecycle_event.rb
714
+ - lib/factpulse/models/lifecycle_response.rb
668
715
  - lib/factpulse/models/line_net_amount.rb
669
716
  - lib/factpulse/models/line_sub_type.rb
670
717
  - lib/factpulse/models/line_total_amount.rb
@@ -676,6 +723,7 @@ files:
676
723
  - lib/factpulse/models/operation_nature.rb
677
724
  - lib/factpulse/models/output_format.rb
678
725
  - lib/factpulse/models/page_dimensions_schema.rb
726
+ - lib/factpulse/models/parse_factur_x_response.rb
679
727
  - lib/factpulse/models/payee.rb
680
728
  - lib/factpulse/models/payment_amount_by_rate.rb
681
729
  - lib/factpulse/models/payment_card.rb
@@ -716,6 +764,9 @@ files:
716
764
  - lib/factpulse/models/signature_info.rb
717
765
  - lib/factpulse/models/signature_info_api.rb
718
766
  - lib/factpulse/models/signature_parameters.rb
767
+ - lib/factpulse/models/signature_success_result.rb
768
+ - lib/factpulse/models/signature_task_status.rb
769
+ - lib/factpulse/models/signature_task_status_result.rb
719
770
  - lib/factpulse/models/simplified_cdar_response.rb
720
771
  - lib/factpulse/models/simplified_invoice_data.rb
721
772
  - lib/factpulse/models/status_code_info.rb
@@ -741,6 +792,7 @@ files:
741
792
  - lib/factpulse/models/submit_vat_amount.rb
742
793
  - lib/factpulse/models/supplementary_attachment.rb
743
794
  - lib/factpulse/models/supplier.rb
795
+ - lib/factpulse/models/task_error_result.rb
744
796
  - lib/factpulse/models/task_response.rb
745
797
  - lib/factpulse/models/tax_breakdown_input.rb
746
798
  - lib/factpulse/models/tax_due_date_type.rb
@@ -768,13 +820,21 @@ files:
768
820
  - lib/factpulse/models/validation_error_response.rb
769
821
  - lib/factpulse/models/validation_info.rb
770
822
  - lib/factpulse/models/validation_success_response.rb
823
+ - lib/factpulse/models/validation_success_task_result.rb
824
+ - lib/factpulse/models/validation_task_status.rb
825
+ - lib/factpulse/models/validation_task_status_result.rb
771
826
  - lib/factpulse/models/vat_accounting_code.rb
772
827
  - lib/factpulse/models/vat_amount.rb
773
828
  - lib/factpulse/models/vat_category.rb
774
829
  - lib/factpulse/models/vat_line.rb
775
830
  - lib/factpulse/models/vat_point_date_code.rb
776
831
  - lib/factpulse/models/vat_rate.rb
832
+ - lib/factpulse/models/vatex_code_info.rb
833
+ - lib/factpulse/models/vatex_codes_response.rb
777
834
  - lib/factpulse/models/verification_success_response.rb
835
+ - lib/factpulse/models/verification_success_task_result.rb
836
+ - lib/factpulse/models/verification_typed_task_status.rb
837
+ - lib/factpulse/models/verification_typed_task_status_result.rb
778
838
  - lib/factpulse/models/verified_field_schema.rb
779
839
  - lib/factpulse/models/webhook_secret_delete_response.rb
780
840
  - lib/factpulse/models/webhook_secret_generate_response.rb
@@ -1,15 +0,0 @@
1
- # FactPulse::FactureElectroniqueRestApiSchemasEreportingInvoiceTypeCode
2
-
3
- ## Properties
4
-
5
- | Name | Type | Description | Notes |
6
- | ---- | ---- | ----------- | ----- |
7
-
8
- ## Example
9
-
10
- ```ruby
11
- require 'factpulse'
12
-
13
- instance = FactPulse::FactureElectroniqueRestApiSchemasEreportingInvoiceTypeCode.new()
14
- ```
15
-