About
Disclaimer
This SDK is an independent open-source project. Conceptualize built it to work with Adobe Acrobat Sign; Adobe did not build it, review it or endorse it. This page explains what that means, and what you can and cannot rely on.
In short
- Independent. Not affiliated with, endorsed by or sponsored by Adobe Inc.
- As is. Free, MIT-licensed software, provided without warranty.
- Not legal advice. Explanations of SES, AES, QES, eIDAS and other countries' signature laws are orientation only.
- Your account, your responsibility. Using Acrobat Sign is governed by your own agreement with Adobe.
An independent project
conceptlz/adobe-sign (the framework-agnostic PHP SDK) and conceptlz/adobe-sign-laravel
(its Laravel bridge) are created and maintained by Conceptualize. They are
client libraries: they call the public Acrobat Sign REST API v6 on your behalf, using credentials you
obtain from Adobe for your own Acrobat Sign account.
Neither package is an Adobe product. Adobe Inc. has not developed, reviewed, certified, sponsored or endorsed them, and is not responsible for them. Adobe's own documentation and support channels are the authority on how Acrobat Sign behaves. When this documentation and Adobe's disagree, Adobe's describes the service, and this documentation describes what the SDK does with it.
The SDK's models are generated from the OpenAPI description of the REST API that Adobe publishes, and its behaviour was checked against a real Acrobat Sign account. That makes the SDK compatible with the API; it does not make it official.
Trademarks
Adobe, Acrobat, Acrobat Sign and Adobe Sign are either registered trademarks or trademarks of Adobe Inc. in the United States and/or other countries. Laravel is a trademark of Laravel Holdings Inc. PHP is a trademark of The PHP Group. GitHub is a trademark of GitHub, Inc. All other trademarks are the property of their respective owners.
These names appear in the packages and this documentation only to say which service and frameworks the software works with. Their use does not imply any affiliation with or endorsement by the trademark owners. The documentation deliberately uses its own design and does not use Adobe's logos or brand styling.
No warranty
Both packages are released under the MIT License. As that licence states, the software is provided "as is", without warranty of any kind, express or implied, including fitness for a particular purpose and non-infringement. Neither the authors nor the copyright holders are liable for any claim, damages or other liability arising from the software or its use.
In practice this means:
- Test your integration, with your own documents and your own Acrobat Sign account, before relying on it in production.
- Pin versions in
composer.jsonand read the changelog before upgrading. Until version 1.0, minor versions (0.4 → 0.5) may contain breaking changes. - Keep your own records of agreements and signed documents. The SDK helps you download them; it does not archive them for you.
Not legal advice
Signature law is jurisdiction-specific
The pages on signature levels, identity checks, eIDAS and national signature laws explain how these frameworks are generally understood, so that developers and technical leads can talk to their lawyers in the same terms. They are not legal advice and do not create any professional relationship.
Whether a particular signature is valid, admissible or sufficient depends on the jurisdiction, the type of document, the parties, any contractual requirements and the facts. The SDK lets you request a signature level and reports the evidence Adobe returns. It cannot decide what the law requires, and whether a signature is qualified depends on the trust service provider configured on your Acrobat Sign account, which the SDK does not control. Confirm your requirements with qualified counsel or your compliance team.
Your responsibilities
When you build with these packages, you remain responsible for:
- Your Adobe relationship. Your use of Acrobat Sign is governed by your agreement with Adobe, including its terms of use, pricing, plan limits and acceptable-use rules.
- Credentials. Integration Keys, OAuth client secrets and tokens give access to your account. Store them securely; the SDK redacts them from its exceptions and logs, but it cannot protect a key you commit to a repository.
- Personal data. Agreements contain the names, email addresses and documents of real people. You decide what you send, you are typically the data controller, and you need a lawful basis, appropriate notices and retention rules. See the privacy policy for what the packages themselves do with data.
- Signers' experience and consent. Choosing identity checks, signature levels and signing order is a business and legal decision as much as a technical one.
- Verifying outcomes. Check agreement status and signature evidence before you treat a contract as concluded.
Third-party services can change
Acrobat Sign is a service operated by Adobe. Adobe can change its API, its behaviour, its error codes and the features available on each plan at any time. Several behaviours documented here, such as data-centre routing, ETag handling and fields that differ from the published specification, were observed against a real account on the dates given in the changelog and may change. Features such as hybrid routing, digital signatures, government-ID checks and identity gateways also depend on your account's plan and settings.
Conceptualize has no control over Adobe's service and cannot guarantee its availability, pricing or continued compatibility. When Adobe changes something, an SDK update may be needed.
Accuracy of this documentation
The documentation is written to match the source code of the release it ships with, and the examples are checked against that code. Mistakes are still possible. If something here disagrees with the code, the code describes what actually happens; please open an issue so it can be corrected.
Example names, email addresses, agreement ids and outputs on these pages are illustrative. Addresses use
the reserved example.com domain.
Security reports
If you find a security problem in either package, please do not open a public issue. Email info@conceptualize.ae with a description and, if possible, steps to reproduce it. Problems in Acrobat Sign itself should be reported to Adobe.
Contact
Questions about this disclaimer: info@conceptualize.ae. Bugs and feature requests: GitHub issues.