- Can I use gheb/docusign-bundle in a Laravel application?
- No. It is a Symfony bundle that relies on Kernel::registerBundles(), a DI Extension with a docusign: Configuration tree, compiler passes and Symfony event subscribers, none of which exist in Laravel. The Laravel ServiceProvider and Facade model with config/*.php files cannot autoload or resolve the bundle's services, so it will not work in a standard Laravel app. Both frameworks share symfony/* components, so the concepts port cleanly, but the artifact as shipped is Symfony-only and best treated as a reference implementation.
- How do I install gheb/docusign-bundle in a Symfony application?
- Install it with composer require gheb/docusign-bundle and accept the Symfony Flex recipe, which creates the config/packages/docusign.yaml file for you. Then make sure the bundle is registered in config/bundles.php, which Flex normally handles automatically. On a non-Flex project you must register it manually and create the configuration file yourself.
- How do I configure DocuSign credentials for this bundle?
- Credentials live in the docusign: configuration tree, typically in config/packages/docusign.yaml, and cover the integrator key (client ID), impersonated user ID, account ID, private RSA key path and OAuth base path. Keep the private key and integrator key in environment variables rather than committing them. Check the bundle's README for the exact key names, since they follow the bundle's own config schema rather than DocuSign's API field names.
- Does the bundle support JWT Grant authentication and token caching?
- Yes. It implements DocuSign JWT Grant authentication with automatic access-token caching and refresh, so you exchange a signed JWT for an access token once and reuse it until it expires. Remember that JWT Grant still requires a one-time admin consent step in DocuSign, and tokens are only valid for about 60 minutes. The bundle does not ship a per-user Authorization Code Grant flow, so confirm which auth model your application actually needs.
- Does gheb/docusign-bundle support embedded signing and recipient views?
- Yes. The bundle exposes services for generating recipient views, which is what you need for embedded signing inside your own application UI. You create an envelope, then request a recipient view URL for a specific recipient and return that URL to the browser. This is one of the main reasons to use the bundle rather than hand-rolling raw REST calls.
- How do I send an envelope with templates and recipients in this bundle?
- Inject the bundle's envelope service, build an envelope definition referencing a template ID and templateRoles for each recipient, then set the status to sent so DocuSign delivers it. Documents can be attached through the document service when you are not using a server-side template. Because everything is a PSR-friendly injectable service, you avoid constructing raw HTTP requests and JSON payloads by hand.
- Which Symfony and PHP versions does gheb/docusign-bundle support?
- Release 5.6.5 added psr/log ^3.0 support along with a code-style fix, which makes modern Symfony and PHP stacks easier to satisfy than earlier releases did. Always read the composer.json constraints for the exact Symfony and PHP ranges before upgrading a project. If you are on an older Symfony version, verify compatibility first because the bundle predates current releases.
- Is gheb/docusign-bundle actively maintained and safe for production?
- It is maintained but small: version 5.6.5 shipped on top of 5.6.4 with work from two contributors, so the project is alive rather than abandoned. However, it has roughly 34 stars and almost no dependents, meaning there are no real production-usage signals, no issue history to mine for edge cases, and no visible governance, security disclosure process or SLA. Pin the version, review the code you depend on, and assume no upstream fix arrives on your timeline.
- What are the alternatives to gheb/docusign-bundle for a Laravel app?
- The recommended path is to skip the bundle and wrap the official docusign/esign-client PHP SDK in a thin Laravel package with a service provider and facade, which typically takes two to four days and avoids fork ownership. You can also fork the bundle's internals into a Laravel service provider, but that costs three to five days plus ongoing maintenance of the fork. Use this repository as documentation of the object graph you need, including JWT signer auth, envelope definition building, recipient view generation and Connect webhook handling.
- How do I test a DocuSign integration without calling the live API?
- The bundle's PSR-friendly service layer is designed to be mocked, so unit tests can stub the envelope, template and recipient view services without any network calls. For integration tests, point the client at a DocuSign developer sandbox account rather than production and keep credentials in test-only environment variables. The bundle ships no field validation or dedicated test helpers, so you will need to assert your own envelope payloads and consent flow behavior.