- How do I install vinicinbgs/autentique-v2 in a Laravel application?
- Install the package with Composer using composer require vinicinbgs/autentique-v2. Then publish and configure the package credentials for your Autentique API v2 account according to the package documentation. No database migration or config migration is indicated for the v4.3.3 patch release.
- Which Laravel and PHP versions does autentique-v2 support?
- The package is a Laravel/PHP integration for the Autentique API, but the provided context does not list a specific PHP or Laravel version matrix. Check the package composer.json and README for the exact constraints before adopting it. Confirm compatibility in your application's CI pipeline, especially if you are on an older Laravel release.
- How do I create and send an electronic signature document with autentique-v2?
- The package provides a PHP client for the Autentique v2 API with a fluent interface for creating, sending, and managing signature documents. You build the document request through the package API, attach signers, and send it to Autentique for the signing workflow. Validate the full signing journey in staging, including status transitions and any webhook handling.
- Can I manage folders and signers with this Autentique PHP package?
- Yes, the package exposes a fluent interface for folders, signers, and webhooks in addition to signature documents. This lets Laravel applications organize documents and manage signer data without building a custom Autentique API client. Review how signer personal data is stored and logged in your application for privacy compliance.
- Does autentique-v2 support Autentique webhooks for signature status updates?
- The package includes webhook support as part of its fluent interface for the Autentique v2 API. You will still need to implement and secure your own webhook endpoint in Laravel and handle delivery failures or retries. Monitor webhook lag and signature failures as part of your production observability.
- What changed in vinicinbgs/autentique-v2 v4.3.3 regarding biometry?
- Version 4.3.3 is a patch release with one fix described as missing biometry info. The release notes do not specify whether the fix changes outgoing request fields, incoming response mapping, or persisted data. Review PR #54 and test biometry-enabled and biometry-disabled signature flows before rolling out to production.
- Is the v4.3.3 biometry fix a breaking change for existing Laravel integrations?
- No breaking API or configuration change is indicated for v4.3.3, and the release risk is low from a semver perspective. However, product and compliance risk is moderate if biometry data is in scope because the blast radius is not documented. Pin your current version, review the changelog and PR, and keep a rollback to the prior patch version.
- How should I handle queues, retries, and rate limits with autentique-v2 in production?
- Use queued jobs, retries, idempotency, and clear timeout handling for signature creation and status synchronization. Scaling is primarily bounded by Autentique API limits, network reliability, and your application queue capacity rather than by the package itself. Monitor rate limiting, credential expiry, signature failures, and webhook delivery problems.
- How can I test the Autentique e-signature integration without sending real documents?
- The provided context does not describe a sandbox mode or fake HTTP client for the package, so check the README and Autentique account options first. At minimum, run signature-creation tests in staging with biometry enabled and disabled, and verify webhook and status transitions. Avoid logging sensitive biometry or personal data during test runs.
- Is vinicinbgs/autentique-v2 a good alternative to building a custom Autentique API client?
- It is a reasonable fit for Laravel applications that want to avoid maintaining a custom Autentique v2 API client. Treat it as an API adapter rather than the system of record for signature evidence, consent, or compliance records. Ongoing maintenance is generally low, but you should still monitor upstream Autentique API changes and your own e-signature workflow requirements.