API Changes
POST /public/v1/documents/{document_id}/send-reminder
/public/v1/documents/{document_id}/send-reminder- ⚠️ added the new
Can't send SMS reminder to recipient groupenum value to theresult/items/sms/detailresponse property for the response status200 - removed the
Can't send reminder to recipient groupenum value from theresult/items/email/detailresponse property for the response status200 - removed the
Can't send reminder to recipient groupenum value from theresult/items/sms/detailresponse property for the response status200
API Changes
Changed
- Customers can now add, rename, reorder and delete template roles by passing a roles array (it replaces the template's full role set in one call).
PATCH /public/v1/templates/id
- Role IDs of existing roles can be retrieved via
GET /public/v1/templates/{id}/details. - Docs: https://developers.pandadoc.com/reference/updatetemplate
Changed
- Updating document fields is now atomic: either all fields are updated or none are, so partial updates no longer leave documents in an inconsistent state. On success, the endpoint now returns
204 No Contentinstead of200 OK— update any clients that rely on parsing the response payload.
PATCH /public/v1/documents/{id}/fields
- ⚠️ removed the success response with the status
200 - added the success response with the status
204
Added
-
Added a new endpoint to retrieve notarization requests, enabling you to programmatically fetch details about notarization processes.
GET /public/v2/notary/notarization-requests- endpoint added
Changed
-
Enhanced the notarization request creation endpoint with new error responses, providing clearer feedback with
400 Bad Requestand401 Unauthorizedstatuses for invalid requests or authentication issues.POST /public/v2/notary/notarization-requests- added the non-success response with the status
400 - added the non-success response with the status
401
- added the non-success response with the status
We’ve enhanced our Field Tags capabilities to provide more flexibility when building your documents. Previously, radio buttons were always required, and the optional * modifier was unsupported.
We are excited to share that radio buttons now fully support the optional modifier (*), allowing recipients to leave these fields unselected if desired!
With this update, the current limitations when working with radio buttons have been updated to the following:
- Radio button options within the same block must be on the same page.
- Preselection of options is not supported.
- Different blocks require unique IDs.
- Values for radio button options must be unique.
- Each document can have a minimum of two and a maximum of 50 radio button options.
📚 Documentation: For more details, check out our updated guide on How to Add Field Tags to Documents.
Added
- Beta document endpoints let you pull the full document text in plain text or Markdown, and request summaries at three levels (detailed, short, or headline). When content or a summary is still being prepared, the API responds with 202 and a Retry-After hint so clients can poll safely. Successful responses include ETag and Vary so caches stay correct when you change
formatortype.
GET /public/beta/documents/{document_id}/content
- endpoint added
GET /public/beta/documents/{document_id}/summary
- endpoint added
Added
- Enhanced notarization request details to include termination information. You can now retrieve details and reasons for a notarization session's termination, providing more comprehensive insights into session outcomes.
GET /public/v2/notary/notarization-requests/{session_request_id}
- added the optional property 'termination_details' to the response with the '200' status
- added the optional property 'termination_reason' to the response with the '200' status
