Make construction of transaction easier on NEAR blockchain.
Multi Transaction Account implementation.
Multi Transaction Core implementation.
Multi Transaction Wallet Selector implementation.
Multi Transaction common utilities.
A multi-transaction protocol for storing data in the Bitcoin blockchain.
BitGo's account library functions
Implementation of the various Ethereum Transaction Types
Helpers for creating and serializing transactions
Utilities for decoding and encoding Ethereum transaction for ethers.
Helpers for creating transaction messages
[](https://www.npmjs.com/package/@aws-sdk/signature-v4-multi-region) [](https:/
Helpers for confirming Solana transactions
Audited & minimal library for Bitcoin. Handle transactions, Schnorr, Taproot, UTXO & PSBT
[](https://github.com/bitcoinjs/bip174/actions/workflows/main_ci.yml) [](https://www.npmjs.org/package/bip174)
A TypeScript/JavaScript API for interacting with the XRP Ledger in Node.js and the browser
Arweave JS client library
BitGo's account library functions
A transaction factory implementation relying on Solana's web3.js
Helpers for creating transaction instructions
Stores transactions alongside their periodically updated statuses and manages interactions such as approval and cancellation
Node.js body parsing middleware
Postgres Sync for PGlite
Typescript SDK for Supra
A programming framework for bitcoin smart contracts.
Pragmatic Rust utilities for Solana development - safety, speed, analytics, and DeFi
Sentri: Transaction simulator for Sentri invariant testing and code generation validation.
Compression strategy trait + SBF-compatible implementations for Solana programs
MVCC page-level versioning for concurrent writers
LLM-powered fuzzing assistant for Solidity smart contracts — generates, runs, and iterates invariant tests with Foundry
A helper crate for integrating Arcium into Solana programs.
Reason: A Shell for Research Papers
Advanced logging classes with buffer backend, transactions, multi logger, etc
Advanced logging classes with buffer backend, transactions, multi logger, etc
Ruby client for Solana's JSON-RPC API. Handles balance, token accounts, signatures, transactions, and blockhash queries. Includes SSL CRL workaround and multi-network configuration.
Delayed is a multi-threaded, SQL-driven ActiveJob backend used at Betterment to process millions of background jobs per day. It supports postgres, mysql, and sqlite, and is designed to be Reliable (with co-transactional job enqueues and guaranteed, at-least-once execution), Scalable (with an optimized pickup query and concurrent job execution), Resilient (with built-in retry mechanisms, exponential backoff, and failed job preservation), and Maintainable (with robust instrumentation, continuous monitoring, and priority-based alerting).
Dry::Workflow allows developers to define complex, multi-step business processes with a clear DSL. It supports `step`, `map`, and `try` operations, similar to dry-transaction, but with an added emphasis on defining and executing rollback procedures for each step if the workflow fails. This helps ensure data consistency and provides a structured way to handle failures in long-running or critical operations.
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/
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.