Weave Code
Adobe Sign Bundle Laravel Package
postyou/adobe-sign-bundle
A Symfony bundle that integrates Adobe Sign (formerly EchoSign) into your application, providing service configuration and a client wrapper for sending agreements, managing signing workflows, and handling Adobe Sign API calls.
At a glance
Frequently asked questions about Adobe Sign Bundle
- Is postyou/adobe-sign-bundle a Laravel package?
- No. It is built and structured as a Symfony bundle, with a DI extension, service definitions and kernel-based bundle registration, so there is no Laravel service provider, config publishing or facade. To use it in a Laravel application you either run it inside a small Symfony sidecar you call over HTTP, or lift the underlying Adobe Sign HTTP client and re-wrap it in your own Laravel-native package.
- How do I install postyou/adobe-sign-bundle with Composer?
- Run composer require postyou/adobe-sign-bundle and register the bundle in your Symfony kernel, then configure the Adobe Sign service credentials. In Laravel there is nothing to auto-discover, so installation alone will not make the package usable. Pin the exact version you tested, for example 0.0.15, rather than relying on a range.
- Does this bundle support Laravel 10 or Laravel 11?
- It does not target Laravel at all, so Laravel 10 and 11 support is not something the package declares. The bundle is loaded through a Symfony kernel, so a Laravel app cannot boot it directly without an adapter layer or a separate Symfony service. Verify the declared PHP and Symfony version constraints in composer.json against your runtime before planning anything.
- What is the best way to use Adobe Sign inside a Laravel application?
- Treat the bundle as an anti-corruption layer rather than a drop-in dependency. Define your own narrow interface, for example createAgreement(), getAgreementStatus(), downloadSignedDocument() and verifyWebhook(), and implement it against this package so no call site ever references Postyou\AdobeSignBundle classes. That keeps a future swap to Adobe's official SDK or a hand-written REST client to a single file.
- Does this bundle handle OAuth2 token refresh and per-tenant Adobe Sign credentials?
- That is not confirmed by the package's documentation or its 0.0.15 release notes, which only add a new exception class. OAuth2 authorization code versus client credentials flow, token refresh, per-tenant credential storage and rate-limit handling all need to be verified in the source or implemented yourself. Store tenant credentials in your own encrypted config rather than in global bundle configuration.
- How does the bundle handle Adobe Sign API errors?
- Version 0.0.15 adds AdobeErrorResponseException, which gives you a typed catch target for error payloads returned by Adobe instead of string-matching messages or catching generic HTTP client exceptions. Beyond that, there is no documented error taxonomy distinguishing 401, 403, 429 and 5xx responses from Adobe business-logic failures. Map the exceptions you receive onto your own domain errors so call sites stay stable.
- Are Adobe Sign webhooks validated by this bundle?
- Webhook signature or client ID validation and idempotency handling are not confirmed as features of this bundle. Since signed agreement events are security-sensitive, assume you must implement verification and replay protection yourself. Route incoming Adobe Sign callbacks through your own controller and expose a verifyWebhook() method on your adapter interface.
- Is it safe to depend on a 0.0.x version like 0.0.15?
- A 0.0.x line carries no API stability contract, so exception classes, method signatures and namespaces can change in any patch release. The 0.0.15 release itself is low blast radius because it only adds a class, but the risk accumulates over future releases. Pin the exact version with a committed lock file and keep all usage behind your own interface.
- What are the maintenance and testing risks of this package?
- The package appears to be maintained by a single agency, so bus factor and release cadence are real concerns for production use. Test coverage and CI configuration are not clearly documented, and there is no stated security disclosure path. Plan for the possibility that the package stalls and keep the Adobe REST layer thin enough to reimplement the handful of methods you actually use.
- What alternatives exist to postyou/adobe-sign-bundle for Laravel projects?
- The main options are Adobe's official SDK wrapped in a Laravel service provider, a thin custom REST client covering only the endpoints you need, or running the Symfony bundle as a sidecar service behind HTTP. Given that agreement creation, status checks and document download are usually a handful of calls, a small hand-written client is often cheaper than owning Symfony compatibility. Choose based on how much Adobe business logic, such as widgets or transient documents, you actually need.
Weaver
How can I help you explore Laravel packages today?