PandaDoc API Enhancements: Jan & Feb Edition
API update: Introducing 4 new features, OpenAPI specification and upcoming changes.
Hello to all developers here 👋
I’m Maria, the API Product Manager at PandaDoc. We’re continuously improving our product and thought it might be helpful to notify you about the latest changes and upcoming releases.
And today, we are happy to share our second API update with you! Below is the list of recent items released in January & February. Enjoy and let me know if you have any questions, feedback, or comments :)
And if you missed the previous update, please check our first PandaDoc API Enhancements edition, where we announced 8 new features, including Link to CRM, Signing Order, Attachments, and much more.
About PandaDoc API platform
What is PandaDoc API used for? It’s an easy and scalable all-in-one API solution for generating documents and capturing eSignature by embedding them into your app, website, or using the backend API. We have detailed documentation, so you can get started with ease. For help or if you want solution expertise for your business problem, write to us here.
🎉 Public OpenAPI specification is out 🎉
Let’s start with a long-awaited update! Today, we are excited to announce that we launched a public OpenAPI specification (ex-Swagger).
That means you may benefit from fully descriptive and interactive documentation, which allows testing PandaDoc API right on a web page.
New features released
1. Document creation with unassigned fields (including via API)
Our customers use unassigned fields on their uploaded PDFs and then populate those unassigned fields with data. Previously, customers with v2 Editor couldn’t create documents with unassigned fields due to feature discrepancy with the former v1 Editor.
Now, PandaDoc documents created with v2 Editor may be sent with unassigned fields. Also, we provide the possibility for removing assignees from fields in the document created previously.
Please see details here: Documentation for Document creation from Template
2. Added Roles in Document Details and webhooks
PandaDoc API returns additional info about recipient roles with Document details response and in a Webhook payload.
Many customers requested this data to be provided, so they could populate data on their side and match the sent and completed documents.
Developer documentation is here.
3. Public view link in Document details
Public Links in API functionality returns a unique link for the document for each of the recipients, in response of:
So you don’t need to send documents via email (“silent”: true) to provide all functionality of the recipient’s view.
4. Improved error handling for documents creation
- To the API error responses, we’ve added more straightforward explanations. For instance, “Field tag validation error” has been transformed to “Error occurred while parsing PDF field tags. Please try PDF flattening or reach out to support”.
- Also, we’ve added details about validation when it’s not passed. For example, “The maximum file size exceeded, limit is 100 Mb”.
- In addition, a number of bugs were created and fixed for incorrect response codes.
Upcoming changes
We’ll continue to add more features to provide a best-in-class developer experience. Stay tuned! But here is a small spoiler for you on what’s coming next:
- API documents creation from DocX.
- Radio buttons support in documents created from Template.
- Provide error code and reason for Webhook event “Document creation failed”.
Get started!
With these updates to the API, we hope that now it would be even easier for you to implement document generation solutions with legally binding eSignature for your business. To get started, head over to our complete documentation with how-to guides, and real examples and try it out! Or get your free developer sandbox account to start building documents today.
