Node.js & Express app with Google OAuth 2.0, EJS templating, and anonymous secret submission
Google APIs Authentication Client Library for Node.js
Octokit authentication strategy for OAuth clients
GitHub OAuth App authentication for JavaScript
GitHub OAuth Device authentication strategy for JavaScript
Set of stateless request methods to create, check, reset, refresh, and delete user access tokens for OAuth and GitHub Apps
GitHub App authentication for JavaScript
Google APIs Client Library for Node.js
GitHub API token authentication for browsers and Node.js
OAuth 2.0 authentication strategy for Passport.
Passport strategy for Google OAuth 2.0
The all-batteries-included GitHub SDK for Browsers, Node.js, and Deno
Google OAuth2 using Google Identity Services for React 🚀
OAuth 2 / OpenID Connect Client API for JavaScript Runtimes
Microsoft Authentication Library for React
OAuth 1.0 authentication strategy for Passport.
Official library for interacting with Slack's Oauth endpoints
Low-Level OAuth 2 / OpenID Connect Client API for JavaScript Runtimes
[](https://www.npmjs.com/package/@google/genai) [](https://www.npmjs.com/package/@google/genai)
This package provides pluggable adapters for OAuth 2.0 authentication schemes.
Library for interacting with OAuth 1.0, 1.0A, 2 and Echo. Provides simplified client access and allows for construction of more complex apis and OAuth providers.
Google (OAuth 1.0) authentication strategy for Passport.
Google authentication strategy for Passport using OpenID Connect.
A Better Auth component for Convex.
Perform Google OAuth authentication from the CLI using redirect flows. Authentication information is saved in a file and can be used for the next authentication.
A full featured wrapper for interacting with the Google Calendar API
This gem provides a Ruby wrapper around the Google Places API for use in your own project. Please note that this gem does not provide OAuth authentication.
Adds Google OAuth as a credential type to RSB's auth system. Registers into the credential registry, provides OAuth redirect/callback endpoints, and verifies id_tokens via Google JWKS.
Hybrid authentication and authorization strategy for Google APIs. Combines the process for obtaining an authorized OAuth request token along with an OpenID authentication request.
This gem provides a set of wrappers designed to make it easy to work with the Google Data APIs. This fork enables OAuth authentication
This gem provides a set of wrappers designed to make it easy to work with the Google Data APIs. This fork enables OAuth authentication
Many companies have internal apps to support their day to day operations. This library is a drop-in Google OAuth authentication and session management library so you don't have to install Devise.
This gem provides a Ruby wrapper around the Google Places API for use in your own project. Please note that this gem does not provide OAuth authentication.
Shakha is a headless authentication broker gem for Rails that handles Google OAuth 2.0 with PKCE security. It provides domain-scoped user identifiers via pairwise subjects, ensuring the same Google account gets different IDs across different applications. Built DHH-style: database sessions (no Redis), Turbo native (zero JS), and a single "Continue with Google" button. Works as an embedded Rails engine or standalone service.
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.