GET /public/v1/logs → endpoint removal
PandaDoc API
Deprecated, no date
PandaDoc deprecated GET /public/v1/logs on February 4, 2026, without a shutdown date. This deprecation affects calls made to the GET /public/v1/logs endpoint. Requests sent to this endpoint will eventually fail once the sunset takes effect.
Calls it hits
GET /public/v1/logs
What to use instead of these calls
Use GET /public/v2/logs instead.
In PandaDoc API's words
The /public/v1/logs and /public/v1/logs/{id} endpoints have been deprecated. Please update your integrations to use alternative methods for accessing log data before the sunset date.
Facts
- API
- PandaDoc API
api.pandadoc.com - Kind
- Endpoint removal
- Announced
- February 4, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against PandaDoc API's own pages
Questions
When does this change take effect?
PandaDoc API deprecated GET /public/v1/logs without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: PandaDoc API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from PandaDoc API 1
-
No date
GET /public/v1/logs/{}Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.